After updating to the latest version of zwavejs2mqtt I got some very strange behavior from HA. After looking at the logs I did find out that I did run the zwavejs2mqtt and zwavejs addons at the same time. So far this wasn’t a problem and I even did think that’s necessary. But since I updated both addons they can’t anymore access the serial port to the USB-stick in parallel.
I did need to restart my Raspi to finally be able to disable the Z-Wave JS addon and running with zwavejs2mqtt only. Frankly I don’t know why it did start working again, but eventually someone else have a similar experience and can clarify this issue.
Z-Wave JS to MQTT
Current version: 0.38.0
zwavejs2mqtt: 6.7.2
zwave-js: 9.0.2
I would remove the z-wave js and just roll with the zwave js to mqtt and verify your serial path to the usb stick. make sure the config in zw2mqtt reflects the accurate path then reboot
Yesterday’s update whacked the USB port in my HA virtual machine. I’m running HA in a VM on my Synology, and a known gotcha is that the USB port gets disconnected from a VM if that VM is powered down. Never saw it happen during a reboot, though.
My only guess is that this update sends a USB unmount/eject command for the Z-Wave stick, and the port remains disconnected until the computer is power-cycled (or the USB port re-attached to the VM)…
I now think that the key issue to make it working again was to be able to reconnect the Z-Wave JS integration to the zwavejs2mqtt addon. Even it is the same URL, after doing the reconfiguration my z-Wave entities where all coming back.
