-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Device Support Request] Aqara Curtain Driver E1 (lumi.curtain.agl001) #2003
Comments
I have one of this for testing. The #1648 mentioned above works well to add battery level and direction control option. However there's something strange about this device. When I set As I understand this device also has a luminosity sensor, would be nice to have one available in Home assistant or to set rules for automatic opening/closing. |
For me, using the custom quirk only adds battery level, the direction control option doesn't show up for me. I tried updating the Aqara E1 Curtain driver to the latest firmware using an Aqara hub, but no joy. |
@circa1665 Did you check the clusters UI (with the custom quirk applied)? Go to the device page -> click the three dots -> Manage Zigbee Device. In the first dropdown menu, select |
Hi @TheJulianJES, thanks for the tip, I was able to reverse opening direction by reading attribute value of Unrelated, have noticed that battery state is now permanently "Unknown". |
@circa1665 Can you restart HA now and see if you get the config entity? |
@TheJulianJES, yes! The curtain mode entity is showing up now - although it's showing as "Normal", rather than "Inverted". |
Changing the curtain mode to "inverted" (whilst the device is awakened) should properly update the status there. home-assistant/core#75132 did not add the attribute to
|
Just to flag, the battery state is still "Unknown" so not a case of it coming back "after some time", thanks! |
What coordinator are you using? |
I'm using a SONOFF Zigbee 3.0 USB Dongle Plus with this firmware: https://github.com/Koenkk/Z-Stack-firmware |
I am trying to control a curtain set with two lumi.curtain.agl001 motors. Not so easy. Just as mentioned above I am missing
I can work around the reverse directions for the right curtain, but not around the other issues. But I have another major problem ..... that is the position of the motors. There is a command ^cover.set_cover_position^ and according to info found position has a range from 0 .. 100 where 0 = closed and 100 is open, (https://www.home-assistant.io/integrations/cover.template/) However that is where the problems are starting:
I have really no idea how to set those closed and open position reference points using the software What ever I would be very very very glad with an updated ZHA-driver and perhaps also firmware for this device !!! To work around the positioning issues, I consider to use sensors at the closed and open position at each site ..... So, again updates will be highly appreciated |
Have updated SONOFF Zigbee 3.0 USB Dongle Plus to latest firmware: https://github.com/Koenkk/Z-Stack-firmware/blob/Z-Stack_3.x.0_coordinator_20221226/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20221226.zip |
So from the original list, looks like:
Would be great to get the remaining points working, is there anything I can do to help? |
Actuality I am using the latest Home Assistant version 2023.2.2 version and probably more relevant the recent Sonoff E USB (EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis by ZHA). Before I used the older Sonoff P USB. Since I made that move, the position slider and the related the set_cover_position command is gone. Since I used to open and close the curtains with the cover_position command (which was more reliable then the open/close command) from the gui and even more relevant from node-red, two points:
|
I added my Aqara E1 curtain driver to Home Assistant Bridge/HomeKit and now the battery sensor works. I've noticed that the state of the entity gets stuck on opening/closing so I've had to create an automation to listen for the events I've also noticed that when I interact with the curtain ( Lastly this doesn't seem to play nice with Home Assistant Bridge/HomeKit, can't operate this device from HomeKit. |
How do you add it to HomeKit and why does the battery work with this method? I thought HomeKit didn't support Zigbee without a Zigbee bridge? |
@Hamish1066, I don’t know why, the battery sensor just started working when I did. I use the HomeKit integration in Home Assistant to make some devices available to control via Homekit. |
@circa1665 I'm also using the HomeKit integration but battery status isn't showing up in HA for me. Weird. |
Recently migrated to Home Assistant Yellow, now the Aqara Curtain Driver E1 does not work with ZHA. This is the only zigbee device I've had any trouble with. Wondering if this might be because Home Assistant Yellow radio type is EZSP, whereas my previous coordinator was a Sonoff ZBDongle-P CC2652P (Texas Instruments based)? Sounds like LouisAtGH was describing something similar. I can get the device to pair if I try repeatedly. But cannot control the device at all. I can't read the reading attribute value of |
Much as I would love to get this working with ZHA, doesn’t appear that’s going to happening anytime soon. Ended up purchasing an Aqara E1 hub USB dongle. Now have this working via HomeKit controller in Home Assistant. The reversing direction isn't exposed as an entity in HA and has to be setup via the Aqara Home app. I now have a functioning cover entity and battery level in Home Assistant which will have to do for now. |
Tja I undestand, but for me that is the wrong direction. HA should be in control, not the suppliers cloud! I have the curtains working, using node-red and sensors at the begin and end of each curtain side. |
I appreciate all the work that @circa1665 has done on this, but I also agree with @LouisAtGH that the goal should be local integration. For me, almost everything works using the device with ZHA. The only quirks are that (1) the battery sensor doesn't show up; and (2) I can't use the open/close function, but it works instead to set a position (i.e. 0-100%). So for me it is totally usable with ZHA, just not perfect. |
I have four of these. Two on two windows. I just applied the custom quirk and battery level is properly exposed on all four units. I'm observing similar behaviours as others with regards to their state. State, current_position and sending open or close commands through the GUI in HomeAssistant are very inconsistent. Sending open or close commands through Home Assistant service calls works 100% of the time. EDIT: that said, even though they move in the correct direction for open and close, when they do report their current_position_lift_percentage it is inverted relative to what Home Assitant is expecting (100 is open, 0 is closed). The custom quirk inverts the position value if the direction is inverted but, at least with my four, the position value should be inverted in the normal direction instead. |
Could you please explain what the custom quirk is. Sorry if I’m missing something. |
It is the PR mentioned in the original post: |
Is there any testing that needs to be done? I've just received a new one of these and was hoping it would be easily integrated in to HA. The existing quick PR also has an unknown battery for me and did not reverse directions. or give me any new options to. |
plus 1 - can help with testing, im using lumi.curtain.agl001, firmware 0x0000001b with sonoff Zigbee |
Please help with testing #2629 and let's continue the discussion there. |
Is your feature request related to a problem? Please describe.
Am able to open and close curtains using the controls in HA, however have to physically turn the device around to change opening direction. The device supports reversing direction, but an entity for this does not appear in ZHA, neither does the battery level. Power source is incorrectly listed as mains powered and device firmware version is not listed.
Lastly, the device has a light level sensor but again no entity for this in ZHA.
Describe the solution you'd like
Device signature
Diagnostic information
Additional logs
Additional context
https://zigbee.blakadder.com/Aqara_ZNCLBL01LM.html
There's a pr for this device here, but it would appear progress has stalled. This currently adds support for the battery level sensor, but the reversing direction and light level sensor don’t work.
The text was updated successfully, but these errors were encountered: