Aqara Curtain Driver E1

Configuration Zigbee
32

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
33

The first position where you do the tripe click, it is always the full closed position. In order words, it will register the position to 0% as closed. Then, you pull the curtain and it will open till the end and register as 100% as open.

For z2m, we do have the inverse option. But for you case, can you setup the travel limits in inverse? Then you don’t have to flip the curtain driver manually and you will get the correct reporting in ZHA.

I have two of these drivers now and use them to open my left and right curtains and I don’t have to configure any of the driver to be inverse in the z2m. I just set the travel limits differently for each of the drivers.

34

I think the problem with doing the initial triple click in the opposite manner would mean that HA would think when its open its actually closed, and when its closed it will think its open because you are doing the initial triple click to set 0 in the open position which actually should be the closed position.

35

FWIW, I initially had problems with the wheel slipping. I realized the track it was running on was really smooth. I wiped it off with some rubbing alcohol (presumably some residual grease or something from the factory) which helped, then I also scuffed the surface with 60-grit sandpaper, which really helped

1 Like
36

I second this! Wiping with alcohol did not help much but slightly sanding the rail surface helped a lot!

37

Sorry if this shouldn’t be here, but I currently have 4 of these Curtain Driver E1 devices (firmware 0.0.0_0024) connected via Zigbee2MQTT (1.28.0) to HA (currently 2022.9.7).

I keep on getting the following errors in my HA log:

Logger: homeassistant.helpers.template
Source: helpers/template.py:582
First occurred: 10:57:32 (26 occurrences)
Last logged: 12:09:16

Template variable warning: 'dict object' has no attribute 'motor_state' when rendering '{{ value_json.motor_state }}'
Template variable warning: 'dict object' has no attribute 'motor_state' when rendering '{% if not value_json.motor_state %} stopped {% else %} {{ value_json.motor_state }} {% endif %}'

I have previously created an issue for this Xiaomi ZNCLBL01LM: Template variable warning: 'dict object' has no attribute 'motor_state' when rendering '{{ value_json.motor_state }}' · Issue #14023 · Koenkk/zigbee2mqtt · GitHub, and added the motor_state to the template Added 'pause' motor_state for lumi.curtain.agl001 by buhito81 · Pull Request #4673 · Koenkk/zigbee-herdsman-converters · GitHub which has become part of the Zigbee2MQTT release 1.28 - but I’m still getting this error.

Does anyone else experience this too?

38

Nope. This is not how it works in z2m. When you do triple click at closed position, it will register as 0 and you pull the curtain towards to open position and it will move all the way to open and register that to 100.

So it will remember which direction it will move as open.

39

Anyone having the same?

40

I managed to set mine up ok, all pretty straight forward really . My issue is the lumi sensor doesn’t show up in HA and apparently it does have one. I am very low down in the food chain when I comes to all this stuff so any help would be appreciated. Thanks

41

Created a GitHub issue for it. Any help would really be appreciated.

42

Hi, I am thinking about buying some of these.

Can someone give an update as to what works and what does over Z2M. I wont be using their hub and all HA based.

43

I’m about to make a purchase… did you?

44

Check this, Xiaomi ZNCLBL01LM control via MQTT | Zigbee2MQTT, I have 4 of them and this functionality sort of works - apart from some errors as described in Xiaomi ZNCLBL01LM: Template variable warning: 'dict object' has no attribute 'motor_state' when rendering '{{ value_json.motor_state }}' · Issue #15116 · Koenkk/zigbee2mqtt · GitHub. Otherwise, send me a PM if you have specific questions.

45

I also have these curtain drivers, and do not manage to get them properly working. I am using Node Red. The problem is a proper and ‘full’ recognition of the curtain driver.

Initially I was using a Sonoff P USB device (ZHA). That did lead to a minimal but very incomplete set of controls and information.

Than I updated the USB-software to https://github.com/Koenkk/Z-Stack-firmware/raw/master/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20221226.zip
Overall, that seems a small improvement, but still not really OK.

So, I decided to upgrade the USB to the advised Sonoff E USB, which as effect that the curtain driver does not work at all any longer :rage:

I also experimented with ‘ZhaQuirk_Aqara Roller Shade Driver E1 device.py’ … which had no noticeable impact

Then I did install MQTT / core-mosquitto … it is running, but no idea how to let it recognize the curtain driver … to be honest I do not even know if a combination of ZHA and MQTT is possible

What ever help is appreciated …

46

But what actually didn’t work? Could you specify? I’m looking forward to help

47

ZHA does not need MQTT and MQTT does not work with ZHA.
What you are looking for is MQTT and then Zigbee2MQTT

48

for all those for whom the curtain driver still slips through. I have found the perfect solution:

This window seal can be mounted on a U-profile as well as the rod. There are certainly in all countries.

1 Like
49

Could you help us out with some pictures as to how you used it?

50

PXL_20230221_141841986
PXL_20230221_1418419862098×1180 159 KB

PXL_20230221_141854876
PXL_20230221_1418548761920×1080 56 KB

1 Like
51

Thats pretty awesome!