Z wave stops working after some time

Setup, Configuration and Use Runtime
1

  • Issue of the topic: After some time my z wave network doesn’t work anymore. I dont see any messages in the log when the sensor states change, I.e. I open a window . When I reboot the system it works again

  • If logs where generated please post these here using code fences:

Those are the only z wave related messages I see

Connecting to 192.168.0.4 port 22, please wait...
login as: 
osmc@192.168.0.4's password: 
Linux osmc 4.14.34-6-osmc #1 SMP PREEMPT Thu Sep 6 00:47:56 UTC 2018 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Oct 16 21:41:52 2018 from 192.168.0.24



tail -f /var/log/openhab2/openhab.log
2018-10-16 21:51:14.996 [DEBUG] [rnal.converter.ZWaveBatteryConverter] - NODE 8: Generating poll message for BATTERY endpoint 0
2018-10-16 21:51:14.999 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 8: Creating new message for application command BATTERY_GET
2018-10-16 21:51:15.005 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Message already on the wake-up queue. Removing original.
2018-10-16 21:51:15.008 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Putting message SendData in wakeup queue.
2018-10-16 21:51:15.012 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Message already on the wake-up queue. Removing original.
2018-10-16 21:51:15.016 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Putting message SendData in wakeup queue.
2018-10-16 21:51:15.019 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Message already on the wake-up queue. Removing original.
2018-10-16 21:51:15.023 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Putting message SendData in wakeup queue.
2018-10-16 21:51:15.028 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Message already on the wake-up queue. Removing original.
2018-10-16 21:51:15.031 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 8: Putting message SendData in wakeup queue.
2

Well that log just shows OH trying to talk to battery devices.
You would need to show the part of the log around the time where your system stops working.
You also fail to mention the OH version and OS you run on and debug settings you used.

PS: you run OH on top OSMC ? Bad idea as that’s an appliance that is likely to interfere with OH.

3

Yes currently running osmc. At I dont need the media center anymore i wanted to change the OS anyhow. Which one do you recommend for raspberry? Rasbian?

I’ll add the debug settings, I guess I have to change to just zwave logging and wait for the failure to happen again. In the current logs I am not sure if I’ll find the point when zwave stopped

4

Use the openHABian image, it’s by far the easiest way on the pi

5

openHABian. Migrate and re-discover your ZWave devices, enable permanent ZWave debugging and see if the problem persists.