core: ZHA plugs - smartenergy_metering > wrong cluster
The problem
In ZHA smart plugs are not showing value for used energy counter. I have tested 4 different types of plugs and all of them show:
smartenergy_metering - ‘unknown’
When I use Manage Clusters I can see that all those plugs report used energy value in cluster 0x702, attrid 0 as current_summ_delivered
So it seems that instead of smartenergy_metering ( I don’t know from which cluster it comes in existing integration) should be used cluster: Metering (Endpoint id: 1, Id: 0x0702, Type: in), attribute: current_summ_delivered (id: 0x0000)
I have checked with: BlitzWolf BW-SHP13, Innr SP 120, Schwaiger ZHS15, Lonsonho 16A Energy Monitoring Plug and all of them report used energy counter in cluster:0x702, attrid:0
Same problem reported also by other users: (https://github.com/home-assistant/core/issues/34090#issuecomment-745948613)
Environment
- Home Assistant Core release with the issue: 2020.12.1
- Last working Home Assistant Core release (if known): N/A
- Operating environment (OS/Container/Supervised/Core): Home Assistant OS 5.9 on RPi4
- Integration causing this issue: ZHA
- Link to integration documentation on our website: ZHA
Problem-relevant configuration.yaml
N/A
Traceback/Error logs
N/A
Additional information

BlitzWolf

Innr120

About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 19 (5 by maintainers)
Fixed in latest dev.
Can you please explain your answer? Why have you selected attribute ‘instantaneous_demand’ to read and not ‘current_summ_delivered’? I have tested 4 different plugs and neither of them supports ‘instantaneous_demand’ but all they support ‘current_summ_delivered’ Can you say any plug which supports ‘instantaneous_demand’? My proposal is not to add new attribute but to replace ‘instantaneous_demand’ with ‘current_summ_delivered’
I can confirm the same issue with the Aqara Smart Plug. No values are present on “instantaneous_demand”, instead “current_summ_delivered” should be used.
Replace sounds like a good solution. Will this be implemented?
I’m experiencing the same problems.