-
Notifications
You must be signed in to change notification settings - Fork 721
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
[BUG] AQARA Roller Shutter ZHAQuirk not recognised #1801
Comments
Enable the local quirk: Copy inside the Add at the end of file this quirk: class RollerE1AQ_2(RollerE1AQ):
"""Aqara Roller Shade Driver E1 (version 2) device."""
signature = {
MODELS_INFO: [(LUMI, "lumi.curtain.acn002")],
ENDPOINTS: {
# <SizePrefixedSimpleDescriptor endpoint=1 profile=260 device_type=256
# device_version=1
# input_clusters=[0, 2, 3, 4, 5, 6, 9, 13, 19, 258]
# output_clusters=[10, 25]>
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
INPUT_CLUSTERS: [
Alarms.cluster_id,
AnalogOutput.cluster_id,
Basic.cluster_id,
DeviceTemperature.cluster_id,
Groups.cluster_id,
Identify.cluster_id,
MultistateOutput.cluster_id,
OnOff.cluster_id,
Scenes.cluster_id,
WindowCovering.cluster_id,
],
OUTPUT_CLUSTERS: [
Ota.cluster_id,
Time.cluster_id,
],
},
# <SizePrefixedSimpleDescriptor endpoint=242 profile=41440 device_type=97
# device_version=0,
# input_clusters=[]
# output_clusters=[33]>
242: {
PROFILE_ID: 41440,
DEVICE_TYPE: 0x0061,
INPUT_CLUSTERS: [],
OUTPUT_CLUSTERS: [
GreenPowerProxy.cluster_id,
],
},
},
} Restart HA and pair the device again. |
That fixed the problem! |
The quirk will be available in the next HA version. |
Hi i have 6 aqara roller shutter and sometimes more of them don’t react to my cover open o closed instructions but reports correctly temperature and battery. Also if I add again in the network without remove them start to works for a few hours. It’s not a coverage problem because I have a enough lqi. Any idea how to fix this problem ? |
Logger: homeassistant.components.websocket_api.http.connection [140153997668176] The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Copied from home-assistant/core#70837 since I have the same problem and it seems like it wasn't reported here while that's what was suggested there.
Describe the bug
The device pairs, but the zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ is not applied
To Reproduce
Pair the device
Expected behavior
The device should be matched to the quick
Screenshots
`2022-04-27 10:21:49 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for LUMI lumi.curtain.acn002 (54:ef:44:10:00:32:90:d1)
2022-04-27 10:21:49 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ'>
2022-04-27 10:21:49 DEBUG (MainThread) [zigpy.quirks.registry] Fail because input cluster mismatch on at least one endpoint
....
2022-04-27 10:21:49 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for LUMI lumi.curtain.acn002 (54:ef:44:10:00:33:ac:14)
2022-04-27 10:21:49 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ'>
2022-04-27 10:21:49 DEBUG (MainThread) [zigpy.quirks.registry] Fail because input cluster mismatch on at least one endpoint
....
2022-04-27 10:21:49 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for LUMI lumi.curtain.acn002 (54:ef:44:10:00:3e:35:9d)
2022-04-27 10:21:49 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ'>
2022-04-27 10:21:49 DEBUG (MainThread) [zigpy.quirks.registry] Fail because input cluster mismatch on at least one endpoint
...
2022-04-27 10:29:07 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for LUMI lumi.curtain.acn002 (54:ef:44:10:00:32:90:d1)
2022-04-27 10:29:07 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ'>
2022-04-27 10:29:07 DEBUG (MainThread) [zigpy.quirks.registry] Fail because input cluster mismatch on at least one endpoint
...
2022-04-27 10:29:07 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for LUMI lumi.curtain.acn002 (54:ef:44:10:00:33:ac:14)
2022-04-27 10:29:07 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ'>
2022-04-27 10:29:07 DEBUG (MainThread) [zigpy.quirks.registry] Fail because input cluster mismatch on at least one endpoint
...
2022-04-27 10:29:07 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for LUMI lumi.curtain.acn002 (54:ef:44:10:00:3e:35:9d)
2022-04-27 10:29:07 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ'>
2022-04-27 10:29:07 DEBUG (MainThread) [zigpy.quirks.registry] Fail because input cluster mismatch on at least one endpoint`
Additional context
Issues with this device are often caused by outdated ConBeeII firmware, but mine is up to date with https://deconz.dresden-elektronik.de/deconz-firmware/deCONZ_RaspBeeII_0x26780700.bin.GCF
The text was updated successfully, but these errors were encountered: