ZHA not recognizing the Aqara Roller Shutter E1 correctly #86752

MTrab · 2023-01-26T20:59:57Z

The problem

I have 4 Aqara Roller shutter devices, only 1 of these are recognized correctly by ZHA even thou they are bought at the same time.

The ones not working are not responding to open/close commands, they have a switch (?!) exposed (the working one doesn't), no battery info and device temperature reports a static 0.3C

What version of Home Assistant Core has the issue?

Home Assistant 2023.1.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA with SkyConnect

Link to integration documentation on our website

No response

Diagnostics information

Working:
zha-9b654b0da4346ac555f8c3518151a96a-LUMI lumi.curtain.acn002-51dd2113f6d91475ac8b7df9ef5af72d.json.txt

One of the non working devices:
zha-9b654b0da4346ac555f8c3518151a96a-LUMI lumi.curtain.acn002-a590cf80ea73f711aa8cbd4025fc73d1.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant · 2023-01-26T21:07:06Z

Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Change the title of the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

zha documentation
zha source
_{^{(message by IssueLinks)}}

TheJulianJES · 2023-01-28T23:56:33Z

Did you all pair them with Home Assistant Core 2023.1.2 or later (or were they paired on a previous version)?
Can you try completely re-pairing the non-working ones? (There was an issue with Xiaomi IEEE prefixes: zigpy/bellows#520)

MTrab · 2023-01-29T06:03:51Z

They were paired with the latest version.And I have tried deleting and pairing again, several times.The non working ones does not get the correct quirk registered, and can't find anywhere I can set this manually.Med venlig hilsen / Regards,Malene Trab29. jan. 2023 00.56 skrev TheJulianJES ***@***.***>: Did you all pair them with Home Assistant Core 2023.1.2 or later (or were they paired on a previous version)? Can you try completely re-pairing the non-working ones? (There was an issue with Xiaomi IEEE prefixes: zigpy/bellows#520) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

SGXander · 2023-01-30T08:51:54Z

+1 on this, Just bought and E1 and pairing seems to be faulty. When pairing, ZHA page goes from ready back to initialising then back to ready and the E1 flashes rapid blue for a full 5 minutes. In HA the control page looks like the below screenshot flicking between unavailable and ok. When the pairing mode on the E1 stops it will settle into ok but neither the cover nor identify actions have any effect and the temperature never changes. After the 6 hour timeout for battery devices it will go unavailable indefinately.

edit: I'm using a TubesZB as a zigbee bridge to my HA VM

MTrab · 2023-01-30T08:58:51Z

Yeah - same as mine.
Looks like the quirks isn't assigned as supposed for this device.
Only one of mine got the correct quirk

SGXander · 2023-01-30T09:02:12Z

I'm no zigbee or zha expert but is there a way to define the devices ieee as a specific type in the config as a workaround?
I'm having a read of: https://www.home-assistant.io/integrations/zha/#modifying-the-device-type to see

SGXander · 2023-01-30T10:07:52Z

if you can extract the quirks from your working one it may be possible to import using this: https://www.home-assistant.io/integrations/zha/#configuration-variables ?

MTrab · 2023-01-30T10:15:22Z

Not sure how to do that. Haven't, yet, figured out how that works 😁

SGXander · 2023-01-30T12:02:43Z

I don't have an aqara hub but if you do can you pair them to that and see if it's a result of newer/older firmware?

MTrab · 2023-01-30T12:19:23Z

Nope, I don't - only have a Conbee II (currently not used) and my SkyConnect

MTrab · 2023-02-05T15:27:02Z

Might just go and migrate back to Z2M, as ZHA still doesn't seem mature for production instances.

stefbontinckx · 2023-02-08T20:56:50Z

I have the same issue with Skyconnect and ZHA.

SGXander · 2023-02-11T19:05:02Z

2022.2.1 seems to be an improvement. Device doesn't go into unavailable and the identify button press works. All other features reamin the same though.

MTrab · 2023-02-11T19:11:41Z

I see no improvements. Have moved the Rollers back to Z2M on my Deconz dongle, but trying ZHA on every update, but no improvements at all.

SGXander · 2023-02-11T19:15:45Z

on the one that worked for you can you extract your signature and paste here please? I'm going to have a go at a quirks file...

MTrab · 2023-02-11T19:16:28Z

Tell me how ;)

SGXander · 2023-02-11T19:24:53Z

If you go to the device page then ... and manage zigbee device there should be a signature tab. pretty sure it doesn't contain any identifying info it's just config registers. hoping by comparing to my faulty one I can figure out what's wrong with it. playing in the write attribute section I can actually get mine to roll up and down so pretty sure it is ok its just the translation to home assistant that isn't working...

MTrab · 2023-02-11T19:26:21Z

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0202",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0002",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0009",
        "0x000d",
        "0x0013",
        "0x0102",
        "0xfcc0"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "242": {
      "profile_id": 41440,
      "device_type": "0x0061",
      "in_clusters": [],
      "out_clusters": [
        "0x0021"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.curtain.acn002",
  "class": "zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ"
}

SGXander · 2023-02-11T19:31:31Z

interesting the differences to mine:

couple of in clusters but crucially the class is just device.device for me. couldn't be that easy but I'm going to have a go at a custom quirk file to change the class...

dawidcieszynski · 2023-02-11T20:07:22Z

I had a similar problem. Bought two devices. Both shown 0.3 °C. I've played a bit with setting min and max on the devices. Then after few hours I've realized that one of the devices started to work, there were proper quirk used.

I've disabled quirks (because I observed that quirks changes the signature), restarted HA, compared the signatures and the not working device had other device_id (0x0202) than working (0x0100) and one of in_clusters
So I made a custom quirk using instructions from zigpy/zha-device-handlers#1801 (comment) (this quirk is already in HA, but with different device id, that's why I had to make my own one)
I've changed
DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
to
DEVICE_TYPE: 0x0202,

Now both works, reports correct data, opens and closes roller shutters. The only not working part is the slider, but it isn't a must. :)

I have Home Assistant 2023.2.3 with Sonoff ZBDongle-E (EFR32MG21)

MTrab · 2023-02-11T20:58:25Z

Thanks @dawidcieszynski

Can confirm all is working, except temperature, with this: https://github.com/MTrab/HAConfig/blob/master/custom_zha_quirks/roller_curtain_e1.py

Made following the guide you linked

SGXander · 2023-02-11T20:58:38Z

can confirm this fixes the cover entity and its position marker as well as removing the useless switch. can probably remove the number entity too which should be relatively easy now I have that example quirks file (thank you!)

SGXander · 2023-02-11T21:00:05Z

I can't find anywhere the zha.devicetype.xxx types are enumerated. we should really use the variable name as opposed to direct code but I wonder if there is a slightly different cover id that will fix it completely?

MTrab · 2023-02-11T21:02:26Z

Okay - temperature was just a tad slow to update - everything works with the one on my repo

MTrab · 2023-02-11T21:03:51Z

And yes - agree, an enumerator should be used for device type

SGXander · 2023-02-13T09:13:08Z

Think I've found the definitions: https://github.com/zigpy/zigpy/blob/dev/zigpy/profiles/zha.py
WINDOW_COVERING_DEVICE = 0x0202
Will test changing it to "zha.DeviceType.WINDOW_COVERING_DEVICE" shortly

the question then is why doesnt the replacement function above your addition work?

applegeeks · 2023-05-22T22:16:59Z

ah nice...i did restart and updatre ha but to no avail.
I did however not try plugin the dongle in and out again.

I wonder if that's what did it and I didnt have to re-flash the firmware?
might have to give this a try if I find myself ordering my third Aqara roller device.

nworbneb · 2023-05-23T16:56:51Z

Hello, I'm still having problems with this. It mostly works but not as well as people seem to have above.

Setting an opening percentage works
Displays correct opening percentage if you specify a percentage, i.e. with slider or Alexa
However, often loses up or down arrow even if percentage is not 0 or 100, i.e. greyed out in GUI
Percentage does not update if you use the arrows to fully open or close
Battery = "Unknown"
Device Temperature = "0.3 degC"

I'm running:

HA 2023.5.3
SkyConnect latest firmware 7.2.2.0
Latest Aqara firmware: 20221009111923_OTA_lumi.curtain.acn002_0.0.0_1530_20221009_6C9C3D.ota, version: 3870
Quirk: zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ_3

Diagnostics:

zha-70d9316c6d191d1748701b7433055d4b-LUMI lumi.curtain.acn002-8907207564c13de75d1a2af23fd8b76f.json (2).txt

jankowski-piotr · 2023-05-23T21:22:10Z

@nworbneb I think you need to set opening limits on the device itself with hardware buttons. https://manuals.plus/aqara/roller-shade-driver-e1-manual#device_rotating_range_setup

nworbneb · 2023-05-24T08:32:06Z

@nworbneb I think you need to set opening limits on the device itself with hardware buttons. https://manuals.plus/aqara/roller-shade-driver-e1-manual#device_rotating_range_setup

The device itself is configured and works fine manually, and for the most part, ok with zigbee. The main problem is battery status, and to a lesser extent, device temperature are not reported correctly.

The disconnect between top and bottom of travel and percentage opening might be a higher level HA issue? I've seen this reported with other non-Aqara devices.

Example: Can't raise blind from 75%

adamxp12 · 2023-06-11T21:32:50Z

Bought two Aqara E1 rollers recently. after having one previously for a while. One of them works perfectly but the other one is like all the others here. it uses the RollerE1AQ_2 quirk instead ofRollerE1AQ and for whatever reason that means the battery percentage is missing, the temperature sensor is 0.3 and it acts rather odd on the state if you use the up/down buttons.

Updated the Sonoff zigbee plus 3.0 USB to latest firmware and repaired but still no dice. I would rather not get an aqara hub to "update" the motor if I have to. seeing as the two units I got have the exact same manufacturer date I find it hard to believe that it is even running different firmware to the working one. Very odd

Hopefully someone can chime in with a proper fix for this
BrokenBlind.txt

WorkingBlind.txt

JoelMSawyer · 2023-07-17T13:42:54Z

I'm having similar issues to others here with my Aqara E1 roller shade driver. It uses the zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ_2 quirk that others have reported to be problematic. Temperature is always reported as 0.3C, the battery state is not reported, and the blind's open/close state is not correctly reported.

I've tried re-pairing the device to HA several times, with no improvement. I'll try updating my Conbee II's firmware, however I doubt that will be the issue as I don't think it's running a particularly out of date version. If anyone has any other suggestions, I'd be very interested to try them.

adamxp12 · 2023-07-19T14:12:43Z

Bought a brand new HASS SkyConnect as I saw lots of issues with the Sonoff dongles, But alas this issue still effects one out of the 2 blind motors I own both from same batch so I am doubtful of different firmware. oh well no loss as the SkyConnect will be better long term.

Looks like an Aqara hub to update firmware might be the only way to fix these. So annoying because it seems to be entirely ZHA issue and am not prepared to move to Z2M for this one device

MTrab · 2023-07-19T15:17:30Z

Did you try the custom_quirk mentioned in this thread?
I'm using it without problems on my roller drivers.

nworbneb · 2023-07-19T15:36:12Z

Bought a brand new HASS SkyConnect as I saw lots of issues with the Sonoff dongles, But alas this issue still effects one out of the 2 blind motors I own both from same batch so I am doubtful of different firmware. oh well no loss as the SkyConnect will be better long term.

Looks like an Aqara hub to update firmware might be the only way to fix these. So annoying because it seems to be entirely ZHA issue and am not prepared to move to Z2M for this one device

I updated to the latest firmware using ZHA (no need for Aqara hub) using 20221009111923_OTA_lumi.curtain.acn002_0.0.0_1530_20221009_6C9C3D.ota - this reports as firmware 0x00000f1e. It didn't resolve the issue.

Ref: https://github.com/Koenkk/zigbee-OTA/blob/master/index.json

nworbneb · 2023-07-19T15:36:41Z

Did you try the custom_quirk mentioned in this thread? I'm using it without problems on my roller drivers.

I don't believe the custom quirk is required as it is already commited.

adamxp12 · 2023-07-19T15:37:18Z

@MTrab I have tried that as well as latest skyconnect firmware but still only one blind is working. I posted the debug data of my working and broken one above. this is so strange

MTrab · 2023-07-19T15:37:21Z

Did you try the custom_quirk mentioned in this thread? I'm using it without problems on my roller drivers.

I don't believe the custom quirk is required as it is already commited.

Since when?! Last time I checked it wasn't commited with my changes.

MTrab · 2023-07-19T15:41:51Z

@MTrab I have tried that as well as latest skyconnect firmware but still only one blind is working. I posted the debug data of my working and broken one above. this is so strange

The one I have posted?
In that case it should be registred like this:

Note the Quirk line.

adamxp12 · 2023-07-19T15:45:40Z

Mine seems the same except I was lazy and named the file e1.py so its not like for like but 100% using your custom qurik

nworbneb · 2023-07-19T15:46:47Z

Did you try the custom_quirk mentioned in this thread? I'm using it without problems on my roller drivers.

I don't believe the custom quirk is required as it is already commited.

Since when?! Last time I checked it wasn't commited with my changes.

Someone else raised a pull, it's listed as version 3 (rather than 2a) but otherwise identical:

zigpy/zha-device-handlers#2341

adamxp12 · 2023-07-19T15:55:19Z

Tried the OTA update file mentioned above. but dont seem to want to upgrade. But I dont feel like I need to because the working one has exact same file version 3614 so yet again the issue seems to be HASS not the blind motor

adamxp12 · 2023-07-20T12:31:59Z

Okay got the firmware on the broken E1 to the latest 3870 same as the working one which updated itself.

And have the latest firmware on my skyconnect. so exactly like the people here with working ones. yet it still chooses the broken quirk over the working one.

Looks like I will just have to run Z2M because this bug dont seem to be fixable

MTrab · 2023-07-20T12:34:54Z

You need to delete and repair it formitnto change quirk.
It doesn't change once paired

adamxp12 · 2023-07-20T13:03:17Z

Define delete and repair?

I have been using the remove button in HA ad then putting the E1 into pairing mode and readding it

MTrab · 2023-07-20T13:10:40Z

Okay, then it should be fine

adamxp12 · 2023-07-20T13:14:04Z

Sadly continues to give me grief. I have zero clue why one works and one dont.

I feel like I need to reboot/factory reset the E1 but I cant seem to do that as it will repair itself everytime and dont seem to actually reset because it remembers top/bottom. starting to wonder if its actually faulty in some way

Someone needs to release a blind motor thats not garbage. all we have are this buggy Aqara and the Tuya version of it which seems identical but offers no battery gauge (not that it works on the Aqara when its such a common issue not pairing correctly)

MTrab · 2023-07-20T13:15:26Z

Sorry to hear you have problems with the device.
I have no issues with the 4 I have, after I have added my custom quirk.

adamxp12 · 2023-07-20T13:36:52Z

I 100% believe that this issue is a combination of things. I think HASS is not talking to it properly during the pairing stage. so the E1 is not exposing the right clusters? I bet Z2M would help

But I also feel like the E1 is just not exposing them to begin with which might explain why some people have success pairing with the actual Aqara hub then repairing with HASS. I bet the Aqara hub is sending some extra commands or something to wake the device up??

Does not explain how I have had one for years working and 1/2 of the brand new ones worked fine too. but the 3rd one which is identical hates life

adamxp12 · 2023-07-20T13:54:45Z

Welp I paired with Z2M and battery showed properly but not device temperature. Repaired with ZHA and same no battery and always thinks its open garbage. urghhhh. I really dont want to move to Z2M but looks like ZHA is just not mature enough (though this is the first issue I have had with many zigbee devices in my setup)

adamxp12 · 2023-07-20T13:58:11Z

Okay soz for the spam but I think I figured something out. I fully shut the blind then repaired and it worked... No idea why. but this info might help someone fix this issue

adamxp12 · 2023-09-18T14:36:21Z

Just got 2x more motors in. new issue. same firmware as the now fully working 2x I had before. but these new ones refuse to give a battery percentage. I can get working temperature readings though. Using the quirk from above on the same firmware as before. have tried pairing multiple ways now. The actual blind and temperature work as expected so its like the blinds are just not giving out battery info? but the other 2x on same firmware work fine still

Over the past week of having the two new ones the same error has been logged by ZHA
Using a skyconnect with lastest irmware and HASS 2023.9.2

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/bellows/ezsp/__init__.py", line 485, in handle_callback
    handler(*args)
  File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 509, in ezsp_callback_handler
    self._handle_frame(*args)
  File "/usr/local/lib/python3.11/site-packages/bellows/zigbee/application.py", line 554, in _handle_frame
    self.packet_received(
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 1010, in packet_received
    self.handle_message(
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 526, in handle_message
    return sender.handle_message(
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 367, in handle_message
    self.endpoints[src_ep].handle_message(
  File "/usr/local/lib/python3.11/site-packages/zigpy/endpoint.py", line 235, in handle_message
    handler(hdr, args, dst_addressing=dst_addressing)
  File "/usr/local/lib/python3.11/site-packages/zigpy/zcl/__init__.py", line 430, in handle_message
    self.handle_cluster_general_request(hdr, args, dst_addressing=dst_addressing)
  File "/usr/local/lib/python3.11/site-packages/zigpy/zcl/__init__.py", line 476, in handle_cluster_general_request
    self._update_attribute(attr.attrid, value)
  File "/usr/local/lib/python3.11/site-packages/zhaquirks/xiaomi/__init__.py", line 325, in _update_attribute
    self.endpoint.power.battery_percent_reported(
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zigpy/zcl/__init__.py", line 845, in __getattr__
    raise AttributeError(f"No such command name: {name}")
AttributeError: No such command name: battery_percent_reported

The existing blinds seem to be working fine still.

Looks like probably upstream changes that are effecting this quirk? https://github.com/zigpy/zha-device-handlers/commits/dev/zhaquirks/xiaomi/__init__.py

I have removed the custom qurik and gone back to the included zha quirks and battery works fine... so seems like its no longer needed

issue-triage-workflows · 2023-12-17T16:09:07Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

thecode added the integration: zha label Jan 26, 2023

home-assistant bot assigned dmulcahey, Adminiuga and puddly Jan 26, 2023

issue-triage-workflows bot added the stale label Dec 17, 2023

issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 24, 2023

github-actions bot locked and limited conversation to collaborators Jan 23, 2024

ZHA not recognizing the Aqara Roller Shutter E1 correctly #86752

ZHA not recognizing the Aqara Roller Shutter E1 correctly #86752

Comments

MTrab commented Jan 26, 2023

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

home-assistant bot commented Jan 26, 2023

TheJulianJES commented Jan 28, 2023

MTrab commented Jan 29, 2023 via email

SGXander commented Jan 30, 2023 • edited

MTrab commented Jan 30, 2023

SGXander commented Jan 30, 2023

SGXander commented Jan 30, 2023

MTrab commented Jan 30, 2023

SGXander commented Jan 30, 2023

MTrab commented Jan 30, 2023

MTrab commented Feb 5, 2023

stefbontinckx commented Feb 8, 2023

SGXander commented Feb 11, 2023

MTrab commented Feb 11, 2023

SGXander commented Feb 11, 2023

MTrab commented Feb 11, 2023

SGXander commented Feb 11, 2023

MTrab commented Feb 11, 2023

SGXander commented Feb 11, 2023

dawidcieszynski commented Feb 11, 2023

MTrab commented Feb 11, 2023

SGXander commented Feb 11, 2023

SGXander commented Feb 11, 2023

MTrab commented Feb 11, 2023

MTrab commented Feb 11, 2023

SGXander commented Feb 13, 2023

applegeeks commented May 22, 2023

nworbneb commented May 23, 2023 • edited

jankowski-piotr commented May 23, 2023

nworbneb commented May 24, 2023 • edited

adamxp12 commented Jun 11, 2023 • edited

JoelMSawyer commented Jul 17, 2023

adamxp12 commented Jul 19, 2023

MTrab commented Jul 19, 2023

nworbneb commented Jul 19, 2023 • edited

nworbneb commented Jul 19, 2023

adamxp12 commented Jul 19, 2023

MTrab commented Jul 19, 2023

MTrab commented Jul 19, 2023

adamxp12 commented Jul 19, 2023

nworbneb commented Jul 19, 2023 • edited

adamxp12 commented Jul 19, 2023

adamxp12 commented Jul 20, 2023

MTrab commented Jul 20, 2023

adamxp12 commented Jul 20, 2023

MTrab commented Jul 20, 2023

adamxp12 commented Jul 20, 2023

MTrab commented Jul 20, 2023

adamxp12 commented Jul 20, 2023 • edited

adamxp12 commented Jul 20, 2023

adamxp12 commented Jul 20, 2023

adamxp12 commented Sep 18, 2023 • edited

issue-triage-workflows bot commented Dec 17, 2023

SGXander commented Jan 30, 2023 •

edited

nworbneb commented May 23, 2023 •

edited

nworbneb commented May 24, 2023 •

edited

adamxp12 commented Jun 11, 2023 •

edited

nworbneb commented Jul 19, 2023 •

edited

nworbneb commented Jul 19, 2023 •

edited

adamxp12 commented Jul 20, 2023 •

edited

adamxp12 commented Sep 18, 2023 •

edited