Zwave controller is going offline after update to OH2.5

Setup, Configuration and Use Installation
1

Hi all,
after my update to OH2.5 my Zwave controller is going offline in a cycle - on and off every minute. I tried the solutions from this post, but it didn’t help to far.

Any thoughts , @chris or anybody else? Thanks in advance…
Jan

  • Plattform:

    • Openhap is 2.5.1-2
    • OS is Debian 4.19.67
    • Hardware MiniATX with a IntelCeleron processor; Zwave controller is an aeotec gen5 usb stick

  • addons.cfg is auto-generated and void including only comments

  • /var/lib/openhab2/config/org/openhab/addons.config look like this after I removed pushbullet and restdocs

binding="sonos,ntp,mqtt1,http1,gpio,fritzboxtr0641,fritzbox1,exec,chromecast,network,expire1,weather1,astro,zwave,serial1"
package="standard"
persistence="rrd4j,mapdb"
remote="true"
service.pid="org.openhab.addons"
transformation="javascript,jsonpath,exec,map,regex"
ui="basic,paper,habpanel,habmin"

I’m not sure if this Zwave log helps in this case, but anyhow the first seconds seems to show the re-initiatization of the controller:

2020-01-23 00:04:51.735 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2020-01-23 00:04:56.959 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2020-01-23 00:04:56.960 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2020-01-23 00:05:57.064 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2020-01-23 00:05:57.065 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2020-01-23 00:06:32.073 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2020-01-23 00:06:37.242 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2020-01-23 00:06:37.242 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2020-01-23 00:06:42.689 [ERROR] [lmessage.RequestNodeInfoMessageClass] - Request node info not placed on stack due to error.
2020-01-23 00:07:31.799 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2020-01-23 00:07:36.908 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2020-01-23 00:07:36.909 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2020-01-23 00:08:31.471 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2020-01-23 00:08:36.589 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2020-01-23 00:08:36.589 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2020-01-23 00:09:28.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.006 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.016 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.028 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.039 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.051 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.059 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.068 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.077 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.086 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.096 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.107 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.118 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Handler disposed. Unregistering listener.
2020-01-23 00:09:29.128 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Disposing receive thread
2020-01-23 00:09:29.128 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Receive thread dispose
2020-01-23 00:09:29.128 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Disposing serial connection
2020-01-23 00:09:29.128 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Serial connection disposed
2020-01-23 00:09:29.129 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
2020-01-23 00:09:29.131 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Deactivate zwave:serial_zstick:4bd824b3
2020-01-23 00:09:31.496 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Creating ZWave discovery service for zwave:serial_zstick:4bd824b3 wi$
2020-01-23 00:09:31.497 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Active zwave:serial_zstick:4bd824b3
2020-01-23 00:09:31.498 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2020-01-23 00:09:31.559 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Initializing ZWave serial controller.
2020-01-23 00:09:31.560 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initializing ZWave Controller zwave:serial_zstick:4bd824b3.
2020-01-23 00:09:31.611 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:4bd824b3:node7.
2020-01-23 00:09:31.612 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:4bd824b3:node13.
2020-01-23 00:09:31.621 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:4bd824b3:node6.
2020-01-23 00:09:31.648 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Channel zwave:device:4bd824b3:node7:switch_binary linked - p$
2020-01-23 00:09:31.649 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Channel zwave:device:4bd824b3:node7:meter_watts linked - pol$
2020-01-23 00:09:31.651 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Channel zwave:device:4bd824b3:node7:config_decimal_param42 l$
2020-01-23 00:09:31.652 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Channel zwave:device:4bd824b3:node7:alarm_power linked - pol$
2020-01-23 00:09:31.652 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Channel zwave:device:4bd824b3:node13:sensor_binary linked -$
2020-01-23 00:09:31.650 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Channel zwave:device:4bd824b3:node7:config_decimal_param41 l$
2020-01-23 00:09:31.650 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Channel zwave:device:4bd824b3:node7:meter_reset linked - pol$
2020-01-23 00:09:31.649 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Channel zwave:device:4bd824b3:node7:meter_kwh linked - polli$
2020-01-23 00:09:31.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Channel zwave:device:4bd824b3:node13:sensor_co linked - pol$
2020-01-23 00:09:31.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Channel zwave:device:4bd824b3:node13:sensor_temperature lin$
2020-01-23 00:09:31.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Channel zwave:device:4bd824b3:node13:alarm_heat linked - po$
2020-01-23 00:09:31.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE ...
2

Check addons.config in userdata. That is usually where the invalid addon is that causes them all to reload every minute. restdocs is a big culprit because it moved locations in 2.5.x from misc to ui. If you are unsure post your addons.config here.

1 Like
3

Thanks, Bruce. My addons.config is in my first post. I removed ‚restdocs‘ and ‚Pushbullet‘, but is there more in conflict with 2.5?

4

I had the same problem last week upgrading openhabian 2.4 - 2.5, just couldn’t get it working after trying heaps of suggestions here. After several hours I decided to do a backup of the key files and set up a new openhabian and then put it back together. Apart from a minor issue with the time setting all is working well.
Maybe something to think about.

Cheers

5

Some of the v1 bindings got moved to legacy due to there being v2 ones now. Do you have legacy bindings enabled?

6

So removing of the restdocs and Pushbullet did not resolve your issue?

I might have ran into the same issue, but I did went back to 2.5M1 from my backup.
I plan to try the upgrade again, but removing restdocs before the upgrade.

1 Like
7

No, didn’t work. Meanwhile I have dumped any binding with 1.x in it. And yet the zwave controller is re-starting… :weary:

Georges suggestion of creating it from scratch is kind of my last resort, but I don’t have any ideas what else to do. Any thoughts what I could try?

8

First, be sure you have a good configuration backup.

Assuming you have a list of your addons, try uninstalling all except zwave and your UIs… Verify your addons.cfg file looks as expected.
If zwave settles down, you can start adding things back to OH.

9

After a couple of hours and still no solution, I went with @George_Whitehouse solution: backup config and start for a fresh install. My learning: plan a lot of time when you do a major update on openhab… :grimacing:

1 Like
10

I am facing the same issue. Found the error on my side. In the addons.config was misc=",restdocs". restdocs must to ui and you must delete the comma.