Ring PIR Motion Sensor - Updates Item for "OFF" But not "ON"

I have a couple of Ring PIR motion sensors (https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/943#) and they seem to be identified by OpenHAB but they do not seem to correctly update the alarm channel. The binary_sensor channel doesn’t seem to do anything at all.

The alarm channel gets updated to “OFF” 3 minutes after motion stops (which is correct) but never gets updated when motion starts or when the cover is removed.

Debug log, motion starts:

2020-04-27 07:09:16.616 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 22 09 71 05 00 00 00 FF 07 08 00 5B
2020-04-27 07:09:16.626 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=34, callbac
k=0, payload=00 22 09 71 05 00 00 00 FF 07 08 00
2020-04-27 07:09:16.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=34, callback=0, payload=00 22
09 71 05 00 00 00 FF 07 08 00
2020-04-27 07:09:16.639 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-04-27 07:09:16.645 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 34: Application Command Request (ALIVE:UPDATE_NEIGHBORS)
2020-04-27 07:09:16.651 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 34: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2020-04-27 07:09:16.656 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 34: SECURITY not supported
2020-04-27 07:09:16.662 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 34: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2020-04-27 07:09:16.668 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 34: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2020-04-27 07:09:16.673 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 34: Alarm Type = BURGLAR (0)
2020-04-27 07:09:16.679 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 34: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2020-04-27 07:09:16.685 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 34: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2020-04-27 07:09:16.691 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 34: Alarm converter processing NOTIFICATION
2020-04-27 07:09:16.697 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 34: Alarm converter NOTIFICATION event is 8, type OnOffType
2020-04-27 07:09:16.703 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 34: Commands processed 1.
2020-04-27 07:09:16.709 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 34: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1985bc0.
2020-04-27 07:09:16.715 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-04-27 07:09:16.721 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-04-27 07:09:16.726 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-04-27 07:09:16.732 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

Debug log, motion stops:

2020-04-27 07:12:50.865 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 22 0A 71 05 00 00 00 FF 07 00 01 08 46
2020-04-27 07:12:50.883 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=34, callback=0, payload=00 22 0A 71 05 00 00 00 FF 07 00 01 08
2020-04-27 07:12:50.894 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=34, callback=0, payload=00 22 0A 71 05 00 00 00 FF 07 00 01 08
2020-04-27 07:12:50.903 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-04-27 07:12:50.912 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 34: Application Command Request (ALIVE:UPDATE_NEIGHBORS)
2020-04-27 07:12:50.922 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 34: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2020-04-27 07:12:50.931 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 34: SECURITY not supported
2020-04-27 07:12:50.939 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 34: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2020-04-27 07:12:50.948 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 34: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2020-04-27 07:12:50.959 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 34: Alarm Type = BURGLAR (0)
2020-04-27 07:12:50.969 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 34: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2020-04-27 07:12:50.980 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 34: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2020-04-27 07:12:50.988 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 34: Alarm converter processing NOTIFICATION
2020-04-27 07:12:50.993 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 34: Alarm converter NOTIFICATION event is 0, type OnOffType
2020-04-27 07:12:51.003 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 34: Updating channel state zwave:device:e87bab33:node34:alarm_burglar to OFF [OnOffType]
2020-04-27 07:12:51.009 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 34: Commands processed 1.
2020-04-27 07:12:51.014 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 34: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1a116c5.
2020-04-27 07:12:51.017 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-04-27 07:12:51.021 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-04-27 07:12:51.024 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-04-27 07:12:51.028 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

It almost seems like the alarm channel is not an on/off channel. In the Notification report line it appears theres 3 possibilities, 0=OK; 8=Motion; 3=Tamper state (Cover removed, not shown in above logs).

OpenHAB Version is 2.5.2 Release, zwave binding is 2.5.3.202003010815 however the last update for this device in Chris’s zwave database appears to pre-date the zwave snapshot I am running so I have not tried to update that yet.

I attached the xml file from the node referenced above. I have not done anything on cd-jackson.com yet, I am not really sure if there is anything additional needed or if I am even supposed to do anything there since the device is already listed but seems to be broken in some way.

I do know how to modify the zwave binding jar file if anyone has suggestions for changes to the thing XML files contained in there, I can pretty easily test it out.

If anyone has suggestions or can point me in the right direction that would be much appriciated! :slight_smile:

network_fd2c8ba0__node_34.xml (10.4 KB)

You provided a lot of good information! First, I expect that the sensor_binary Channel would report if the controller was added to Group 2. This would probably be a good addition to the device db, but you can also do this manually in Habmin. As for the alarm Channel, it looks like this may be misconfigured. A tamper Channel could also be added. Can you provide a log with the device being opened and closed?

I attached the logs since the cover open log entry is pretty long, hopefully makes it easier to read.

MotionSensorCoverClosed.txt (3.0 KB) MotionSensorCoverOpened.txt (11.5 KB)

Are you thinking the alarm channel is possibly misconfigured on my end or in the device database/zwave binding?

Items file:

// Test Motion Sensor
Switch  SN_TestMotion                   "Test Motion"           <motion>                                { channel="zwave:device:e87bab33:node34:alarm_burglar" }
Switch  SN_TestMotion2                  "Test Motion 2"         <motion>                                { channel="zwave:device:e87bab33:node34:sensor_binary" }
Number  SN_TestMotion_BatteryLevel      "Test Motion Battery"   <batterylevel>  (GR_SensorBatteries)    { channel="zwave:device:e87bab33:node34:battery-level" }

Sitemap:

         Text            item=SN_TestMotion                      label="test motion [%s]"
         Text            item=SN_TestMotion2                     label="test motion 2 [%s]"
         Text            item=SN_TestMotion_BatteryLevel         label="test motion batt [%s]"

I ended up restarting OpenHAB a few minutes ago and for some reason the sensor-binary channel now appears to work! “SN_TestMotion2” (the sensor_binary chan) shows ‘triggered’ or ‘untriggered’ now. SN_TestMotion (the alarm_burglar channel) always shows OK still. This is the first device I’ve added to OpenHAB that required me to restart the service, not sure if this is just a coincidence or not.

Here are the logs showing motion starting and stopping. You can see that sensor_binary is now being updated.
MotionSensorMotionStart.txt (5.2 KB) MotionSensorMotionStop.txt (5.4 KB)

Battery meter seems to work fine. I will test the other identical sensor I have in a little bit and see if its working on the sensor_binary channel now.

Thanks!

The device db Channel config. I should be able to take a look this evening (ET)… but if someone else wants to jump in, please do!