ZWave HSM02 not handling tamper alarm

On the Everspring HSM02 door/window sensor, I’m not seeing the tamper alarm get generated. The tamper alarm occurs when you release the button on the back of the device. I’m seeing this same bahavior with the Everspring SM103 door/window sensor. Looks like the frame is badly formatted, or the binding is not handing correctly.

Here’s the debug log.

2016-06-11 15:10:21.190 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 08 04 71 05 01 11 99
2016-06-11 15:10:21.191 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-06-11 15:10:21.192 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 04 00 08 04 71 05 01 11 99
2016-06-11 15:10:21.193 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0A 00 04 00 08 04 71 05 01 11 99
2016-06-11 15:10:21.194 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 04 71 05 01 11
2016-06-11 15:10:21.194 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Application Command Request (ALIVE:DONE)
2016-06-11 15:10:21.194 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Starting initialisation from DONE
2016-06-11 15:10:21.195 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@ff31dd already registered
2016-06-11 15:10:21.195 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Incoming command class ALARM
2016-06-11 15:10:21.195 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: Received Alarm Request V0
2016-06-11 15:10:21.195 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: Process Alarm Report, V0, length 7
2016-06-11 15:10:21.196 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 04 71 05 01 11 >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 04 71 05 01 11 (9)

Thanks for any assistance.

@chris Your log viewer seems to be interpreting this correctly as an ALARM. Should I log this as an issue?

There’s an outstanding PR for the notifications -:

I suspect once this is merged it will solve the issue as well.

Yep, that PR looks like it will solve the issue.