Consolidated Device Settings

The are too many dis-joined settings pages and they all need to be consolidated so you don’t need a treasure map to know which setting page has the setting you are looking for. Many of the settings pages only have one or two options on them.
Here are some examples of the different settings pages I have come across just to try and find where to update the IP of my devices (still haven’t found where to do this and have been looking for over an hour)…

Under Overview if I open an Entity:
I can click “settings” (can’t set the IP)
Within settings, if I choose “Advanced settings” (still can’t set the IP)

Under Settings - Devices & Services:
I can choose “Configure” (can’t configure the IP)
I can choose “…” then “System Options” (no option to change IP)
I can go to Devices tab and open the device (can’t update device IP)
In the device page I can click “Edit settings” pencil in top right (can’t edit the IP)

Um… Might help if you could tell us what device you’re talking about?

The actual problem is that many devices configured by the GUI do not actually allow to reconfigure basic connection settings like the IP address :frowning:

Random example: Harmony

image
image

Workaround/last resort: Edit directly in .storage/core.config_entries and restart

image

Unfortunate side-effect of moving from YAML configuration to GUI…

The setting nonsense is for all devices, as I provided 6 different places of where to find settings for a device. It appears the same for all my integrations (Insteon, Pentair, Magic Home, Broadlink, etc.). I think simplifying would make for a better overall experience.

I don’t understand how it would not be “allowed” via GUI, but it’s “allowed” via config file. Same user, same permission. To me it sounds like the option just needs to be exposed as a configurable setting in the GUI.

“Allowed” as in “not able to do it”, not as in “permitted to do it” (although that’s a practical side-effect) :wink:

Indeed, just that it’s the responsibility of the integration developers, and they more than often do not do it, for whatever reason, forcing to remove/add the integration (or hack the configuration files) rather than enabling configuration through the GUI.

I’m not sure there are guidelines for developers on that subject…