Zwave controller offline (after system upgrade?)

Add-ons Bindings
1

Hi,

my zwave setup stopped working (i.e. Razberry controller offline), maybe (?) caused by the latest system upgrade which included some bluetooth related update but this is just guessing.
Seeing the controller offline I again disabled the serial port and moved bluetooth to miniUART via option 35 in openhabian-config (RPi4) but it seems something else is broken.

The log below shows some zwave details right after a reboot:
No idea what to do now? I have been using openhab for some years but am no expert to solve issues related to hardware/linux/openhab/zwave.

Thank you for any help.

2021-05-28 15:04:27.635 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Creating ZWave discovery service for zwave:serial_zstick:d6cc7170 with scan time of 60
2021-05-28 15:04:27.637 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Active zwave:serial_zstick:d6cc7170
2021-05-28 15:04:27.639 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2021-05-28 15:04:27.872 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Initializing ZWave serial controller.
2021-05-28 15:04:27.874 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initializing ZWave Controller zwave:serial_zstick:d6cc7170.
2021-05-28 15:04:27.961 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node18.
2021-05-28 15:04:27.966 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node21.
2021-05-28 15:04:27.966 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node20.
2021-05-28 15:04:27.969 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node22.
2021-05-28 15:04:27.993 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node8.
2021-05-28 15:04:27.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node19.
2021-05-28 15:04:28.000 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node14.
2021-05-28 15:04:28.009 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node10.
2021-05-28 15:04:28.079 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node13.
2021-05-28 15:04:28.081 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node15.
2021-05-28 15:04:28.086 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node11.
2021-05-28 15:04:28.106 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node5.
2021-05-28 15:04:28.108 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node17.
2021-05-28 15:04:28.117 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node16.
2021-05-28 15:04:28.139 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node7.
2021-05-28 15:04:28.145 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node6.
2021-05-28 15:04:28.178 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node3.
2021-05-28 15:04:28.179 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node9.
2021-05-28 15:04:28.182 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node2.
2021-05-28 15:04:28.203 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:d6cc7170:node4.
2021-05-28 15:11:32.820 [DEBUG] [g.zwave.internal.ZWaveConfigProvider] - No bridgeUID found in getConfigDescription thing:zwave:serial_zstick:d6cc7170
2021-05-28 15:16:23.320 [DEBUG] [g.zwave.internal.ZWaveConfigProvider] - No bridgeUID found in getConfigDescription thing:zwave:serial_zstick:d6cc7170
2021-05-28 15:16:23.359 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Disposing receive thread
2021-05-28 15:16:23.361 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Receive thread dispose
2021-05-28 15:16:23.362 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Disposing serial connection
2021-05-28 15:16:23.363 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Serial connection disposed
2021-05-28 15:16:23.365 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
2021-05-28 15:16:23.366 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Initializing ZWave serial controller.
2021-05-28 15:16:23.367 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initializing ZWave Controller zwave:serial_zstick:d6cc7170.
2021-05-28 15:16:23.759 [DEBUG] [g.zwave.internal.ZWaveConfigProvider] - No bridgeUID found in getConfigDescription thing:zwave:serial_zstick:d6cc7170

2

same problem - help needed

3

No idea what this problem is. I had to pull out my 3.01 SD image backup to flash the SD. Then did all system updates via aptitude except for the Bluetooth stuff. All is fine now but I wonder if the Bluetooth update is really the issue…? So far I held it in its installed version.

4

This allowed my controller to come online:

[SOLVED] OH3: zwave binding Z-Wave Serial Controller Aeotec Z-Stick Gen5 remains offline

1 Like