Zwave Alarm Class V3 and Multilevel V5

Add-ons Bindings
1

hi
for my fibaro smoke sensor version 002

the incoming fire alarm is not translated to the switch to go on.
as well the incoming multilevel report for temp does not update the item.

here is a log:

09:55:04.709 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 40: Transaction not completed: node address inconsistent.  lastSent=40, incoming=255
09:55:12.701 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 10 28 06 31 05 01 22 01 00 DF 
09:55:12.708 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09:55:12.709 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 10 28 06 31 05 01 22 01 00 DF 
09:55:12.711 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 10 28 06 31 05 01 22 01 00 DF 
09:55:12.712 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=10 28 06 31 05 01 22 01 00 
09:55:12.713 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 40: Application Command Request (ALIVE:DONE)
09:55:12.714 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 40: Incoming command class SENSOR_MULTILEVEL
09:55:12.715 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 40: Received Sensor Multi Level Request V5
09:55:12.716 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 40: Sensor Multi Level REPORT received
09:55:12.717 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 40: Sensor Type = Temperature(1), Scale = 0
09:55:12.718 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 40: Sensor Value = 25.6
09:55:12.719 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
09:55:12.720 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=40, callback=35, payload=28 02 84 08 
09:55:12.722 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=10 28 06 31 05 01 22 01 00 
09:55:12.723 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=35, expected=SendData, cancelled=false      MISMATCH
09:55:17.047 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 10 28 0A 71 05 00 00 00 FF 01 00 01 03 51 
09:55:17.050 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09:55:17.052 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 10 28 0A 71 05 00 00 00 FF 01 00 01 03 51 
09:55:17.054 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 10 28 0A 71 05 00 00 00 FF 01 00 01 03 51 
09:55:17.056 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=10 28 0A 71 05 00 00 00 FF 01 00 01 03 
09:55:17.056 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 40: Application Command Request (ALIVE:DONE)
09:55:17.057 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 40: Incoming command class ALARM
09:55:17.058 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 40: Received Alarm Request V3
09:55:17.059 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 40: Process Alarm Report, V3, length 13
09:55:17.060 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 40: Alarm report - 1 = 0, sensor=0, event=0, status=255
09:55:17.061 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 40: Alarm Type = Smoke (1)
09:55:17.061 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
09:55:17.062 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=40, callback=35, payload=28 02 84 08 
09:55:17.081 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=10 28 0A 71 05 00 00 00 FF 01 00 01 03 
09:55:17.082 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=35, expected=SendData, cancelled=false      MISMATCH
2

The alarm class have been updated to support notifications. I just need to find a few minutes to complete the review and merge.

I’ll have a look at the multilevel sensor when I get a chance - what device is this from?

3

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/129

4

I don’t think the lack of update has anything to do with the version of the command class - the message is processed correctly, but it’s just not passed on to the item.

Did you update any configuration in this device? I found a bug yesterday with the re-initialisation of the device after certain configuration was updated and this is exactly what happens (no event is passed to the thing handler) so it might be this that is the problem here.

5

mhh I think only after logging the stuff to see if modifications on config solve it

however I can test again when the bug is fixed. you talk about temperature and not the alarm right?

I actually thought aswell that the temperature was reported ok in the past. so you are most possible right here

6

Correct.