Ok, I put the batteries back on. Attached are the log files:
zwave.log (with DEBUG enabled)
openhab.log
events.log
This time, there is no Queue Full exception error, but the events still stop after some time.
The flow of events is in note1.
I’m working with a stable build, and the development zwave binding on top. I added the development binding using the steps in note2 (Should I do it differently?)
note1 - flow of events
-
Started openhab at around 2017-05-06 08:54
-
OFF/ON events coming from the HASM100 and Fibaro devices at e.g.
– node6 (Fibaro): 2017-05-06 09:01:06.496, 2017-05-06 09:12:10.579
– node3 (HSM100): 2017-05-06 09:01:46.219, 2017-05-06 09:12:10.270 -
Communication error events
– node3 (HSM100): 2017-05-06 13:14:44.666
– node6 (Fibaro): 2017-05-06 14:48:28.029
note2 - installed bundles
uninstall zwave binding from http://localhost:8080/paperui/index.html#/extensions
cd /usr/share/openhab2/addons
sudo wget http://www.cd-jackson.com/downloads/openhab2/org.openhab.binding.zwave-2.1.0-SNAPSHOT.jar
sudo chown openhab:openhab org.openhab.binding.zwave-2.1.0-SNAPSHOT.jar
openhab> bundle:list -s | grep zwave
200 | Active | 80 | 2.1.0.201704162057 | ZWave Binding | org.openhab.binding.zwave
202 | Installed | 80 | 2.0.0 | ZWave Binding | org.openhab.binding.zwave