[ZWAVE] Sensor Type 133 with ZW100

Spaceman_Spiff · August 29, 2016, 6:04am

Hi,

I have a Aeotec ZW100 Multisensor. Today I got the following line in my logs (running last weeks snapshot from cloudbees):

2016-08-29 01:50:13.551 [ERROR] [veMultiLevelSensorCommandClass] - NODE 46: Unknown Sensor Type = 133, ignoring report.

Does anybody know what kind of sensor this is supposed to be? I am using a standard configuration:

Number      Movement            "Bewegung [%d]"                     (gRRD4J)                { zwave="46:command=sensor_binary" }
Number      Tamper              "Alarm: [%s]"                       (gRRD4J)                { zwave="46:command=alarm" }
Number      Temperature         "Temperatur: [%.1f °C]"             (gRRD4J,cTemperatur)    { zwave="46:command=sensor_multilevel,sensor_type=1,sensor_scale=0" }
Number      Humidity            "Feuchtigkeit: [%.0f %%]"           (gRRD4J)                { zwave="46:command=sensor_multilevel,sensor_type=5" }
Number      Brightness          "Helligkeit: [%.0f Lux]"            (gRRD4J,cHelligkeit)    { zwave="46:command=sensor_multilevel,sensor_type=3" }
Number      UV                  "UV [%d]"                           (gRRD4J)                { zwave="46:command=sensor_multilevel,sensor_type=27" }

Edit:
I enabled the Debug-Trace and I get this:

[DEBUG] [z.internal.ZWaveNetworkMonitor:441 ]- NODE 46: Node is asleep. Defer heal until it's awake

even though I included it while mains powered.

chris · August 29, 2016, 9:03am

Please provide a debug logfile so I can see what is actually being received.

Spaceman_Spiff · August 30, 2016, 9:50am

It did not occur yet, but I found something different:

2016-08-30 08:41:22.634 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
2016-08-30 08:41:22.635 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ]- NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 15
2016-08-30 08:41:22.637 [DEBUG] [ApplicationCommandMessageClass:89  ]- Transaction not completed: node address inconsistent.
2016-08-30 08:41:24.218 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0B 00 04 00 2E 05 31 85 05 01 4D 26 
2016-08-30 08:41:24.221 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-08-30 08:41:24.221 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-30 08:41:24.224 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0B 00 04 00 2E 05 31 85 05 01 4D 26 
2016-08-30 08:41:24.225 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0B 00 04 00 2E 05 31 85 05 01 4D 26 
2016-08-30 08:41:24.227 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 2E 05 31 85 05 01 4D 
2016-08-30 08:41:24.228 [DEBUG] [ApplicationCommandMessageClass:40  ]- NODE 46: Application Command Request (ALIVE:DONE)
2016-08-30 08:41:24.229 [DEBUG] [ApplicationCommandMessageClass:58  ]- NODE 46: Incoming command class SENSOR_MULTILEVEL
2016-08-30 08:41:24.230 [DEBUG] [veMultiLevelSensorCommandClass:95  ]- NODE 46: Received Sensor Multi Level Request
2016-08-30 08:41:24.231 [WARN ] [veMultiLevelSensorCommandClass:165 ]- Unsupported Command 0x85 for command class SENSOR_MULTILEVEL (0x31).

and

2016-08-30 09:56:10.317 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ]- NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
2016-08-30 09:56:10.318 [DEBUG] [ApplicationCommandMessageClass:89  ]- Transaction not completed: node address inconsistent.
2016-08-30 09:56:16.277 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0B 00 04 00 2E 05 31 15 1B 01 00 E5 
2016-08-30 09:56:16.280 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-08-30 09:56:16.280 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-30 09:56:16.284 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0B 00 04 00 2E 05 31 15 1B 01 00 E5 
2016-08-30 09:56:16.286 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0B 00 04 00 2E 05 31 15 1B 01 00 E5 
2016-08-30 09:56:16.288 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 2E 05 31 15 1B 01 00 
2016-08-30 09:56:16.289 [DEBUG] [ApplicationCommandMessageClass:40  ]- NODE 46: Application Command Request (ALIVE:DONE)
2016-08-30 09:56:16.290 [DEBUG] [ApplicationCommandMessageClass:58  ]- NODE 46: Incoming command class SENSOR_MULTILEVEL
2016-08-30 09:56:16.291 [DEBUG] [veMultiLevelSensorCommandClass:95  ]- NODE 46: Received Sensor Multi Level Request
2016-08-30 09:56:16.292 [WARN ] [veMultiLevelSensorCommandClass:165 ]- Unsupported Command 0x15 for command class SENSOR_MULTILEVEL (0x31).

chris · August 30, 2016, 9:58am

