[BUG] LLKZMK11LM: power metering disappears after restart

[mikoff]

Describe the bug
On Home Assistant restart, the power monitoring entity of the device disappears. If we go to the cluster management screen we see that the device can read proper wattage, but the entities report “Unavailable” status.
The option to "Reconfigure" does not help.

To Reproduce
Steps to reproduce the behavior:

1. Pair LLKZMK11LM
2. Check that power monitoring works and reports
3. Reboot HA
4. Power monitoring utilities are missing

Screenshots

Additional context
The problem was discussed by other users on HA forum, for example:
https://community.home-assistant.io/t/aqara-lumi-2-channel-relay-with-zha/356984

[mazerte]

It may be related to this one to #1337.

On my side I get the same problem with the Aqara Smart Plug. Clusters are reporting good metrics but entities are unavailable.

[dmulcahey]

Do you have the same errors in the logs that the linked issue above does?

[leonardpitzu]

Logs are empty. Same the entities.

[mikoff]

I can confirm that logs are empty.

[jims-code]

The strange behaviour mentioned in this issue is shown by Aqara Smart Plug devices that were connected some days ago. Devices that were connected last year work fine.

Maybe there are some hints in these issues that help finding the reason for this strange behaviour:
home-assistant/core#67644
#1337

The file plug_mmeu01.py has been updated 3 months ago. It might be that this caused an unwanted side effect.
#1252

[kvvoff]

Is there any progress in solving the problem? I have the same with LLKZMK11LM

[jims-code]

For the Aqara Smart Plug the problem has been solved in zigpy/zha-device-handlers Release 0.0.73. The installation was done automatically by a Home Assistant update.

More details concerning the bug can be found here: home-assistant/core#67644

[kvvoff]

for LLKZMK11LM still doesn't work. Latest version of HA

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.