Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.17k stars 1.68k forks source link

IKEA E1743 kicking out Aqara motion sensor #3030

Closed mr2c12 closed 4 years ago

mr2c12 commented 4 years ago

This problem is driving me crazy. Sometimes (like 1-2 times a day) the Ikea E1743 on/off remote takes a long time to get back (i.e., you press the button, nothing happens, no log from z2m, no mqtt message, so on). After several button presses, than it comes "online" and works as usual. When this happens, the Aqara motion sensor 0x00158d00019fdd44 disappears. Nothing is received by z2m, even if the motion is triggered for sure.

When the E1743 is already "online" (i.e., immediately react to the button press) this is not happening. The two devices are quite close (like 1 meter apart). In the same area (1 square meter..) there are a bunch of devices:

This is the map. I added a red arrow pointing from the offending device to the "victim". graph (1)

This has been happening for two days now. Anyway, in the latest few days, I:

Adding another router in the same area didn't change. Any other end device seems unaffected.

Can you please help me?

Koenkk commented 4 years ago

Could you sniff the network when this happens? https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

mr2c12 commented 4 years ago

Sure. I just installed and configured the necessary tools. Already tried a first capture but.. the remote was "online" and the problem didn't occured. Anyway, keeping the capture just in case. Will try later or maybe tomorrow and let you know.

I suspect something is going on with the ikea remote sleep.

Hilpas commented 4 years ago

I also discovered major stabillity problems with my z2m network and i actually added two E1743 lately. Some devices simpliy dropping off the network which can only be recovered by either restarting or pairing it again. I will remove my two remotes and try whether that fixes it for me.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

mr2c12 commented 4 years ago

I hae not been able to replicate the problem.