This is not a great advertisement for Home Assistant. The writing is also not good like some point. I am on my third iteration of HA, I regularly update it, so

This is not a great advertisement for Home Assistant. The writing is also not good like some point. I am on my third iteration of HA, I regularly update it, so I also read the release notes that the author prepares/publishes. HA feels like a broad church that caters to many users' integration needs. Lots of plugins that are supported as part of the core, fancy ways to create dashboards (admittedly I still struggle beyond the basics, and maybe I want automation and not dashboards). It's one thing to write in the release notes about the fancy new features being added to dashboards, and another to actually use them as the lead developer. I personally wouldn't have posted that as my best/most used dashboard, because that signals that you don't really use your product. There's a time when I led a team building a product, and my sermon to the team was that we should always be the superusers of our product because we'll be the first people to notice issues, our clients would look to us for support and we can't correctly build what we don't understand. I don't get a sense of that from this post. It's not even about having a well oiled automation/assistant (as you're not the only one using devices in the house like you correctly point out), but find a subset of your devices in the instance you want to use, and produce something you want to regularly tell the world about. Else we'll keep getting frustrated with HA until the big beans eventually catch up. My 18 month toddler can do things with Google Home, she knows where to press to turn on the lights she can't reach. She fumbles her way around "he gugu". That's a good experience for someone who can't yet form sentences. Even with the best devices, I doubt I'd get her to that proficiency with HA. Yeah, it's been the year of voice, but it feels complicated at a distance, I'm not even bothering with it.