I have a new LZW60 motion sensor from Inovelli. I’m using the SNAPSHOT zwave binding 2.5.2.202002180542. Things are working great (mostly) for the temperature, humidity, and luminance. My problem is that the alarm_burglar channel seems to only receive an OFF state. I have a rule that works well detecting motion with a different brand of sensor that uses the alarm_motion channel that toggles from OFF to ON when motion is detected, but with the Inovelli using the alarm_burglar channel, I do not see the channel toggling back and forth between on and off. All I see is an OFF update at the item bound to the channel when motion occurs. Is there something I’m missing?
Very like this thread
Can you provide a debug log showing exactly what it does send and we can take a look.
See the binding docs for how to configure this.
1 Like
openhab.log (931.6 KB)
Node 19 is the problem child. I think it does look similar to the problem @rossko57 referenced. Thanks for taking a look, @chris.
I figure Chris is probably slammed with stuff right now so I’m not pushing but just figured I’d do some troubleshooting. Here is what I’ve found after comparing this device to a motion detector that is working with OH.
The “working” node log:
27-Mar-2020 16:39:53.909 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 22: Application Command Request (ALIVE:DONE)
27-Mar-2020 16:39:53.910 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 22: resetResendCount initComplete=true isDead=false
27-Mar-2020 16:39:53.910 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 22: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
27-Mar-2020 16:39:53.910 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 22: SECURITY NOT required on COMMAND_CLASS_ALARM
27-Mar-2020 16:39:53.911 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 22: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
27-Mar-2020 16:39:53.911 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 22: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
27-Mar-2020 16:39:53.911 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 22: Alarm Type = BURGLAR (0)
27-Mar-2020 16:39:53.912 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 22: Got an event from Z-Wave network: ZWaveAlarmValueEvent
27-Mar-2020 16:39:53.912 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 22: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
27-Mar-2020 16:39:53.913 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - NODE 22: Alarm converter processing NOTIFICATION
27-Mar-2020 16:39:53.913 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - NODE 22: Alarm converter NOTIFICATION event is 8, type OnOffType
27-Mar-2020 16:39:53.914 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - NODE 22: Alarm converter processing NOTIFICATION
27-Mar-2020 16:39:53.914 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - NODE 22: Alarm converter NOTIFICATION event is 8, type OnOffType
27-Mar-2020 16:39:53.914 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 22: Updating channel state zwave:device:d5395f3c:node22:alarm_motion to ON [OnOffType]
27-Mar-2020 16:39:53.915 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 22: Commands processed 1.
Here is the LZW60 log:
27-Mar-2020 16:42:25.546 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 49: Application Command Request (ALIVE:DONE)
27-Mar-2020 16:42:25.547 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 49: resetResendCount initComplete=true isDead=false
27-Mar-2020 16:42:25.547 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 49: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
27-Mar-2020 16:42:25.547 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 49: SECURITY NOT required on COMMAND_CLASS_ALARM
27-Mar-2020 16:42:25.548 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 49: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
27-Mar-2020 16:42:25.548 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 49: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
27-Mar-2020 16:42:25.548 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 49: Alarm Type = BURGLAR (0)
27-Mar-2020 16:42:25.548 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 49: Got an event from Z-Wave network: ZWaveAlarmValueEvent
27-Mar-2020 16:42:25.549 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 49: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
27-Mar-2020 16:42:25.549 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - NODE 49: Alarm converter processing NOTIFICATION
27-Mar-2020 16:42:25.549 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - NODE 49: Alarm converter NOTIFICATION event is 8, type OnOffType
27-Mar-2020 16:42:25.550 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 49: Commands processed 1.
27-Mar-2020 16:42:25.550 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 49: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@b638e3.
27-Mar-2020 16:42:25.601 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 49: Application Command Request (ALIVE:DONE)
27-Mar-2020 16:42:25.601 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 49: resetResendCount initComplete=true isDead=false
27-Mar-2020 16:42:25.602 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 49: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
27-Mar-2020 16:42:25.602 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 49: SECURITY NOT required on COMMAND_CLASS_ALARM
27-Mar-2020 16:42:25.602 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 49: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
27-Mar-2020 16:42:25.603 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 49: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
27-Mar-2020 16:42:25.603 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 49: Alarm Type = BURGLAR (0)
27-Mar-2020 16:42:25.603 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 49: Got an event from Z-Wave network: ZWaveAlarmValueEvent
27-Mar-2020 16:42:25.603 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 49: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
27-Mar-2020 16:42:25.604 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - NODE 49: Alarm converter processing NOTIFICATION
27-Mar-2020 16:42:25.604 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - NODE 49: Alarm converter NOTIFICATION event is 8, type OnOffType
27-Mar-2020 16:42:25.605 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 49: Commands processed 1.
The only difference I see is that the “working” one has:
COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT at Line 5
and updates the Channel state at line 14.
Whereas the LZW60 has:
COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT at Line 5
and DOES NOT update the Channel state (until it turns off).
I don’t know how to code in JAVA but I figured this may be useful to someone or Chris when things settle down.
It may be worth opening an issue on GitHub. Things get lost here.
Thanks Bruce, that’s good advice. Before I did that I checked the above linked forum post and it looks like it was fixed in the binding. I upgraded to 2.5.4 and it is working after deleted the thing and node xml.
Both of my devices have motion working now.
1 Like
I also got things working after deleting the thing and node.xml and re-adding the thing. Thanks all!
1 Like