Zwave binary sensor triggered item status

bastiaan_van_h · October 4, 2022, 5:00pm

Hi,

I have a Zwave PIR binary sensor. Previously, the linked item had status ON or OFF. Currently it has one continuing status Triggered. When I link a new item, it changes to triggered once the binary sensor detects motion. The item sticks on triggered status.

Looking at the debug logs of Zwave binding the channel is updated to ON. I have no idea why the linked item keeps sticking on Triggered.

Is this somekind of change or a bug in my setup?

Things tried:

Upgrade to latest milestone openHAB 3.4.0.M2
Clean cache
New item

Any help is very welcome.

Zwave debug on PIR movement.

2022-10-04 18:52:54.122 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 31 04 30 03 FF 08 00
2022-10-04 18:52:54.122 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=49, callback=0, payload=00 31 04 30 03 FF 08
2022-10-04 18:52:54.123 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=49, callback=0, payload=00 31 04 30 03 FF 08
2022-10-04 18:52:54.123 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-10-04 18:52:54.123 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 49: Application Command Request (ALIVE:REQUEST_NIF)
2022-10-04 18:52:54.123 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 49: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2022-10-04 18:52:54.123 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 49: SECURITY not supported
2022-10-04 18:52:54.123 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 49: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
2022-10-04 18:52:54.124 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 8
2022-10-04 18:52:54.124 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is TAMPER
2022-10-04 18:52:54.124 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 49: Sensor Binary report, type=Tamper, value=255
2022-10-04 18:52:54.124 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 49: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2022-10-04 18:52:54.124 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 49: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255
2022-10-04 18:52:54.125 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 49: Updating channel state zwave:device:a5062334:node49:sensor_binary to ON [OnOffType]
2022-10-04 18:52:54.125 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 49: Commands processed 1.
2022-10-04 18:52:54.125 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 49: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@4c19a14d.
2022-10-04 18:52:54.125 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-10-04 18:52:54.125 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-10-04 18:52:54.125 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-10-04 18:52:54.125 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2022-10-04 18:52:54.147 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 31 0A 71 05 00 00 00 FF 07 03 00 00 5F
2022-10-04 18:52:54.147 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=49, callback=0, payload=00 31 0A 71 05 00 00 00 FF 07 03 00 00
2022-10-04 18:52:54.147 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=49, callback=0, payload=00 31 0A 71 05 00 00 00 FF 07 03 00 00
2022-10-04 18:52:54.147 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-10-04 18:52:54.147 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 49: Application Command Request (ALIVE:REQUEST_NIF)
2022-10-04 18:52:54.147 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 49: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2022-10-04 18:52:54.148 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 49: SECURITY not supported
2022-10-04 18:52:54.148 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 49: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2022-10-04 18:52:54.148 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 49: NOTIFICATION report - 0 = 0, event=3, status=255, plen=0
2022-10-04 18:52:54.148 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 49: Alarm Type = BURGLAR (0)
2022-10-04 18:52:54.148 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 49: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2022-10-04 18:52:54.148 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 49: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2022-10-04 18:52:54.148 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 49: Alarm converter processing NOTIFICATION
2022-10-04 18:52:54.148 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 49: Alarm converter NOTIFICATION event is 3, type OnOffType
2022-10-04 18:52:54.149 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 49: Commands processed 1.
2022-10-04 18:52:54.149 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 49: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@42bebc01.
2022-10-04 18:52:54.149 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-10-04 18:52:54.149 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-10-04 18:52:54.149 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-10-04 18:52:54.149 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

rlkoshak · October 4, 2022, 5:28pm

That’s how some motion sensors work. They just report when they are triggered but don’t “time out” and return to a non-triggered state.

Depending on what you want out of this Item you may not need to do anything. You can trigger a rule when the Item receives an ON command and that rule will trigger every time motion is detected. However, if you do need the Item to return to OFF, use the Expire Item metadata to set it back to OFF a defined amount of time after the last time an ON command is received on the Item (e.g. it will go to OFF five minutes after the last ON command is received).

bastiaan_van_h · October 4, 2022, 5:53pm

I’m using this binary sensor for a year with a attached rule that triggers on command change from OFF to ON. This worked perfectly until a month back. I now added a expiration timer to change the state back to OFF after 10 seconds. Now the rule works again. I really don’t know why the behavior of this sensor has changed, but I’m glad it works again.

Thanks!

apella12 · October 4, 2022, 6:52pm

I’m guessing the change is due to a device database update/change. You can look up the device here. Note the “last update” to see if that could be a cause.