Driver stopped working on any upgrade post version 8.22.3

[r-zlo]

Hey folks,

I'm a little stuck with the upgrade of my container zwave js ui container.
In short I've got a VM which hosts my containers and seems that the zwave js container is no longer able to see the AOTEC gen5+ ZWave USB dongle after this version.

Everything seems to work fine when I rollback to the previous version, so I don't suspect that there is any issue with the dongle, USB ports nor configuration, but happy get any suggestion.

A friend of mine, who uses the same setup also hit the same issue when tryed to upgrade a few months back, which suggest that something has changed on the driver mapping since that version that breaks the USB pass throught once the container image is upgraded.

Any help is much appreciated.

Error:

Driver: Failed to open the serial port: Error: No such device or address, cannot open /.
Driver: Failed to open the serial port: Error: No such device or address, cannot open /dev/zwave (ZW0100)
Error: Driver: Failed to open the serial port: Error: No such device or address, cannot open /dev/zwave (ZW0100)

vm-iot2:~/docker/containers/zwave$ lsusb
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
vm-iot2:~/docker/containers/zwave$

here is a snipped of my docker-compose.yaml:

version: '3.5'
services:
  zwavejs2mqtt:
    container_name: zwave
    image: zwavejs/zwave-js-ui:9.2.3
    restart: unless-stopped
    tty: true
    stop_signal: SIGINT
    environment:
      - SESSION_SECRET=XXXXXXXX
      - ZWAVEJS_EXTERNAL_CONFIG=/usr/src/app/store/.config-db

    devices:
      - '/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave' 
    volumes:
      - zwave-config:/usr/src/app/store
     
volumes:
  zwave-config:
    name: zwave-config

[robertsLando]

@r-zlo What's the output of ls /dev/serial/by-id ?

If not existing check: #3589

[r-zlo]

When I run the container with the new version (i.e. 9.2.3), it only exists on the host (i.e. outside).

host:~$ ls /dev/serial/by-id
usb-0658_0200-if00

then when I rollback to the earlier version (i.e. 8.22.3), it only exists on the VM

vm-iot2:~/docker/containers/zwave$ ls /dev/serial/by-id
usb-0658_0200-if00

it seems to be related to what @kpine mentioned on his post below but somehow it changes the behaviour depending on the nodejs version, it is presented to the VM or not.

[kpine]

Soft-reset of the controller on startup will cause a USB reset for a 500-series. A VM that is not configured properly or does not support hot-plugging of USB devices will "lose" the device. The preferred solution is to fix your VM. If that's not possible, you can disable Soft-reset in the Z-Wave settings.

[r-zlo]

Thanks, @kpine. sounds plausible.

But as I mentioned on the response to @robertsLando, it is clear to me (consistently tested multiple times) that it behaves differently depending on the version of the node js image that I load.

I'm happy to poke around on the VM settings but I'm out of my depth here. here is the I think that the XML screenshot here suggests that I've got the right configuration: managed="yes"

(the screenshot above was taken when I have the newer version of the node js running (9.2.3)

I then reverted back to version 8.22.3 (killed the container and restarted the host)... noted other couple of lines are showing probably as a result of the usb mapping to the VM.

does the above looks right from a "VM configuration" perspective? or where else should I go to check the config?

[kpine]

Sorry, I don't know how to enable USB hotplug with QEMU. After some searching, I found some articles, maybe they will help. https://github.com/tobias-/hotplug-proxmox-devices/blob/master/README.md or https://github.com/darkguy2008/hotplugger.

As I said, if you are unable to fix the VM, you can disable Soft-reset in the Z-Wave settings instead.

Newer versions of Z-Wave JS changed behavior of soft-reset, so you need to adjust. zwave-js/node-zwave-js#6341