No, this is not normal. Zwavejs2mqtt is losing connection to the zstick. It is likely momentary and re-establishes it, which would explain why things are working for you.
However, it will likely cause issues if you don’t get to the route of the problem and fix it. If you post your install type - including how you installed Home Assistant, and what system/hardware it is running on, that could help with diagnosing where the connection could be failing.
Also are you using the community addon of zwavejs2mqtt or running it some other way (ie docker)?
using zwavejs2mqtt. Running The HA-OS install in a VM. Was presenting the USB stick… now after I rebooted everything the HA-OS is not even seeing the Aeotec stick.
I’ve read and searched for so many answers. Can’t seem to get the HA-OS to detect it or set it up properly.
DMESG shows this which is the proper stick, but it never creates /dev/ttyACM0 like it used to:
[ 1.786752] cdc_acm 2-2:1.0: ttyACM0: USB ACM device
[ 1.832119] usbcore: registered new interface driver cdc_acm
[ 1.871249] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Running the linux VM, Host is Unraid KVM Platform. This has been running fine for a few weeks, but after rebooting can’t seem to get the USB stick to appear in /dev
This is what I get when I plug the device in:
[ 153.984033] usb 1-2: new full-speed USB device number 3 using xhci_hcd
[ 154.111923] usb 1-2: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[ 154.111926] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 154.115962] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 154.116317] usbcore: registered new interface driver cdc_acm
[ 154.116318] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 156.653965] usb 1-2: USB disconnect, device number 3
It connects and then immediately disconnects. I can get the device to work in a win10 VM on the same Unraid, and can get it running in a docker, so I know it’s not the USB ports or the device. Something in the HA-OS causing it to immediately disconnect.
interesting… I have rebuilt an entirely new HA-OS and the USB device stays mapped and is accessible until I install the zwavejs2mqtt, once I enable this and point it to the /dev/TTYACM0 it crashes the /dev/TTYACM0.
If I configure zwave2JS, it has no issue. So it seems maybe a the updated version is broken? How do I revert to a prior version?
The newer versions of ZWaveJS2MQTT (and indeed ZWaveJS) do have a note on the releases page that they now “soft reset” the stick before starting, and this may not be compatible with all sticks.
confirmed that unchecking soft reset fixes the disappearing stick. (Aeotec zStick Gen5+)
What a darn day it has been tracking this bug down. I can also confirm now that by converting to /dev/serial/by-id/xxxxxx solves the original post of retry connection.
