All helpers are not fully reconfigurable

There are helpers in UI that have many parameters but when you once configure it you can’t change most of parameters any more.

For example in Riemann sum integral sensor you can change only precision but not the source sensor, integration method etc.

Utility Meter let you later change the source but not a supported tariffs.

There are probably more similar inconsistencies.

The examples you posted aren’t helpers. They are integrations.

You should probably change the title to better reflect that.

The configuration of these is under “Helpers” section in UI. Technically they are integrations but you don’t see and can’t access these integrations under the “Integrations” tab :slight_smile:

1 Like

Well isn’t that silly.

I guess I don’t know how HA classifies some integration as a helper or not. I’ve never looked in the “helpers” tab since I never configure my “input_x” entities thru the UI and I thought only “input_x”, timer & counter entities were considered helpers.

Otherwise what’s the point of having integrations classified separately if any random integration can be called a helper? Not a question for you specifically but just a generic “WTH?” question.

4 Likes

Whether its an integration or a helper. It does not matter. Its accessed and used though the helpers section.

There are options under the helper section that one can configure (like integration) but when you go to edit them some of the key options are missing. That’s a problem and it would be really useful if the standard was that anything in the helper section had a UI that allowed all the settings (where that makes sense) to be corrected/ updated.

I agree with all of that.

I was just saying that it is silly that some regular integrations are suddenly designated as “helpers” thru a seemingly arbitrary decision and are configured under a different tab.

I still say the title should be changed to include all UI integrations and not just helpers.

If we are forced to configure integrations thru the UI (whether they are regular or “helpers”) then every integration should be re-configurable thru the UI as well.

Still no solution about this issue ?

Just ran into this with the Utility Meter helper. Once configured you can only modify the Periodically resetting and what sensor it’s based off.

Headbutting against this exact issue right now. WTH can’t I change the cycle of a utility meter helper in the UI after it’s creation? Also because I’ve made it in the UI it’s not like there’s a YAML file I can just jump in and edit, so the only option is to delete and re-create the helper, which is as frustrating as it sounds.

Hit this again. I changed IP address for frigate but cannot change it via the integration configuration UI.

This is even worse considering this integration has nearly 500 entities and when I delete and re-add it the entities will all be suffixed with _2 since the original entity name was taken.

I’ve dealt with this so many times now across so many different integrations. It’s getting pretty infuriating. All of the options you get when adding an integration should be available when you edit it. YAML didn’t have this limitation.

1 Like

This integration is a custom integration. Home Assistant provides an API to reconfigure options but many integrations do not take advantage of it, you should request reconfiguration feature request on the frigates custom integrations Github page.

Secondly, frigate is not a helper. All built-in helpers now allow re configuring for all setup options.

Hue and Unifi integrations have this exact same issue and they are internal integrations. I will report it for the Frigate integration though.

I know these are not helpers and are not directly related to this thread just figured I would post back here since I had the same issue with a helper. I’ll go post my feedback in the right place though.

To get around this issue I shutdown HA and modify the storage config files directly. It’s quite an annoying way to have to fix this but it works and doesn’t muck up my entity ids.

You can always open a Feature Requests for each integration.