Aqara Curtain Driver E1

2022.8.0 + ZHA let’s you reverse the open/close direction; yay!

1 Like

Don’t know if this has been in a recent firmware update, but pressing the reset button 3 times in quick succession reverses the rolling direction.

1 Like

Hi, I just got my E1 driver and installed at my curtain. So far no issue in integrating to z2m. Setting the travel limits also no hassle though bit tricky.

Uhm. So, I bought 2 of these. I have Conbee 1 attached to a NUC and HA 2022.8.6 version installed. I’ve never used any curtain or roller shade products (or any HA Cover products actually) and I’m a bit lost. I have a feeling that something is not working, but since I don’t know how they should work, it’s a bit tricky to troubleshoot.

So ZHA integration finds the driver and it says it’s integrated successfully. I get the device there and the cover with up and down arrows and the square button. But none of them do anything. Nor does the thing broadcast any state.

So basically I have no way to control these. If I click on the physical button on the product, it starts to move without any problems. But that’s it. It doesn’t know when to stop and so on.

My next move will be to upgrade the firmware on the Conbee 1 but if that doesn’t help then I’m out of ideas.

EDIT: Damnit. I’m on the latest firmware (from August 2021) already.

EDIT2: Apparently I can’t pair them with the Aqara E1 hub either. I got the hub in a bundle when I bought the drivers and figured I’d try that, even though it’s not the best idea to create another Zigbee network. But no luck there either. Quite troublesome.

Any suggestions?

Where do you got to change the direction? I can open and close them just fine in HA but no idea how to make it reverse?? I just physically have one turned around right now… does the trick but would be nice to have them both facing the same way.

You don’t see this?

Lol, I do, guess I wasn’t looking there at that drop down!

Update: Ok this is weird, only one of them has that control option…

Different question, have you seen where you curtains will just stay in a closing state? Like they don’t change from closing to closed? Wondering if something is off with the calibration of these. Not sure I set them up exactly right, as in what was your process of actually doing the setup, did you start with the device in the open position, then move it to the closed position and do the triple click on the button to set max range? Just wondering what steps you followed?

I have noticed that it doesn’t report its state very quickly. Pressing the identify button may help. And I noticed that service calls work far better than the buttons in the device controls. Aka, my lux-based automation to open/close works great, and so does “Hey Google”. But pressing the buttons (in HA) might not unless you press identify first. No biggie, since this is such a new device.

I followed the instruction booklet to manually set them up. Took a couple tries, resetting in between, before I figured it out.

Great, I reset and deleted both devices then re-added them thinking I would be starting over… now neither has the reverse control lol :frowning: UGHHH

So I got my left and right curtain motor setup and they seem to have good open and close positions… Only problem is, they are reversed, so when I open them, HA says they are closed and when they are physically closed, HA says they are open. I still don’t see the Configuration section on the device for either now :frowning:

You are using ZHA? What version of HA?

I have using ZHA, on the latest stable releases,

Home Assistant 2022.8.7
Supervisor 2022.08.5
Operating System 8.5
Frontend 20220802.0 - latest

Also fyi, when I go to add it/pair it, this is what it detects,

LUMI lumi.curtain.agl001

Might be best to enable debug logging, re-pair and submit an issue on GitHub.

Are your open and close states matched to your open and close buttons? Oddly enough if my curtains are closed and it’s status says closed, then slide the slider to the right to a value of 100 to open them, it works fine. But in that same scar io but hit the open button itself, it tries to close them again, it’s like the slider and status are good, but the open and close button are backwards?? I’ll post some bugs… hopefully it will help improve the integration

I have noticed the same thing with z2m. Using service calls to open/close work best for me.

I did the other way round. I first make sure the driver is in full closed position, triple click the button and it will move slightly till it hits the stop position and sounds a long beep. Then, I manually pull the curtain all the way to fully open position that I want and it will sound another long beep and this will be my full opened range.

This is how I set the travel range and I only have one driver at the moment. The second one is in shipment. But I think the same procedure should apply even with dual drivers according to the manual.

I did find the manual tells the different thing as it says it will move itself towards the full opened position and set the opened position when you pulled the curtain by ~10cm. For my case, it didn’t move and I have to manual pull them.

Hope it helps.

I have a couple of these and can answer a few of the questions on this thread:

  1. Yes when these are setup and configured without the aquara hub manual control works fine (you tug on the curtain and they open / close)
  2. you can set the direction of the curtain in the zigbee2mqtt settings:

I am really struggling to get them setup correctly though. The travel calibration without the aqara hub really seems to not work properly. I have either got into a state where the driver stops about 1" short leaving a 2" gap in the middle of my curtain pair when they are closed or there is no calibration and each driver runs for around 30 seconds after it has reached either end of the pole just spinning the wheel on the bar.

I also have issue with the wheel slipping on the bar…

I decided to return these. Too many problems for example with the wheel slipping. I finally got them paired with the Aqara E1 hub though, which helped a lot. Apparently it required three (!!) consecutive firmware upgrades to the hub. After the first it didn’t cross my mind that it would not upgrade it straight to the newest version.

In the end my main problem however was with the U-track I have. Here in Finland we basically don’t have U-tracks big enough for rollerglides. Maybe for commercial use, but they are too expensive. Without rollers the friction / load seems to get too big for the motor when closing the curtains.

Are you using the Aqara E1 USB hub? If yes, can the E1 hub be integrated to HA?

I’m thinking to get this hub also to be easier to work with this curtain driver and also the FP1 sensor. Plus, it can offer firmware upgrade also.

Currently I’m using them with z2m.

For those having issues getting these setup, ill just offer my experience after getting two more of these.

  1. I just have them paired with ZHA, but non of them have the reverse option in the settings (if you look back at my posts, one did for a little while until I re-paired it). not exactly sure why ZHA doesn’t have this option but apparently its a bug.

  2. When installing them, I followed this procedure.
    a. Pair the device to ZHA
    b. Close your curtain
    c. Lower the extension hook by double tapping the button
    d. Attach the Curtain Driver to the little mounting piece that goes over the rail and with the curatin still full closed, double tap the button to raise the mounting hooks.
    e. Once fully raised I triple click the button which I think sets the end (or start point depending on how you think about it).
    f. Last I pull the curtain gently to open the curtain and the motor driver should start opening the curtain and then set the maximum position from that.
    g. Now the tricky part, because I can’t inverse the driver in entity settings, if you find the device lists itself as open when its closed or vice versa, you have to essentially reverse how it works physically, this involves flipping the device by lowering the hooks and reattaching it, but also flipping what was the open and closed position… this really isn’t intuitive but it works to say the least.

I find this gets the job done, again its not perfect. If the entity driver were fixed to allow me to invert it more easily that would be great. Also the button to open and close does not work, only the position slider… so the drivers need some work to say the least :(. But it now works and I can open and close my curtains!

2 Likes