Like it. Esp. the direct-deep-links in devices and automations. Should be in the other menu items as well.
didn’t see this mentioned yet, but Ive always wondered why the About isn’t under System. Isn’t the about the about of the system…?
With Petro, I find the meatballs menu the most confusing bit of the current frontend. That is, besides the Repairs (again under the meatballs/kebab? Btw why this is not called Chicpeas is beyond me. being a vegetarian)
Even the wording says it all… this is nothing to repair. It’s System info.
Please re-order that.
2 Likes
Good point.
I agree with the buttons at the top of the page. I was envisioning something slightly different, but TBH it doesn’t matter how they are displayed as long as they aren’t in the meatballs.
I don’t agree with the search bar. It’s redundant. You have a search at the top with the magnifying glass.
I don’t think we should get rid of hardware as hardware specific things will be added there in the future. I do think we should add information w/ the startup times and the system information.
The backup and storage should stay separated. I believe both will be getting additional features in the future.
2 Likes
Thank you for the feedback. I agree we don’t need redundant things (as much as possible at least).
Though the search bar I had to look up to see. And the fact that I had to search for the search function says enough. In my opinion this should not be another click and the hourglass should not be all the way up in the right corner either.
But maybe even more important is to improve the search function. Because I just search “timezone” nothing is found. If I search “people” nothing is found. How does a search function, in settings, help me if it doesn’t bring me to the settings I can’t find?
About the Backup and storage, I agree with you. And the same goes for hardware.
1 Like
A log isn’t a setting.
2 Likes
My favorite: Energy Settings. How to reach them without searching ?
Please rethink the settings Menu, its almost on windows 11 level now 
That’s why it’s under system 
Settings → Dashboards → Energy. Not the greatest placement IMO, but easy to learn.
1 Like
Oh wow, this Should not be there, but anyway thanks
1 Like
[funny mode]
Can’t find a setting
Search “Petro” ask him where to find it
Click to correct place to make setting
[/funny mode]
I’m pretty sure Amazon mechanical turk has an API. Make a conversation integration for it. When you ask a question it asks it over there and returns the response.
2 Likes
I think good settings navigation these days is less about good menu hierarchies and more about good “search functionality”.
Who really cares where it is if you can start typing a keyword and see relevant results appear as you type…
1 Like
You are somehow right, but for what would you search if you don’t know, that a setting is available at all?
For “discovering” settings, you probably aren’t in a rush to get some task done.
So just trawling through big lists that are grouped “ok but not amazingly” is probably ok.
Devices and Services?
Services isn’t in there.
It’s in Developer Tools. Did it used to be under the Devices & Services menu?
Or does Services in that menu refer to something different that is no longer labelled Services?
Services as in services provided by other companies
I didn’t know the restart button was in that place until I read this thread and i’ve hit that page lots of times - my eye doesn’t get drawn to the top right at all.
My annoyance is when I have updates and I click “Show All Updates” I go to a page listing my updates. I click the back arrow at the top and I’m not at the screen I just came from?! That is confusing - I’ve been moved further into the menu and my back button doesn’t take me back. I used to end up just having to click on “Settings” again to get me back to where I wanted to be until I figured out what was happening.
Hey guys. Interesting post. I am also a bit frustrated when I try to reach the “Restart HA / quick reload” menu.
Is there a way to add the above as shortcut buttons to the UI?
type: button
tap_action:
action: call-service
service: homeassistant.restart
data: {}
target: {}
entity: 'whatever'