GE/Jasco Motion Switch (26933) Not Receiving Motion Events

I have the device https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/740, and I’ve linked the alarm_burglar channel on endpoint two to an item:

Switch GuestBathLights_Contact "Guest Bathroom Lights Occupancy" { channel="zwave:device:512:node43:alarm_burglar2" }

When I turn on debug logging, I see that the device is sending a notification when I trigger it:

2019-03-06 17:12:54.697 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 04 00 2B 0D 60 0D 02 01 71 05 00 00 00 FF 07 08 00 24 
2019-03-06 17:12:54.697 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 0D 60 0D 02 01 71 05 00 00 00 FF 07 08 00 
2019-03-06 17:12:54.697 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 0D 60 0D 02 01 71 05 00 00 00 FF 07 08 00 
2019-03-06 17:12:54.698 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-03-06 17:12:54.698 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Application Command Request (ALIVE:DONE)
2019-03-06 17:12:54.698 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: resetResendCount initComplete=true isDead=false
2019-03-06 17:12:54.698 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2019-03-06 17:12:54.698 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Incoming command class COMMAND_CLASS_ALARM, endpoint 2
2019-03-06 17:12:54.698 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: SECURITY not supported
2019-03-06 17:12:54.698 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2019-03-06 17:12:54.698 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 43: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2019-03-06 17:12:54.699 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 43: Alarm Type = BURGLAR (0)
2019-03-06 17:12:54.699 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-03-06 17:12:54.699 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got a value event from Z-Wave network, endpoint=2, command class=COMMAND_CLASS_ALARM, value=255
2019-03-06 17:12:54.699 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 43: Alarm converter processing NOTIFICATION
2019-03-06 17:12:54.699 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 43: Alarm converter NOTIFICATION event is 8, type OnOffType
2019-03-06 17:12:54.699 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Commands processed 1.
2019-03-06 17:12:54.699 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@f6bf976.
2019-03-06 17:12:54.700 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-03-06 17:12:54.700 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-03-06 17:12:54.700 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

But it doesn’t update my item. Shortly after I get the update on the dimmer part itself, and that works fine:

2019-03-06 17:12:54.721 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 2B 07 60 0D 01 01 26 03 63 F1 
2019-03-06 17:12:54.721 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 07 60 0D 01 01 26 03 63 
2019-03-06 17:12:54.721 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 07 60 0D 01 01 26 03 63 
2019-03-06 17:12:54.721 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-03-06 17:12:54.722 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Application Command Request (ALIVE:DONE)
2019-03-06 17:12:54.722 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: resetResendCount initComplete=true isDead=false
2019-03-06 17:12:54.722 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2019-03-06 17:12:54.722 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Incoming command class COMMAND_CLASS_SWITCH_MULTILEVEL, endpoint 1
2019-03-06 17:12:54.722 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: SECURITY not supported
2019-03-06 17:12:54.722 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Received COMMAND_CLASS_SWITCH_MULTILEVEL V2 SWITCH_MULTILEVEL_REPORT
2019-03-06 17:12:54.722 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 43: Switch Multi Level report, value = 99
2019-03-06 17:12:54.722 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-03-06 17:12:54.723 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got a value event from Z-Wave network, endpoint=1, command class=COMMAND_CLASS_SWITCH_MULTILEVEL, value=99
2019-03-06 17:12:54.723 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Updating channel state zwave:device:512:node43:switch_dimmer1 to 100 [PercentType]
2019-03-06 17:12:54.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Commands processed 1.
2019-03-06 17:12:54.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@459188bd.
2019-03-06 17:12:54.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-03-06 17:12:54.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-03-06 17:12:54.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

@chris Is this another case similar to [SOLVED] GE/Jasco ZW6302 (34193) zwave motion sensor events ignored where the database just needs a slight tweak to use alarm_motion rather than alarm_burglar?

Yes, and I see you’ve updated the database already - I think it looks fine but I will double check when I do the export.

Thanks.

I had added a channel so that I can change it’s mode from rules, but hadn’t touched the alarm channel yet.

Ok, someone updated it, but it doesn’t seem to be listed in the change log…

image

This change is still pending, and I think it will resolve the issue.

Awesome, I’ll try it out when I see the db has been exported, and in a new snapshot. Thanks.