Open tyl0r opened 2 years ago
I've changed this channel to a motion sensor - hopefully it will resolve this problem.
Thanks Chris, I'll wait for the snapshot to build
This works as expected. Thank you very much!
I know there are probably other directions floating around somewhere but for anyone who cares to update their zwave binding, this is what worked for me. And you don't have delete all your zwave items (just the affected ones), and you don't have to re-exclude/include the zwave thing
ssh openhab
cd /usr/share/openhab/addons
wget https://ci.openhab.org/job/openHAB-ZWave/lastStableBuild/artifact/target/org.openhab.binding.zwave-3.3.0-SNAPSHOT.jar
Issue: The Alarmburglar item status is not updating when motion is detected. Does the database record need updating for this device? I'm having a similar problem described here: https://github.com/openhab/org.openhab.binding.zwave/issues/1112
Take a look at the OK.txt attachment below. It has an
Updating channel state
message whereas ALARM.txt does not. I think handleEvent() is returning null forstate
(which is causing the updating to be skipped) but I'm not sure: https://github.com/openhab/org.openhab.binding.zwave/blob/3.2.0/src/main/java/org/openhab/binding/zwave/handler/ZWaveThingHandler.java#L1441It looks like
alarm_burglar
channelType case (in the switch statement within thehandleNotificationReport
method) falls to thedefault
case block. I'm not certain but I think the issue is somewhere in thedefault
case block: https://github.com/openhab/org.openhab.binding.zwave/blob/dcc155dc7e2bb5c72d9170aa0b59be136b8a5b90/src/main/java/org/openhab/binding/zwave/internal/converter/ZWaveAlarmConverter.java#L362I'm happy to test any changes.
tyl0r
ALARM.txt OK.txt
network_f66344c2__node_5.xml.txt