-
-
Notifications
You must be signed in to change notification settings - Fork 33.3k
Aqara Lumi Smart Plug EU missbehaving using ZHA #67644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey there @dmulcahey, @Adminiuga, mind taking a look at this issue as it has been labeled with an integration ( zha documentation |
Same problem here using a Conbee II. I don't know yet if this is a general problem in ZHA or only with this plug, maybe only this device "quirks" have been modified but this needs some attention. |
Hi, i got same issue with both of mine, have tried to reset one of them but same result, as seen in log information below it's like it do not poll it fast enough or something is not picking up the status correctly anymore. The one that is the most broken do not show firmware version at all for me. I run with the ConBee II in a Raspberry PI. What version of Home Assistant Core has the issue? What was the last working version of Home Assistant Core? What type of installation are you running? Integration causing the issue Diagnostics information |
So, we are almost a month later and there is still no comment from the developers... In the meantime I ordered a basic Sonoff equivalent to see it works and I think a warning should be issued somewhere to prevent others to be caught. |
Yeah, not even a comment :-( Sad. |
zigpy/zha-device-handlers#1337 Discussion can be found here for both the MAEU01 and the MMEU01. It would be cool if someone w/ dev experience that has one of these can help out. I am tied up with other things atm and I don’t have the devices in question. |
I have some (very small) dev experience, but with some guidance I might be able to help. I bought a MAEU01 in december 2021, that has worked flawlessly. Now in march 2022 I bought two new MAEU01 and I have the same problems. The watt-measurement may display for a while, but the gets unavailable. I have tested on both a RPI3 and a RPI4 |
I'm comming from zigpy/zha-device-handlers#1337 When initially adding these plugs I was running Homeassistant 2022.02. I've spun up a new instance of homeassistant:2021.12 and after adding the plugs again the plugs now shows I'm currently trying to narrow this down a bit more. |
Very interesting observation about the Quirk. |
So after my findings, I tried removing the signature lookup for the maeu01 (effectively reverting: zigpy/zha-device-handlers@b0bbbfb which was one of the changes in zha-device-handlers earlier this year) in my 2022.02 install, but it did still not register correctly. The quirk assignment is no longer there, but still the device is not configured properly. |
Did you remove and re-join the plug after the change? |
Thanks for reminding me, I might have forgotten. |
Hi! I have struggled with the same problems with my lumi.plug.maeu01. Now I downgraded ZHA-QUIRKS to try to get rid of the problems How to downgrade:
|
Brilliant ! |
But if that helps, we should file a bug with the zha-quirks package. Also downgrading seems to be working. |
@dmulcahey ...I'm on stuck modelling a dedicated quirk, why endpoints 21 and 31 (AnalogInput.cluster_id) are mismatching, they are both listed in the replacement area too.. ? |
@husjon .. I did a try by removing lumi.plug.maeu01 model signature in parallel with post publication (zigpy/zha-device-handlers#1337 (comment)) 15 days ago, but only the on-off functionality was ok, tested nowadays (remove, reboot, add) same results. That's why I'm struggling trying to build a dedicated quirk.. (not such an easy task!), I was very prone to live without a correctly translated DeviceTemperature. |
Hi @Stefano0042, that's wierd. I'm running homeassistant as a docker instance and in my case I attached to the container and did the following:
MODELS_INFO: [
(LUMI, "lumi.plug.mmeu01"),
# (LUMI, "lumi.plug.maeu01"),
],
After these steps, the plug went from only allowing power switching to also reporting Before: #67644 (comment) The after is without anu quirk assigned. Hope this helps. On a sidenote, I was thinking of trying to setup the zha-quirks environment so that I can debug this a bit closer, I might be able to take a look over the weekend, but I can't promise anything yet. |
..yes I can see you commented out/removed, the model signature, that lead to 'no quirk' of course, I did it in the same way, but with a different end results, so weird. |
New quirk version has been released, 0.0.69 But i don't find any information on what is changed from previous version ? Does anybody know how these new versions are updated in the ha version ? Finally, does anybody know where to see running ha's quirk version ? |
This issue has not been addressed yet |
I can confirm that this worked on my newest Aqara LUMI EU plugs.
|
The file plug_mmeu01.py had been updated on Jan 6 2022. Is the smart plug misbehaviour seen using the old version too? |
Last working was |
That’s fine, we have to consider too that through a well engineered new quirks, we can do much more. |
Same here... doesnt work! |
I've tried downgrading on my side, I get the entities Update : If i try to: |
Cool. I did as Digipix said and it worked, kinda.. but the "identify" was still "unknown" the class said "zigpy.device.Device" in Signature at bottom. So thanks for all of you :) |
What does the identify entity do ? |
Good question, but now it says "2022-04-06T16:19:32.301496+00:00" instead of "Unknown" :P |
I was more curious about the function in general - what is the purpose of this function ? |
Identify sets the device in identification mode, f.ex a lamp/bulb will blink for a couple of seconds to indicate which physical lamp/bulb it is. |
The plug is partly working but without any measurement using procedure above. But this quirk does not work with release 2022.4 anymore. Had to remove 0.0.65. |
Can I produce any logs that will help debugging the issue? |
folks... PLEASE STOP MESSING WITH DEPENDENCIES. You are risking tanking your entire system for a single device. IMO that isn't worth the risk and it is killing us support wise trying to mitigate the fallout from users modifying things they shouldn't modify. |
zigpy/zha-device-handlers#1337 (comment) If someone with this device can test this with a local quirk I would appreciate it. Again... Please do not use the custom deps add-on or modify your containers. Also, after testing remove the local quirk |
Same issue here. But I have two devices. One was added some months ago and power/energy is working (temperature is Unavailable). The other one was added today and all sensors are Unavailable. |
@dmulcahey here is the whole pairing log debug. |
I have the same problems here, is there anything I can do to help? |
Same problem here. Running ZHA, everything Vanilla. Just purchased 2 of those plugs to extend my Zigbee network and monitor power consumption of my water heater and other devices but no power metering working since day 1 (running the latest version of Home Assistant). If there is anything I can do to help, please let me know |
..well, in this case that it appear to be particularly harsh on my perception, it make perfect sense to try help the developers, by rising up a certain fund, everybody in the community of Aqara plug users might contribute with a coffee, so that they can "at least" order one sample by their own, but why not even more..., it is obvious the union that make the difference. @dmulcahey Hi David please how can I offer a coffee to you? @aqara_community, please rise up your thumb if you agree with me. |
I have 3 plugs. I can donate one to the project if it will help. |
..wow this is a "Beau Geste" not outrageous to anybody, hopefully :) I have spent 2 complete dedicated days, before give up, on this issue, half a day just digging the quirks knowledge and the remaining time struggling without success on finding a solution. |
The problem
When I add the Aqara Lumi Smart plug EU to homeassistant using ZHA it doesnt work all out.
Here is some info
And here is the result:

What version of Home Assistant Core has the issue?
core-2022.3.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
ZHA
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: