[ZHA] [Conbee 3] Xiaomi Mi Power Plug EU (lumi.plug.mmeu01) can control on/off but does not report anything power related

[merdok]

The problem

I got myself a Conbee 3 recently and migrating everything from a deconz and Conbee 2 setup to Home Assistant zha! So what i noticed is that i can pair the Xiaomi Mi Power Plug EU (lumi.plug.mmeu01) and i can control the on/off state but nothing which is power related is not reporting. Also the plug state (plugged or unplugged) is stuck in the state which was during pairing. I tried to re-pair and reconfigure already multiple times now but now luck.

What version of Home Assistant Core has the issue?

2023.12

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

zha

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

zha-2e77803ea191c738f07993cb33390d51-LUMI lumi.plug.mmeu01-aefd5a4f9c20ef772b84700390b5a28c.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

The same plug was working fine before, but i used the deconz integration and Conbee 2.

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zha` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zha` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation zha source _{^{(message by IssueLinks)}}

[puddly]

Can you include a debug log of the reconfigure and of you toggling its state?

Also, is your Conbee III running the latest available firmware?

[merdok]

@puddly can you tell me where i can find the debug log of the reconfigure and state toggle?

I just saw that there was a firmware update yesterday. I do not have it installed yet, you want me to try that before i continue?

[puddly]

Enable debug logging for the integration (devices > ZHA) and perform both actions. After that, disable it and a file will download.

As for the firmware update, yes, definitely.

[merdok]

Did the firmware update, nothing changed! Unfortunately the issue still persists.

Here are the requested logs: home-assistant_zha_2023-12-09T15-55-23.128Z.log

[TheJulianJES]

Can you also check the app_version attribute on the Basic cluster of your mmeu01 plug? You can do that using the three dots on the device page, select Manage Zigbee device, clusters tab.

[merdok]

It is 24

[TheJulianJES]

That version requires the Xiaomi manufacturing codes to be sent during pairing. For EZSP, bellows will do this automatically. For Conbee 1 and 2, the firmware needs to be updated. I'm not sure how Conbee 3 handles this though. Either way, the codes need to be sent during pairing, as the device will not work correctly otherwise. I'd guess this is the issue here.

(Btw., if you experience random toggling on this plug, you can downgrade it to v22. That version also doesn't require the Xiaomi manufacturing codes to be sent. That issue should still be fixed though.)

[merdok]

The thing which is confusing me ist that those same plugs were working fine with a Conbee 2 over the deconz interation before.

[puddly]

The Conbee II and Conbee III run very different firmwares and have different chips inside. Try the same device with deCONZ with the Conbee III if you can and see if it works the same way it does with the Conbee II.

[merdok]

I understand that, but the whole point of my migration is to get rid of the deconz middle layer and use zha directly, as i use HA for all my automations anyway. For this reason Ii decided to get the Conbee 3 and start from scratch directly on HA and zha. Nevertheless, what is the solution here? I have downgrade the firmware of my Mi Plugs?

[TheJulianJES]

what is the solution here? I have downgrade the firmware of my Mi Plugs?

That's a workaround, not a solution. It'll likely work for this plug, but all newer Aqara devices require those codes to be sent during pairing to work properly. Again, not sure how it works with the Conbee 3, but zigpy-deconz or Conbee 3 firmware needs to implement the feature of sending the Xiaomi manufacturing codes when a Xiaomi device is paried.

If you can temporarily try deCONZ to see if the plug works there, we can see if they implemented sending Xiaomi manufacturing codes (in deCONZ).

[merdok]

but all newer Aqara devices require those codes to be sent during pairing to work properly.

Well that is a statement which reminds me that i have also the Aqara E1 Thermostats and i tried to pair one, it seemingly paired successfully but i cannot control the thermostat, it simply does nothing. Can this also be the same issue?

As i almost already moved all devices to the new zha setup, currently it would be hard for me to move the stick back to the other machine and try it with deCONZ there... An option would be for me to install deconz in parallel on the same machine, but the question is if that might corrupt my current zha network, if i setup both on one conbee?

[puddly]

but the question is if that might corrupt my current zha network, if i setup both on one conbee?

As long as you disable ZHA before starting deCONZ (and vice versa) there will be no issues.

[merdok]

Ok, since i had a spare microsd, i used a fresh Raspberry Pi OS image, installed just deconz and used it in my pi with the conbee 3 stick. I then paired the Mi Power Plug EU with that setup and i can confirm that everything works there (current power consumption shows up)! So i guess deconz implements it in software and not in the conbee stick firmware?

[merdok]

@puddly @TheJulianJES any update on this?

[issue-triage-workflows[bot]]

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 Home Assistant 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.