I have an issue with my Aeotec gen 5 Z-wave stick which has stopped working after I upgraded from OH 3.0.x to 3.1 recently. And I need help getting it working again.
Here is a debug log of the binding (and the serial binding) when I enable my z-wave thing:
2021-07-10 15:45:47.469 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Creating ZWave discovery service for zwave:serial_zstick:ebf2caa1 with scan time of 60 2021-07-10 15:45:47.475 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Active zwave:serial_zstick:ebf2caa1 2021-07-10 15:45:47.475 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null 2021-07-10 15:45:47.489 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:serial_zstick:ebf2caa1' changed from UNINITIALIZED (DISABLED) to INITIALIZING 2021-07-10 15:45:47.492 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Initializing ZWave serial controller. 2021-07-10 15:45:47.493 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initializing ZWave Controller zwave:serial_zstick:ebf2caa1. 2021-07-10 15:45:47.494 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:serial_zstick:ebf2caa1' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline 2021-07-10 15:45:47.499 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:ebf2caa1:node2' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING 2021-07-10 15:45:47.502 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:ebf2caa1:node2. 2021-07-10 15:45:47.503 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:ebf2caa1:node2' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline 2021-07-10 15:45:52.495 [DEBUG] [ort.serial.internal.RxTxPortProvider] - No SerialPortIdentifier found for: /dev/ttyACM0
I am running OH on Ubuntu 20.04.2 LTS which is running inside a virtual machine powered by VMWare ESXI. The OS does see the USB stick… running lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 005: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 002 Device 004: ID 1cf1:0030 Dresden Elektronik VMware Virtual USB Mouse Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
The serial port
/dev/ttyACM0 also exists.
Additional Java options inside of
/etc/default/openhab are also configured:
Similar thing happened to me soon after I upgraded OH from 2.5 to 3.0. Back then I solved the issue by doing this:
Add the following line to the
legacy.conf(as I said previously mine didn’t have
d /run/lockline in it):
d /run/lock 0775 root dialout -
And then copy the legacy.conf to
cp /usr/lib/tmpfiles.d/legacy.conf /etc/tmpfiles.d/
I checked and this fix is still in place and OH is part of the dialout group (and checking the permissions on /dev/ttyACM0 it is owned by the dialout group. This fix worked just fine for months after I applied it.
I am at a loss in what else to do anymore. Can anyone help?