2022.5: Streamlining settings

Ildar_Gabdullin · May 4, 2022, 9:29pm

I just started testing the 2022.5 rev.
And the first thing I checked is the new UI.

I am using Dev tools a lot.
Well, I am tired of reminding how uncomfortable is “not showing entity_id” in the “Set state” panel (as well as in History and some other places) - time flows, this functionality is not being fixed. OK, what can I say…

But I wonder why the RESTART button was hidden so deep?
Where is a logical connection between “YAML”, “Dev tools” & “Restart” ?
Move all Automations, Blueprints - everything low-level - to the Dev tools then…

OK, there is one more Restart button:

But for me “Check config”, “Restart”, “Reload yaml stuff” are commands which are used very often.

sparkydave · May 4, 2022, 9:36pm

Well restarting is something you shouldn’t need to do too often, only when changing things… as the ‘dev’ of your system…

Ildar_Gabdullin · May 4, 2022, 9:38pm

Since many things are changing, I am in a constant “development mode”…
And I am still learning too.

petro · May 4, 2022, 9:38pm

The entire page has to do with yaml configuration except for the reload button… Reload individual integrations that are yaml only, or checking your configuration. The restart being there is/was a bonus. The restart button is also accessible via the search button, the c hotkey, the settings → system menu, and the services tab.

Ildar_Gabdullin · May 4, 2022, 9:42pm

As was mentioned in the Community many times, people are very sensitive to UI changes.
This particular change (Check config, Reload yaml staff moved to Dev tools) is not critical at all.
Moreover, I appreciate moving Blueprints to Automations, Helpers to Entities.

petro · May 4, 2022, 9:44pm

Well, I guess we will be repeating this conversation again next release.

CentralCommand · May 4, 2022, 9:45pm

Type ‘c’ and type ‘reload’ from any page:

As with restart there’s really no reason to navigate to any particular page.

Now one thing that is missing from here unfortunately is check config. That needs to be added. Although you could always do what I do and have an automation that automatically calls homeassistant.check_config any time a yaml file changes in your config folder. Then you never forget to run it!

Ildar_Gabdullin · May 4, 2022, 9:46pm

Earlier Blueprints were in the same section as Automations.
Then they were moved to another section.
Now they are again in the Automations.
If they will be moved once again, similar conversations may start again…

TheHolyRoger · May 4, 2022, 9:46pm

Have you tried actually opening a Pull Request for this particular change you want for entity_id? Would only be a couple of lines of code to show it like this.

petro · May 4, 2022, 9:46pm

It’s almost like people are listening to feedback…

petro · May 4, 2022, 9:53pm

FYI, you’re welcome to join the discussions before these changes go live.

Ildar_Gabdullin · May 4, 2022, 9:53pm

Is this “entity_id” field available out-of-box?
In this 2022.5.0 release?
No.
I am not sure that many people know about a fix.

Could you post a link to the fix?

Ildar_Gabdullin · May 4, 2022, 9:54pm

Thank you!

petro · May 4, 2022, 9:57pm

You know that instead of using the set state box, you can just use the grid below? You can copy the entity_id from there. Or click the entity and then copy the id from the states drop down.