I'd like to give kudos to Hubitat from moving away from their in house ZWave stack to ZWave-JS (Open Source). I also like that they are focusing their energy on their value add which IMHO is the UI and Rule Machine. I'd like to encourage them to continue the move away from other in-house code and adapt more open source projects and stacks which are just as good or better. Free up the engineering organization to focus on your true strengths and away from commoditized functionality. Best Regards. Well done.
Z/ip gateway was not in-house.
2 Likes
regardless, I hope the true intent of my opinion came through anyways. 
I'm sure this has been debated internally many times. Just wanted to tip my hat of approval.
I personally now only use Hubitat for the UI, Dashboards, and Rule Machine. I dont use any Z-Wave or Zigbee drivers from Hubitat. I have converted everything to MQTT and have written all the Hubitat drivers to control and get status from Z-Wave and/or Zigbee devices via MQTT. In fact, my Z-wave and Zigbee radios are completely off on the hub.
Just so you don't get shocked some time in the future, technically your radios are ON. But the Hub's platform OS (and either Z/IP or ZWaveJS) are blocked from sending commands. It's a tiny detail, but if you were to put two hubs on top of each other, thinking there's no way to interfere because one has the radios off... I'm saving you half a day's puzzlement. 
5 Likes
thanks for the heads up. I appreciate that. I'll go put it in a metal box in a dark hole someplace with just power and ethernet.
1 Like
