Ya’ll really should pay attention to things outside these blog posts instead of making assumptions based on the blog post. You’ll learn more about the future plans of dashboards.
The blog posts just covers what’s in this release. You’re making speculations about the future of this feature without watching the live streams that cover the future of this feature. Area dashboard won’t be the only auto generated dashboard.
Thank you, yes, I was making assumptions based on what I’d read in the release post and here. I stand corrected.
In fairness, there are only so many hours in a day, and I already devote far too many of them to tweaking and monitoring HA, and reading about it here. Watching a video on it hasn’t risen to the top of my priority list quite yet. Life gets in the way sometimes.
Quick update: with 2025.4.2 the memory issues are gone, all back to normal. The release notes gives no clue as to what was the cause, but I’m happy it has been solved
If anyone has feedback about the future of the automated dashboards, please feel free to discuss those concerns in the Announcing State of the Open Home 2025 blog post.
For full disclosure, I removed many off topic comments unrelated to this release. If your post was deleted, send me a PM and we can work on getting it reinstated over on the Announcing State of the Open Home 2025 blog post.
Has anyone else noticed their annual energy dashboard stats have changed after this update?
I happen to have extracted my annual data of 2024 before the update. And now the total grid import and export numbers are different compared to before the update.
But no records have been added to the previous year I assume.
I think we need to be able to use “agent_id” at the very least and ideally “conversation_id” as well with start_conversation. For example we might have a greeter agent that uses the extra_system_prompt to address the guest and the default system prompt / conversation agent may struggle with that. It would be nice to use a custom conversation agent with a custom prompt to handle guest interactions (just an example!).
I do not understand the dislike for areas. Outside of HA there are areas in my house that I name. At a point in time, each device is in one of those areas. I think this is really important. To me the area of a device is an attribute of the device. Some devices don’t move - an hardwired outlet - and some devices constantly move - a phone. I think areas would be greatly improved if I could define them and HA could dynamically figure out where each device is. One thing that could help this is if HA knew how areas connected. That way it would have a better idea of where each device is.
The bottom line is I like areas and hope that HA does more with them, not less.
Areas are great. I totally support improving and expanding their use. They can be used lots of different ways. Versatility is one of the great things about HA.
I don’t happen to use them currently, but that’s just one person. My only point is to consider the new user. Are they going to understand all the great things you can do with areas? Are they going to have a well-thought-out strategy for assigning devices to areas? Are they even going to have enough devices to develop that strategy?
All of which has already been said here, along with the fact that the focus on areas is just one direction the new default UI is going to offer. So it’s sort of a moot point now.