HASSOS - Failed to initialize the driver

Hi,
First and foremost, i’m a senior Linux Sysadmin and Network Engineer since 32 years. I like Home Assistant and it worked pretty well for the last 3-4 years. Recently, Z-Wave stop working for no apparent reason. I was using the straight “ZWave JS” plugin and switched to “ZWave JS UI”. The message in log is:

Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)

HASSOS is running on my AlmaLinux 9 KVM server for the last 2 years without problem. On the KVM host, lsusb is showing correctly:

Bus 003 Device 006: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB

So this USB device is passed directly to the HASSOS VM, didn’t change anything. I have problem debugging it because all i see in the HASSOS VM with lsusb is:

Bus 003 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 002 Device 001: ID 1d6b:0001

So the USB device is not recognized of lsusb doesn’t show extended information. I read many places people using /dev/serial/… but this isn’t see inside HASSOS VM, there is no /dev/serial/…

I tried plug / unplug, change port, etc. All i can say is that KVM doesn’t fail passing USB device and installation is rock solid. My problem is that i never seen what it should look like inside the VM before today. Should lsusb show “Aotec…” like in the KVM server or it is normal it doesn’t ?

Ok, replying to myself, fooling around with plug / unplug, removing / adding the USB device for the HASSOS VM, finally the VM sees the Aeotec usb ZWave dongle. Now, in ZWave JS UI, i see i can choose between:
/dev/serial/by-id/usb-0658_0200-if00
or
/dev/ttyACM0

lsusb inside HASSOS OS still doesn’t provide extended information but i do see one more device than before (was 4 devices, now 5).