ZHA: PARASOLL Door/Window Sensor switching Router lumi.plug.maeu01 off

Configuration
,
1

Hi!

I have had multiple lumi.plug.maeu01 plugs running as zigbee routers for a long time without problems.

Now I have integrated some IKEA PARASOLL Door/Window Sensor (FW: 0x01000019) into the network and I start to have issues with the lumi.plug.maeu01 used as a router for that device!

When the door closes the Zigbee Router the Parasoll is connected to has its Relay switched off.

I read somewhere that there is a “clash” with default groups between Ikea and Aquara, but I am unable to find a way to correct the situation.

Any help would be appreciated!

2

The one thing I find when I reconfigure the device and have enabled debug logging is:

2024-07-28 12:25:15.034 DEBUG (MainThread) [zigpy.device] [0xcd2e] Removing endpoint 1 from group 0
2024-07-28 12:25:15.131 DEBUG (MainThread) [zigpy.device] [0xcd2e] Removed endpoint 1 from group 0

(hint for that pattern comes from zha-device-handlers/zhaquirks/xiaomi/aqara/plug_eu.py at a6d414dea6d3513a659bd1c7265cb6c9d45e0316 · zigpy/zha-device-handlers · GitHub)

And strangely: all 4 of my plugs have different (quirks) classes:

  "class": "zhaquirks.xiaomi.aqara.plug_eu.PlugMAEU01Alt1"
  "class": "zhaquirks.xiaomi.aqara.plug_eu.PlugMAEU01Alt2"
  "class": "zhaquirks.xiaomi.aqara.plug_eu.PlugMAEU01"
  "class": "zhaquirks.xiaomi.aqara.plug_eu.PlugMAEU01"

while the Parasol device has class:

zigpy.device.Device

(so no quirks)

What seems to me is that Conbee is disconnected from Group0, but the Routers still listen on that Group in any case.

Home Assistant: 2024.7.3
Conbee II: Firmware: 0x26780700 (which is I believe the latest)

3

Unfortunately there has been no solution proposed.
So my solution to make those aquara plugs only act as repeater but without anything sensitive attached and have some automation that turns the device on again in case it is off…

4

Hi!

I case you or anyone else are still trying to solve this;

I have the exact same issue with the IKEA PARASOLL sensor turning off the Aqara plugs, but its a known issue for a while and also happens with some other other devices using the Aqara plug as a router.

It seems that firmware >v32 for the plugs causes this to happen. Downgrading the firmware to v32 seems to work a lot better for a lot of users. You can find more info in this thread.

I haven’t tried it myself yet as I am still reading about how to downgrade the firmware as its a bit different then described in the topic with the changes you have to make to the configuration.yaml file because of newer versions of HASS, but ill let you know if it works!

Update; My Aqara plugs updated to firmware v45 and dont have this behaviour anymore :smiley: