Xiaomi Aqara Plug (SP-EUC01/lumi.plug.maeu01) Toggles without reason #13903
Comments
|
I can confirm and reproduce that behavior. My plug has the same firmware. With my E1743, I can reliably turn on or off the plug. |
|
Seems the plug started listening to group 0, can you try to make a group 0 in z2m, add the plug to it and then remove it again? |
|
Creating group: Adding the plug to the group (plug is 0x54ef441000157f54): Testing the switch off and on (switch is 0x8cf681fffe2d74ae, plug is 0x54ef441000157f54): Removing the plug from the group: Testing the switch off and on (switch is 0x8cf681fffe2d74ae, plug is 0x54ef441000157f54): The behaviour of the plug is still the same, it switches based on switch commands only routed through it. |
|
That's strange, look that the fw is buggy since it shouldn't respond to that command. Can you try to bind the ikea remote to group 0, unbind it and then bind it to another group (random, e.g. 128). You should bind the |
|
I have the same problem with LLKZMK11LM relay on firmware 9-22-2021. IKEA remote E1524/E1810 toggles the relay switch at Endpoint: l1 when it routed through it. Seems like the problem is in Aqara devices... |
|
What I also noticed since the firmware upgrade is the SP-EUC01 plug creates these kind of errors in the log: It is written in the log as is, with these special characters. |
When I want to bind the Ikea switch to group 0, the button is not active:
I can unbind it on the GUI, then I press a button on the Ikea switch to wake it up, then the GUI says it was successful with the green popup and I see it in the logs. After this the plug still responds to the switch commands if the switch is routed via the plug. If I bind it to group 128 with the genOnOff cluster, still the same behaviour, the plug toggles. I stronlgy suspect this is the results of the firmware, is there a copy of the old version, can the device be rolled back? |
|
@Otnow given the bugs in this fw, can we put back the old ones? |
It is a pity that this firmware version ( Created a PR to return the previous version ( |
|
Only saw this issue because of the updated OTA files:
Edit 1: Looks like this "fix" to have the plug leave group 0 was already discovered somewhat? |
|
I have the same issue. I was unable to make the plug leave group 0, unbind the OnOff cluster, etc. Rolling back the firmware also doesn't work as the device prevents it (tried via Local OTA index). Is there any way to at least temporarily fix this until a new firmware is released? |
|
WARNING: Do this at your own risk. You could fully brick your device. (Although no one has managed to do so, yet) Instructions on how to downgrade maeu01 plug to v32 by bypassing the file version checkThe Aqara MAEU01 plug only checks that the header file version of the provided OTA image is bigger than the one currently installed. ((NOTE: The above firmware download is only for the Using zigpy/zigpy-cli, the image for the import pathlib
from zigpy.ota.image import parse_ota_image
data = pathlib.Path('OTA_lumi.plug.maeu01_V32_20200922_C11F8A.20200924102946.ota').read_bytes()
image, remaining = parse_ota_image(data)
assert not remaining
image.header.file_version = 42
pathlib.Path('OTA_lumi.plug.maeu01_V32_20200922_C11F8A.20200924102946_modded_to_v42.ota').write_bytes(image.serialize())You should be able to use that image to downgrade your plug to v32 from v41. If you're lucky, the device doesn't brick itself. I did have to re-activate pairing mode on my MAEU01 plug for some reason though. (The device didn't actually re-pair itself to the network though.) You can confirm the downgrade was successful by checking that If you also try this, please let me know how it went. (Note: Remove the OTA file after you've downgraded your plug successfully, as ZHA and likely Z2M might try to continuously "upgrade" your plug again. If the update starts again with ZHA, stop HA during the second update, remove the OTA file, start HA again, then re-pair the plug, so it stops requesting the rest of the OTA image.) You might want to remove and then re-pair the device after the old firmware is installed. @Otnow Do you know if there are any firmware versions for that plug between v32 and v41? |
Excellent. I hope this will help others to roll back from the problematic firmware version.
It seems that there is no judging by the information from the Aqara Developer Platform: {
"result": [
{
"releaseTime": "1642585695000",
"necessary": 0,
"fileSize": 273278,
"updateLog": "1.Fix the offline problem of device",
"state": 2,
"firmwareVersion": "0.0.0_0041"
},
{
"releaseTime": "1603976430000",
"necessary": 0,
"fileSize": 278094,
"updateLog": "1.Fixes known issues",
"state": 2,
"firmwareVersion": "0.0.0_0032"
}
]
} |
|
@TheJulianJES It worked for me, thanks for the tutorial and the image! |
|
@TheJulianJES Thanks, worked for me too! I used Z2M. In case anybody wonders how to do it:
|
Thanks, following this I have also successfull downgraded the firmware and the problem got resolved, so this is a viable workaround. Thanks all. I presume I shouldn't close the issue as it still persists, we just have a workaround until a proper solution is applied. |
|
@TheJulianJES Hi! Does this also work for the lumi.plug.mmeu01 or do i need another firmware? (Model: ZNCZ04LM Firmware: 01-23-2022) |
|
@greiseknoue Does the mmeu01 also have the problem with toggling randomly on the 2022 firmware? Or what exactly are you trying to achieve? |
|
@TheJulianJES Yes i have the same issue where the E2001/E2002 and E1812 toggles the plug. I have three mmeu01 plugs where the one i updated has this issue. The firmware build on the non-updated plugs are on 09-06-2019. in one case, i randomly got E2001/E2002 to work only to the coordinator (I noticed it didn't route through the plug in the "map"-section"). |
|
NOTE: This is only for the Xiaomi NOTE: For the The instructions for installing that firmware should be basically identical to the ones in #13903 (comment). |
|
Thank you so much for your help. I think i got it working, but it still says "Firmware build date 01-23-2022" in the ui of the device. I'm guessing i should look somewhere else to find the right firmware? |
|
Mhm, |
|
After removing the plug from the wall and plugging it in, it works and it says 09-06-2019! Thank you once again! I will report back if the issue still persist. |
|
How to disable ota if the device is already on version 32? |
|
@lo97 Are you using ZHA or Z2M? For ZHA, just remove the modified OTA file from the ota directory. |
There may be one, mine has |
I'm trying to find that option(add |
|
@kevinmilner, unfortunately I did not find firmware lower than It's a pity that this version of the firmware caused problems, I created a PR to remove it. |
|
Hi, I have issue with new Aqara Smart Plug (EU round) and I think it's same problem like here. But I'm not using Home Assistant. I have Aeotec Hub and using only Smartthings app for control, pairing etc. I just got a few of those Aqara plugs and my oldIKEA Switch (which I use for lights) is controlling one of these plugs by itself. So switching light off is also switching my PC off and that's very unfortunate. I'm trying to find solution, but not sure if that's even possible for me since I'm using only Smartthings app. |
|
This issue was driving me nuts for days. I tried to connect RODRET switches to the network and they have been routed through my AQARA Plug (model lumi.plug.maeu01) (firmware 0.0.0_0041) which resulted in unexpected toggling of the plug directly. Can confirm firmware 01-13-2023 is also affected. After I literally turned of everything else in the network (also the coordinator) the plug was still turned off and on by the switch. Please spread this information and help removing the bugged firmware everywhere in the web. |
|
just a quick note to thank you everybody for that help ! I'm french and use diffrent Aqara plug some are in v42 some in v43. Following this guideline and downloading the good firmware file allow me to use Aqara with HA and it's working like a charm ! |
|
E2123 And aqara eu wall plug … the issue is always here |
|
So that is what causes this... fortunately the remotes usually route through other devices. |
|
I'm experiencing the same issue but with lumi.switch.b2nc01. Anyone happens to know where to get an older firmware for this device? It's currently on 06-15-2022. |
|
My plug came with version 43 firmware. I followed the instructions from #13903 (comment) but after restarting the zigbee2mqtt service in the logs I still have "update":{"installed_version":43,"latest_version":32,"state":"idle"},"update_available":false My data is organized like this: configuration.yaml config: aqara_OTA_downgrade.json config: Why doesn't it pick up the update? edit: after I send the command to update it: these are the logs: edit2: figured it out, the issue was in configuration.yaml |
Thanks. With v.43 and this modified one sp-euc01 only occasionally reports voltage and current. Should it work like this? Power is reported fine as i see. |
|
Aqara pushed v45 through m2 in Europe. Can anyone intercept the update and make the OTA possible? So that we can test whether this bug has been fixed. Thanks. |
|
v45 was apparently pushed to the zigbee-ota repo: Koenkk/zigbee-OTA#560 |
|
I updated 8 of my Aqara EU plugs, it seems that the problem that the router plug gets turned off and on by a remote is fixed now. Happy to wait for others' responses. |
Is it reporting voltage with v. 45 properly? With previous v.43 and after downgrading to v.32 it wasn't. Just randomly changing values occasionally. |
It is better probably. I updated yesterday during day (not all at the same time). Chart for last two days: |
|
Hello there, I own a lumi.plug.maeu01 which I too recently updated from the 32 to 45 firmware version; it has been half a day and I did not experience strange behaviours. I will keep an eye on it and come back to give more feedback after a couple of days |
|
Mine still reports null voltage, same as before the upgrade. |
Maybe this made a difference: after the update I found duplicate entries in the reporting section of the device settings (this might be cause by my customisations to the reporting) - I therefore removed the device from the network, then put it in pairing mode, added it back again and tryed it with a hairdryer withe the default settings. After this "adoption dance" the plug reports voltage and energy as before, however I did not check in between. |
|
No change after re-pairing unfortunately. info 2024-09-24 12:46:49MQTT publish: topic 'zigbee2mqtt/socket2', payload '{"auto_off":null,"button_lock":null,"consumer_connected":null,"current":null,"device_temperature":null,"energy":0.01,"led_disabled_night":null,"linkquality":86,"overload_protection":null,"power":167.4,"power_outage_memory":null,"state":"ON","update":{"installed_version":45,"latest_version":45,"state":"idle"},"update_available":false,"voltage":null}' |
|
Disclaimer: I'm not a pro at this so bare with me.... So two days ago HA (Z2M) told me, that there was a firmware update available for my Aqara SP-EUC01. I happily updated. Since then my two plugs have been insanely unstable. They are offline/unavailable most of the time. See the following screenshot: So looks like the have both received the latest firmware which have made them incredibly unstable. |
|
Same here, one is 07-19-2024 the other is 09-22-2020. Neither of them report voltage or current (which was also the case before the firmware upgrade). |
|
If upgraded plugs do not report anything, re-pair them to Z2M/ZHA. If it still doesn't work, make sure you're running updated firmware on the coordinator(!), then re-pair again. |
|
For context, as pointed out by TheJulianJES: I am using a Sonoff Zigbee 3 Dongle P, with firmware I cannot think of any other differences right now, but I am willing to help with diagnosing this device if you have suggestions. |
But it reports values, but then it loses connection for some hours, then reconnects itself and reports values again. Before the firmware update I had no issues with them dropping out. :( |
This is with the plug with v45 on my end. |
Doesn't look like voltage is reported properly. Or you have VERY stable voltage |
|
I upgraded a plug from v41 to v45:
before / after: before / after: before / after + comparison Maybe there is some new mapping of props required?! Seems still buggy to me. |
and others
What happened?
I've executed OTA firmware update on the Xiaomi Aqara plug (SP-EUC01). Old fw version: 09-22-2020. New version came from zigb222mqtt OTA location, version 20211206.
The upgrade completed without problems.
After that update, whenever I press the button on any IKEA E1812 or E1743, the plug toggles its state which is really undesired. It happens only when the button is connected to that plug (routed via it). Repairing the button using another router helps for a moment but as the network reconfigures itself, the buttons are again routed via the plug, so random buttons start to turn that router plug on and off. Since that plug is not solely a router but provides power to my home office, this is very annoying and made the device unusable. It didn't brick it, but the functionality became useless.
This is in the logs when I press an unrelated button routed through the plug, and switching it:
I accidentally realized that these ghost switches work when zigbee2mqtt is down, ie. the plug works in a binding manner with all switching devices that are routed through it. In the meantime sensors routed through it work fine. It seems like when the firmware got upgraded to the one on the OTA server, it makes the plug and all routed switches like binded devices. It may be that the firmware is corrupt, but I have found no way to roll back. I've tried to unbind the switches that are routed through the plug via zigbee2mqtt GUI. The unbind gives a success message but the faulty behaviour remains.
Apparently happened to ohers but not too much traffic in that thread: https://community.home-assistant.io/t/aqara-plug-sp-euc01-lumi-plug-maeu01-toggles-without-reason/451671/2
What did you expect to happen?
After the firmware upgrade the device behaviour is identical and can be switched by binded devices or via zigbee2mqtt.
How to reproduce it (minimal and precise)
IKEA | E1812 | 20210727 | 2.3.080
IKEA | E1743 | 20210722 | 2.3.079
Zigbee2MQTT version
1.27.2
Adapter firmware version
20220219
Adapter
Slaesh CC2652RB
Debug log
No response
The text was updated successfully, but these errors were encountered: