Sorry, I just have to interject on this one. One of the reasons I stopped using HomeAssistant is that it seemed every fourth of fifth release contained breaking changes that sent me scrambling to fix automations, or UI, or something. I routinely found things that didn’t work as documented in both core and components. On top of this, component updates are inconsistent: some fast, some slow, some good, some bad. There are currently 822 open issues in Github for Hass. The development team fixes things when they feel like it. Balloob lords over everything. In several cases past, where several users pointed out completely conflicting behavior vs the documentation, it took months to get fixes, and a few issues that I participated in are even today not yet fixed. Patches abound, and often are lost and need to be redone, or are invalidated completely and need to be reconceived, by core updates. And among many of the component developers with whom I had interaction (including pyvera, the library used to connect HA to Vera), things were often regarded as “working good enough” and there was little that could be done to motivate the improvements necessary to make things right (for reference, the lead developer of pyvera even told me he doesn’t really use Hass himself, he just uses his library for his own stuff, so Hass is a secondary customer in his world).
I would not say that’s leaps and bounds better than Vera. At best, it may be on similar footing. But I never even came close to getting my Hass automations as deep and as reliable as what I can do on Vera (eating my own dog food–I use my own plugins, so I know if I can get done what I need, so can this community, or I’ll fix it).
You know that you and I agree completely on a fast release cycle; we’ve discussed that many times, so no argument there at all. And yes, adamantly, 7.0.30 has become a perfect example of why they must.
But I would not hold up Hass as a shining example of software quality, and I would not be happy if Vera’s release behavior was like that of Hass.
Hass is a community-developed product. It literally has +1,600 contributor who have made contributions at various levels, some continuously, some just once. This type of product naturally will have a lot more discussion. It also runs on a variety of OSs, and a larger variety of hardware, and with several different Z-Wave sticks and other connectivity components. So naturally, there’s going to be a lot more questions. There’s also going to be a lot more problems. So they have a lot to talk about.