Sometime yesterday, my Aeon multi-sensors stopped sending full motion detection messages. All that is sent now is;
2018-02-19 14:47:58.314 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Application Command Request (ALIVE:DONE)
2018-02-19 14:47:58.314 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2018-02-19 14:47:58.314 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@461d449f already registered
2018-02-19 14:47:58.314 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class SENSOR_BINARY
2018-02-19 14:47:58.315 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 13: Received SENSOR_BINARY command V1
2018-02-19 14:47:58.315 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 13: Sensor Binary report, type=Unknown, value=255
2018-02-19 14:47:58.315 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
2018-02-19 14:47:58.315 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=13, callback=245, payload=0D 02 80 02
2018-02-19 14:47:58.315 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0D 03 30 03 FF
2018-02-19 14:47:58.316 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=245, expected=ApplicationCommandHandler, cancelled=false transaction complete!
Nothing about a motion detection (or anything related to this node) shows up at that time in the event.log
Since I had first set it up about a week ago, it had been sending these messages;
2018-02-16 17:40:57.880 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Application Command Request (ALIVE:DONE)
2018-02-16 17:40:57.880 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Starting initialisation from DONE
2018-02-16 17:40:57.880 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@5b30bac already registered
2018-02-16 17:40:57.880 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class SENSOR_BINARY
2018-02-16 17:40:57.880 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 13: Received SENSOR_BINARY command V1
2018-02-16 17:40:57.881 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 13: Sensor Binary report, type=Unknown, value=255
2018-02-16 17:40:57.881 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
2018-02-16 17:40:57.881 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2018-02-16 17:40:57.881 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 255
2018-02-16 17:40:57.881 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Updating channel state zwave:device:7efa0603:node13:sensor_binary to **ON** [OnOffType]
And the event.log showed;
2018-02-16 17:40:57.882 [vent.ItemStateChangedEvent] - KitchenMotionSensor changed from OFF to ON
I disabled and re-enabled motion in HABmin, then restarted OH2. The full messages started showing back up again. Then sometime later (less than 1 hour), they reverted back to the incomplete messages.
One of the 4-in-1 sensor .xml files is at;
https://paste.ubuntu.com/p/8qpQZ9QtWy/
Is this a problem with the sensors, the event handling mechanism, or … ?