I would hazard a guess that these are corrupted frames so there’s not so much that can be done. I would also hazard a guess that the sensor type 133 might also be a corruption issue.

I recall in the past problems with some Aeon sensors return corrupt information if they were polled, and correct information if the data is sent unsolicited - is this from polling?

Spaceman_Spiff · August 30, 2016, 11:42am

Very strange. I do no polling whatsoever, the device reports them by itsself (see configuration in first post).

It also reports two command classes which are not yet supported: CONTROLLER_REPLICATION and POWERLEVEL .

2016-08-30 11:21:28.105 [DEBUG] [b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveBinarySensorValueEvent
2016-08-30 11:21:28.106 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
2016-08-30 11:21:28.108 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ]- NODE 46: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 0
2016-08-30 11:21:28.110 [DEBUG] [ApplicationCommandMessageClass:89  ]- Transaction not completed: node address inconsistent.
2016-08-30 11:21:28.410 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 10 00 04 00 2E 0A 73 05 00 00 00 FF 07 00 02 00 43 
2016-08-30 11:21:28.414 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-08-30 11:21:28.414 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-30 11:21:28.417 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 10 00 04 00 2E 0A 73 05 00 00 00 FF 07 00 02 00 43 
2016-08-30 11:21:28.420 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 10 00 04 00 2E 0A 73 05 00 00 00 FF 07 00 02 00 43 
2016-08-30 11:21:28.423 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 2E 0A 73 05 00 00 00 FF 07 00 02 00 
2016-08-30 11:21:28.424 [DEBUG] [ApplicationCommandMessageClass:40  ]- NODE 46: Application Command Request (ALIVE:DONE)
2016-08-30 11:21:28.426 [DEBUG] [ApplicationCommandMessageClass:58  ]- NODE 46: Incoming command class POWERLEVEL
2016-08-30 11:21:28.427 [DEBUG] [ApplicationCommandMessageClass:64  ]- NODE 46: Command class POWERLEVEL not found, trying to add it.
2016-08-30 11:21:28.428 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass:239 ]- NODE 46: Unsupported command class POWERLEVEL
2016-08-30 11:21:28.430 [ERROR] [ApplicationCommandMessageClass:77  ]- NODE 46: Unsupported command class POWERLEVEL (0x73)

2016-08-30 09:19:20.808 [DEBUG] [ApplicationCommandMessageClass:89  ]- Transaction not completed: node address inconsistent.
2016-08-30 09:19:21.567 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0C 00 04 00 2E 06 21 05 03 0A 00 DA 28 
2016-08-30 09:19:21.570 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-08-30 09:19:21.570 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-30 09:19:21.576 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0C 00 04 00 2E 06 21 05 03 0A 00 DA 28 
2016-08-30 09:19:21.578 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0C 00 04 00 2E 06 21 05 03 0A 00 DA 28 
2016-08-30 09:19:21.580 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 2E 06 21 05 03 0A 00 DA 
2016-08-30 09:19:21.581 [DEBUG] [ApplicationCommandMessageClass:40  ]- NODE 46: Application Command Request (ALIVE:DONE)
2016-08-30 09:19:21.582 [DEBUG] [ApplicationCommandMessageClass:58  ]- NODE 46: Incoming command class CONTROLLER_REPLICATION
2016-08-30 09:19:21.584 [DEBUG] [ApplicationCommandMessageClass:64  ]- NODE 46: Command class CONTROLLER_REPLICATION not found, trying to add it.
2016-08-30 09:19:21.585 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass:239 ]- NODE 46: Unsupported command class CONTROLLER_REPLICATION
2016-08-30 09:19:21.587 [ERROR] [ApplicationCommandMessageClass:77  ]- NODE 46: Unsupported command class CONTROLLER_REPLICATION (0x21)

What can I do to provide further information?

chris · August 30, 2016, 11:45am

Ok- it was just a thought in that Aeon devices have been known to send corrupt data.

This shouldn’t matter - you probably don’t want to use these classes? It’s very unlikely they will ever be added to OH1.

I don’t think there’s much more I can say - it seems the device is sending invalid information so there’s not much we can do I think.

Spaceman_Spiff · August 30, 2016, 11:52am

No - it was intended as additional information for you.

I’ll track the issue a little bit further in the thread - maybe we can find something.
But essentially I’ll consider this closed.
Thank you for your quick reply.

chris · August 30, 2016, 11:55am

Ok - thanks ;). There are a lot of command classes that aren’t implemented - especially in OH1. Most of them are not really useful, or used day to day…

FYI, I have a switch at home that after a month or two of running, starts to send these sorts of things and I end up with invalid command class errors, or invalid command errors - same sort of thing as you see. If I power it off/on, the errors stop for a month or two.