Aqara Curtain Driver - Offline Issues

I have around 25 Curtain Drivers installed at home, but at any given time, 3–5 of them are offline, even when they’re located close to the hub. I often have to remove the accessory from my profile and re-add it, which is a time-consuming process to repeat each time. Is there a more efficient solution for this?

4 Likes

Hello, this topic (dismantling equipment) was discussed here. Maybe you have some other Aqara devices that work as repeaters, when you turn them off, there is a possibility that the entire Zigbee connection scheme breaks. Read the link I gave you so as not to repeat it on the forum pages.

1 Like

Sorry, but where is the link? The one you provided is for the water leak sensors, whereas I’m looking for solutions specific to the Curtain Driver. Thanks.

1 Like

The leak sensor and your curtain driver have the same communication algorithm with the gateway, so this is a general question about communication. You read about the leak sensor and think about your driver :slightly_smiling_face:

1 Like

If these are 220v motors, they are repeaters, there is still no network map. If these are battery motors, then they go to sleep to save battery power.

1 Like

I think by default that these are battery-powered drivers.

1 Like

how do you get them back online without having to reset them all over again?

What type of drivers do you have, what powers them (battery)?

Aqara Smart Curtain Motor E1 (Rod Version) - battery

1 Like

If the driver “fell off”, try to move it manually (physically with a button), and then see if it (wakes up) in the program. But I think this is related to the Zigbee network. Another option is that the battery is fully charged?

How many other Aqara devices do you have in your house that are powered by 220?
This is a question about 220, because I want to imagine how complex your Zigbee communication system is.
Another question is what are the distances between the drivers in the rooms and the gateway.
Answer these questions, maybe a picture of the problem will emerge.
Thank you.

Same issue on my side with the same model, tested as linked on different hubs (m3) , and manual movement or through the button are not re-enabling the driver from the hub. The only solution is to reset the driver (5 sec on the driver button) and to re-adopt it.
A firmware update should fix such issues.