Yep, will probably give it a go on Monday if I can contain the excitement till then Updating 2 HASS installs is OK from my point of view because the plan is to keep one with ZWave, MQTT and literally nothing else, so that I’d only need to look out for ZWave breaking changes.
I will definitely be using this opportunity to create a 3rd VM, though, finally a DEV/TEST environment with all hardware accounted for!
Anybody know if zwave2mqtt can handle double taps? Like I have a few automations that run on double taps on my light switches. If not, guess my best best is statestream
Right now I’m bashing my head against a wall with mqtt_statestream and mqtt_discovery not seeming to want to play nicely with each other. But yeah, if zwave2mqtt is “easier” i might be tempted.
I think it was on Reddit, but the developer said he just released a version of Zwave2MQTT that supported Home Assistant MQTT discovery. It sounded like more of a beta version, but worth checking out.
@abalakov, I tried doing what you suggested above, except for the fact that my user is named “MQTT” instead of “mqtt” (I am re-using it from another integration that I already had for a Raspberry Pi Monitor client), now I have a switch on the slave system that is set to Unavailable, any idea if I must name the user “mqtt” specifically?
@abalakov, never mind that question, I have another
I realized I hadn’t included the zwave entity alongside the switch, corrected that and now it can be seen in the slave HA!
Just one issue remains, I can’t control it from the slave system. I can see the state changes, control it from the master system, but it ignores on/off from the slave system.
I used the exact code you gave above and am assuming the command_topic: “ha_master_topic/switch/myswitch/set” is what is not working for me at the moment…
OK, so I’ve made some progress in the sense that I’ve forwarded a dozen ZWave switches to the new instance via MQTT, buuuut, the switching from the slave system is not 100% functional…it seems to set the switch, but doesn’t update the state on the slave system…it shows the state correctly all the time if I use the switch on the master system.
Any ideas? (or rather, has this happened to anyone else?)
I think in your guide a couple of more details need to be given as to where the MQTT statestream and discovery components need to be inputted, because it’s not clear if they should be on the main system, on the zwave system, or both. Can you please elaborate that part a bit?
After following part of your guide discovery seems to be working for my switches, but I still wouldn’t say reliability is perfect…it seems a bit better than with my previous config, but I still seem to have introduced some extra “wonkiness” vs. just using the zwave switch directly, not all of them update every time.
In case you haven’t seen it. There is a custom component that is much more elegant than mqtt based stuff. It grabs the states from one or more remote HA instances and forwards local service calls to the remote instance.
I’d prefer zwave2mqtt if it worked well. However, it does not support all device types. thermostats are, for example, rather tedious because they need a special config and don’t work out of the box. For some of them, this config has been shared in github issues or here on the forum, but it looks like a pain to create this from scratch.
Having another HA instance running is a lot of overhead, but you can pull out not only zwave related stuff but other features as well. This allows you to have dedicated instances for different RF standards or have redundancy.
I have just migrated my main instance to a VM and my zwave and Zigbee stuff to a pi. Zigbee works great with deconz but still don’t feel fully confident in zwave2mqtt ability not to crap out on me and cause me a massive headaches.
I have been using this for close to 2 years. It works perfectly for me. I installed it around HA .90 version days and it has continued to work flawlessly for me up to 0.102.3
I use multiple raspberry Pi installs with zwave sticks around my large home that all then report to a central hassio install running on a NUC (over 1000 zwave devices) I can’t praise this plugin enough!