Aqara smart plug (EU) not reporting kWh and W through deCONZ

[dieugab]

Describe the bug

Aqara smart plug (EU) version with power metering is not reporting kWh and W sensors, even though you can see the stats being updated in deCONZ REST API. This issue is forwarded from https://github.com/home-assistant/core/issues/84867 by request due to https://github.com/home-assistant/core/issues/84867#issuecomment-1368066490

Steps to reproduce the behavior

1. Add Aqara smart plug in deCONZ
2. Read all required attributes
3. Add to Home Assistant through official integration
4. Plug in device that draws power

Expected behavior

Current W draw is reported, like it used to before the introduction of DDF

Screenshots

Environment

• Host system: Raspberry Pi
• Running method: Home Assistent deCONZ Add-on
• Firmware version: 26720700
• deCONZ version: 2.19.03 / 9/19/2022
• Device: ConBee II
• Do you use an USB extension cable: yes
• Is there any other USB or serial devices connected to the host system? No

deCONZ Logs

Additional context

[Mimiix]

What's the manufacturer I'd and model id? I believe this is a duplicate.

[dieugab]

What's the manufacturer I'd and model id? I believe this is a duplicate.

[Mimiix]

Seems that this should be fixed before by a pr by @SwoopX .

[timiman]

I have the exact same issue as @gvssr . Un-pairing and re-pairing the device does not fix this. Maybe the previous fix was for the US version and not the EU one ?

Reference: #6502

[cappadanna]

Same issue here with same plug and firmware

[ondrackajan]

I tried it on 3 different smart plugs and it's bugged on all. It could be semi-solved by removing and adding the smart plug over and over again (remove the node, restart HA, remove entities, add plug). It's being added as "power" or as "consumption" in deconz. So maybe it takes x tries to rotate to the "correct" constellation. Then it works. However, when I moved the plug to a different room, I had to start the whole process again. It took me about 7 tries. Also sometimes when I restart host, it may stop working again.

Maybe another clue. Each plug created 2 entities for Power and 2 entities for Consumption. Only one of each shows correct values.

[dieugab]

@ondrackajan I've noticed for me while trying to add / remove / add the plug there's a huge delay in reported Wattage in deCONZ API vs. what shows up in the Home Assistant frontend.

Through DDF: 5-10 minute delay before changed values show up Without DDF: Updated every 1-5 seconds

[BabaIsYou]

Through DDF: 5-10 minute delay before changed values show up

With "refresh.interval": 300 in DDF it seems normal to me to have a refresh at 5mn

[Rob787]

Same issue here with 0w and 0 kwH readings

[Mimiix]

Did all of you check https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Xiaomi-smart-plugs-not-working-correctly

[Rob787]

@Mimiix Yep, I'm on latest version already and resetted multiple times:

[Rob787]

I did notice following behaviour:

Initially HASS only get the Temp and Power (wattage) entity. Then the Power seems to get updated. After a while, and a HASS restart, the Consumption entity also returns, and then Power and Consumption remain on 0.

[Mimiix]

@Mimiix Yep, I'm on latest version already and resetted multiple times:

Also the conbee / raspbee ?

[Rob787]

@Mimiix Yep, I'm on latest version already and resetted multiple times:

Also the conbee / raspbee ?

Yep Conbee II:

[Mimiix]

@Mimiix Yep, I'm on latest version already and resetted multiple times:

Also the conbee / raspbee ?

Yep Conbee II:

In that case I'm out of options 😅

[Smanar]

Can you check using the flag "DDF" in logs if the device use the DDF or not for power ?

On the actual DDF for "lumi.plug.maeu01" , the DDF chek for the presence of cluster 0x1f and 0x15 to be used It use the Xiaomi cluster for current, voltage, and cluster 0x000C /attribute 0x0055 (from cluster 0x1F and 0x15) for power and consumption.

So what is working or not ?

If you read the value in the GUI, it update the value in the API ?

[dieugab]

This issue actually pushed me over to migrating to Zigbee2Mqtt, solving my problem. I'll keep this issue open for others, but am unsubscribing as it's no longer applicable for me.

[github-actions[bot]]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[github-actions[bot]]

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.