ZWAVE - Not the right scale

shorty707 · December 25, 2016, 4:45pm

I deleted a thing and readded it … now some meter stuff stopped working and the log shows “not the right scale”.
can you help me out there? device: http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1

17:41:35.219 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 14 00 04 00 02 0E 32 02 21 34 00 00 00 01 00 00 00 00 00 00 C7 
17:41:35.226 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
17:41:35.231 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 14 00 04 00 02 0E 32 02 21 34 00 00 00 01 00 00 00 00 00 00 C7 
17:41:35.234 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 14 00 04 00 02 0E 32 02 21 34 00 00 00 01 00 00 00 00 00 00 C7 
17:41:35.238 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 0E 32 02 21 34 00 00 00 01 00 00 00 00 00 00 
17:41:35.240 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
17:41:35.242 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
17:41:35.244 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@b0754c already registered
17:41:35.246 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class METER
17:41:35.264 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 2: Received METER command V3
17:41:35.273 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 2: Meter: Type=Electric(1), Scale=W(2), Value=0.1
17:41:35.273 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 02 03 25 03 FF 2A 
17:41:35.275 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMeterValueEvent
17:41:35.280 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMeterValueEvent
17:41:35.283 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 0.1
17:41:35.285 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:15348538564:node2:meter_watts to 0.1 [DecimalType]
17:41:35.318 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_Power_Factor <> E_W
17:41:35.319 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_KWh <> E_W
17:41:35.320 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_A <> E_W
17:41:35.322 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_V <> E_W

chris · December 25, 2016, 4:59pm

The “Not the right scale” messages are a hangover of some debugging - you will always see these at the moment (I should remove them) - you’ve probably just not noticed them before. Basically, when a meter update is received, the code loops through all the channels that are defined, and it processes when there’s a scale match, and when there’s not, it prints this message.

In the event above, you’ve received a E_W meter reading, and there are presumably 5 meters defined for the device so you see 4 off these messages (the 5th being the one that should actually be processed). We can see that in this log, the binding did update the watts channel, so all looks 100% fine here…

So, don’t worry about these messages - they are fine… What actually isn’t working?