I recently switched to zwavejs, and although it worked rather well, it currently has some limitations. So, I installed zwavejs2mqtt, combined with the zwavejs integration. It gives me far more control over the network. However, before I could read zwavejs_events to see if buttons were pushed, but this doesn’t work anymore.
I assume zwavejs2mqtt works differently, but I’m not sure where to find these events anymore. Listening to all events in Home Assistant doesn’t reveal anything about this.
4 Likes
Did anyone get any further with this? I have the same issue - Zwave works fine, can control it from HA but I can’t see ANY zwave* events in HA at all. If I subscribe to * I don’t see anything zwave related, even when nodes change state or are controlled via HA.
Any thoughts/inputs?
If I understand correctly, the setup is HA with zwavejs integration that is connected to zwavejs server via websocket and this zwavejs server is also running zwavejs2mqtt?
(BTW I don’t use this particular setup, but will try to help out…)
I would recommend turning on logs for ZWaveJS2MQTT using the GUI.
How to do this may vary depending on which version, but try:
GUI->Settings->General->Turn on “Log Enabled” (hit save and wait a while).
GUI->Debug->Start. You can see logs here.
See if the events you’re interested in show up in the log. If they do, but are not showing up on MQTT, then its possible that the MQTT setup in ZWaveJS2MQTT needs some adjustments.
Did you find a solution ?
I just migrated to zwavejs integration with Zwavejs2mqtt as backend connected via websocket, zwave works fine but I can’t get any events.
For information I use theses versions, all in docker :
zwavejs2mqtt: 6.1.1
zwave-js: 8.9.0-beta.1
When I try to trigger a event from my device, I get the log in zwavejs2mqtt :
zwavejs2mqtt | 2021-12-22 11:11:21.452 INFO ZWAVE: Node 7: value notification: 91-0-scene-001 0
But If I listen zwave_js_notification in homeassistant, nothing appears, same with listen on *, nothing about zwave
Ok just fixed.
I wanted to try to exclude/include device, but the exclusion did not exclude but repaired device… 
So it was just a migration issue for me.
1 Like