Z-Wave Fibaro FGD212 power (meter_watts1) not updated

Hi @chris and others

I have a Fibaro FGD212 with firmare version 3.5 where the meter_watts1 channel is not correctly updated.
My thing file looks like this:

Thing fibaro_fgd212_03_005 node22 “Bedroom lighting” @ “Bedroom” [ node_id=22 ]

And the items file looks like this:

Number Bedroom_light_watts “Soveværelse lys effektforbrug” (Bedroom_light) [“Measurement”, “Power”] { channel = “zwave:fibaro_fgd212_03_005:controller:node22:meter_watts1” }

I believe the device is reporting the power usage at regular intervals however the channel is not getting updated. The interval is about 5 minutes as I configured the device to report more frequent then default in a first attempt to fix the issue.
When I control the lights the meter_watts1 is updates, however it does not end up with the correct final value. I am guessing this is because a have configured the device to dim the lights very slowly. So that when I change the lights the first update will be send as something other than COMMAND_CLASS_SENSOR_MULTILEVEL V4 and these work correctly but the background reporting is not received and therefor the channel is not updated with the final value.

This is the Z-Wave debug log I get every 5 minutes.

2022-07-31 21:24:08.341 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 16 0A 60 0D 01 01 31 05 04 22 00 00 88
2022-07-31 21:24:08.342 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=22, callback=0, payload=00 16 0A 60 0D 01 01 31 05 04 22 00 00
2022-07-31 21:24:08.342 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=22, callback=0, payload=00 16 0A 60 0D 01 01 31 05 04 22 00 00
2022-07-31 21:24:08.342 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-07-31 21:24:08.342 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Application Command Request (ALIVE:DONE)
2022-07-31 21:24:08.343 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: resetResendCount initComplete=true isDead=false
2022-07-31 21:24:08.343 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2022-07-31 21:24:08.343 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 1
2022-07-31 21:24:08.343 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: SECURITY NOT required on COMMAND_CLASS_SENSOR_MULTILEVEL
2022-07-31 21:24:08.343 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 22: Received COMMAND_CLASS_SENSOR_MULTILEVEL V4 SENSOR_MULTILEVEL_REPORT
2022-07-31 21:24:08.343 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 22: Sensor Type = Power(4), Scale = 0
2022-07-31 21:24:08.343 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 22: Sensor Value = 0E+1
2022-07-31 21:24:08.344 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2022-07-31 21:24:08.344 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got a value event from Z-Wave network, endpoint=1, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=0E+1
2022-07-31 21:24:08.344 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 22: Sensor conversion not performed for POWER.
2022-07-31 21:24:08.344 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Updating channel state zwave:fibaro_fgd212_03_005:controller:node22:sensor_power1 to 0 [DecimalType]
2022-07-31 21:24:08.344 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Commands processed 1.
2022-07-31 21:24:08.344 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@4750d002.
2022-07-31 21:24:08.344 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-07-31 21:24:08.345 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-07-31 21:24:08.345 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-07-31 21:24:08.345 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

I am guessing that the issues is related to the log with the text : “Sensor conversion not performed for POWER” can you confirm this ?
In that case I will have a deeper look and maybe add the missing code to handle POWER in ZWaveMultiLevelSensorConverter.java.

Thanks for you help.

Kennet

Ok I did a bit of digging and found that the issue is not related to "Sensor conversion not performed for POWER” value is still used just without any scaling.

Instead I found that there is another channel called sensor_power1 this looks like it is updated correctly.
But is there somebody that can explain the difference between the two channels sensor_power1 and meter_watts1 ?