I just want to chime in that I’m also very much looking forward to the voice hardware. I can relate to much what I’m reading about the choice of wake word, I really hope that will be easy to change or choose another one. 
3 Likes
Yes, same with zwave js. That started external and grew past their own implementation so in time their own implementation was dropped and zwave js became the official one. Right?
1 Like
If the maintainer of the integration WANTS to be in core is step 1. HA cannot go and suck up people’s projects… Besides the fact they don’t have enough core paid Devs to do everything already.
Im fine with Z2M and Domo and all the other zigbee integrations (i think there’s at LEAST three now) being options.
I personally use Z2M myself and am fine with ZHA being the one of choice.
Openzwave made way for ZWaveJS as far as I understand because ZWaveJS was actively being maintained and brought up to modern needs while OZW wasn’t so. There was a need…
Here you have two or more perfectly good ways and one is well maintained in Core and one is well maintained out of core.
Pick which works best for you.
2 Likes
I’ll just come out and say it. The voice hardware will sell no matter what. This very much feels like a vocal minority. Nobody liked Google or Alexa or Siri on launch this isn’t any different. Sure you can ask people and they will say they hate it. Hell you get people complaining about hey vs ok after all these years. After some voice commands that all goes away. Also correct me if I’m wrong but the team never said no not going to happen right? So what’s the problem lol?
2 Likes
I think you’re making incorrect assumptions. I
both have some concerns about how the wake word decision was made, and will also buy several of the voice hardware.
1 Like
Having just committed my first blueprint (I’d made some in the past for myself only), I can agree with the issue about making blueprints easier to use.
I think a major part of that is having some built-in way to package multiple elements in a blueprint. Because some automations need to read and write data to helpers in order to circumvent the limited scope of variables within an automation, or you would want to split up long code that you need to use often into separate scripts that can be called from the main automation with certain parameters/fields.
A framework that would allow such things within the blueprint yaml, or a way to package the helpers and scripts together with the blueprint would make it easier to write and use blueprints IMO.
2 Likes
I am incredibly happy about the fact the privacy and user segmentation will soon be in the focus. I find this to be the only thing thats really missing in HA which is such a great system. I love the work on sections. I think the integrations (not problem of HA) should deserver more attention from developers. But it will come HA is bitcoin (gold is about to be overtaken, gold standard will be over) standard of IOT platforms
4 Likes