When I first started my journey into Home Automation, I wanted an appliance that could be easily hackable. From my research, Vera seemed the best answer.
I didn’t wanted to hack things too much, since my wife could probably kill me if I left her in dark or things like that (since I travel 50%+ of my time and I live between two cities each at 800 km from the other - but that’s another story and I’m not sure I will continue this way after this COVID situation). But, with Vera, I ended up writing a lot of code to normalize its weirdness and quirks.
So, if I have to write code and have a system that’s not an appliance, maybe choosing my own components is a better choice. If complete compatibility and an easy transition path are on the plate, I’m more than happy to follow this route. My only blocker is that I invested too much into Nests thermostats, my wife likes it, the interior designer that’s in me can’t like other solutions - and I have probably to run a Vera just to have the plug-in running and bridged to openluup - at least until Nest sort things out and it’s out with a new API for integrations.
I’m also exploring a couple of ideas where I can add a C# module/application to openluup and have them integrated beyond HTTP. We’ll see.
I’ll take a look at the new Linux firmware because why not, but I’m not impressed at the moment. With all that said, I think this situation with Z-wave outstanding problems not fixed in the current firmware will force a lot of people go to different platform and never look back. If I was in the dev team, I’d have put more support into this, to keep the current user base loyal. To be honest, they tried this summer, but they’re now vanished, feedback is ignored and transparency has ceased, so we’re basically left behind - like before eZlo took over. Who could assure me that this will not happen again, let’s say, in 3 years with the new firmware?