UI is really nice.
To Point 1) i can’t say anything as it never bothered me in any way.
for 2 and 3 i can just say: Poster is right here!
But 4) is a killer. In yaml it was just a little change of an entry and everything worked fine again. Now for many integrations it feels like being locked out of my own system.
5) is a really nice idea! Please make this possible!
In cosmically connected event, Geoff Geerling just did a video on how he commissioned a light switch and a motion detecter. It’s a fascinating display of just how a user’s path appears before them…HA UI team, check it out for deep insight:
This also gives an indication into how much of a challenge this new objective will be.
Good news! Hope to see a real powerful upgrade.
But if we are speaking about experience it is very important to finish all bugs troubleshooting and full features adding for existing integration. Home Assistant issue tracker and community forum are full of bugs and important feature requests with no any feedback from authors. Some inquiries can stay with no any feedback from the authors for many months, what didn’t take place a couple of years ago.
Here are the examples:
Very slow work of lovelace in case it has a lot of entities and last visited lovelace page loss;
One fairly simple response, to Geoff’s experience of being left to wonder if the process of onboarding his devices was complete, is to present a ‘Finished?’ button allowing the user to decide this for themself. This button could be a simple link to a pre-filtered device list of the new devices that had been loaded. This would have led Geoff to his new toggle button etc. which in turn leads him to the opportunity of adding it to Lovelace
Yes to all of that, especially point 1 about math, so many times I find myself setting up a graph, gauge or card and find that 2 or more sensors dont have the same units.
Then I find myself copying and pasting a previous template, changing the friendly name but not the entity name and having to restart HA again. I lose data on some sensors when HA restarts, so that is another reason I try and avoid that.
It has been nice though in the last few iterations(past year maybe) that restarts don’t take anywhere near as long as they used to, so its not a chore like it was in the past.
I have so many friends who get really excited when ever I tell them about stuff I do with HA, and they always want it for their homes, too. But I know my friends, so I recommend not getting into home automation / HA. They expect things to be “plug&play” and easy to maintain and they would not understand most of the things I did to get my stuff running, and they would not want to spent that amount of time.
Maybe, when HA would become more streamlined, it would be more accessible (and less frustrating) for not so tech-savvy people.
I hope that Zigbee network + Zigbee Coordinator backups in the ZHA integration are also part of what Home Assistant founders indirectly thought about in this blog-post about “Streamlining Experiences”, especially now that Home Assistant Yellow hardware will contain a Zigbee Coordinator as standard:
We need a streamlined experience for recorder, history, and statistics. My current database file is 33gigs and I actually want a long history (currently set at 900 day purge) but probably some of it can become statistics.
There is currently no good UX for seeing and controlling MY data. I’d love to see which devices/entities are creating the most data and have control over retention down to the entity level.
Please consider streamlining the recorder/statistics into a new storage configuration screen so I can easily manage MY data.