I am using an AEOTEC hub and added a TriSensor.
It was working great yesterday, My biggest application for the tool is Motion and it was great.
Today, it is no longer working, despite the temperature, battery and luminosity are reporting. The motion alert never hits. The Motion Alarm is never set on (hence my rule never fires). It is almost like the ‘read’ of the data is now failing
The log shows:
2022-03-06 11:59:16.561 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
2022-03-06 11:59:16.561 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 12
2022-03-06 11:59:16.562 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION
2022-03-06 11:59:16.562 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 4: Sensor Binary report, type=Motion, value=255
2022-03-06 11:59:16.563 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2022-03-06 11:59:16.564 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255
2022-03-06 11:59:16.565 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
I made no changes, although I did reboot. ZWA005 is the device. It is there, temp and lumonsity work just fine. Something went sideways during the night (or during reboot)
The binding is configured to listen to the MOTION ALARM reports - not the binary sensor reports, so this is why it’s not updating based on the report you provide above. This hasn’t changed since June.
It looks like parameter 4 configures this - the default is the motion alarms (notifications) and not the binary sensor, but I guess for some reason this may have been changed.
I solved the problem by removing the sensor from the controller, disabling the device, then re-added it as a new device. All is fine now. These are the settings I am currently using:
I made very few changes (setting lifeline), these are the defaults when I discovered and re-added the device.
I do not know how to associated these with the UI so I am unsure of what had gone sideways or how. I really try not to make changes without 1)documenting the change; 2) immediately testing; 3) rollback if any problem. To the best of my recollection, I had made no changes before it quit working.
While I have a working solution in place now, I would like to understand what happened. Since this is part of home security, understanding what went sideways would give me confidence before travelling.
