Open bjarnekrottje opened 9 months ago
Did you check the "Manage Zigbee device" -> "clusters" dialog? (Three dots on the device page)
Hi @TheJulianJES, that's a quick response. I did check it and do see the information available there. For example in this case the Operation Mode can be found here: Unfortunately you are not able at the moment to change this through the UI as for example a configuration property on the device page. Or is it because the data can be found in the "clusters" dialog the quirk is working correct, but somewhere else these properties have to be defined to show (and/or be configurable) in the UI? Thanks in advance!
Unfortunately you are not able at the moment to change this through the UI
You can change it on that page. Change the upper "value" field to 0
or 1
for example. Leave the lower text field empty. Then, press "write attribute". Afterwards, you can press "read attribute" to see if it correctly wrote that value.
But yes, ZHA config entities should be added for these custom attributes. (just not implemented yet)
Change the upper "value" field to
0
or1
for example.
Thank you very much for this tip. I tried entering OppleOperationMode.Coupled
or OppleOperationMode.Decoupled
and then pressing "write attribute", but that didn't work. Using 0
and 1
did the trick!
But yes, ZHA config entities should be added for these custom attributes. (just not implemented yet)
If that's something I could help with, please let me know. Happy to help and contribute to this, just not sure where to start to achieve this at the moment.
Just a quick related question, is the l1aeu1 also supposed to support the same features as the l2aeu1? In HA I only see the changes for my l2aeu1 device, and my l1aeu1 devices have not changed.
FYI, there is an indirectly inconsistency issue where the Aqara Wall Switch single and double rocker have different device type:
https://github.com/zigpy/zha-device-handlers/discussions/1957
There also seems to be a related bug that prevents users modifying the device type in ZHA without using a custom quirk:
Change the upper "value" field to
0
or1
for example.Thank you very much for this tip. I tried entering
OppleOperationMode.Coupled
orOppleOperationMode.Decoupled
and then pressing "write attribute", but that didn't work. Using0
and1
did the trick!But yes, ZHA config entities should be added for these custom attributes. (just not implemented yet)
If that's something I could help with, please let me know. Happy to help and contribute to this, just not sure where to start to achieve this at the moment.
I have been testing the double rocker no neutral version about the decoupled mode as that was a deal breaker for my use case
Did you find any way to set the switch to be on (rather than off) by default?
Problem description
Hi all,
Since the merge of #2784 (Thanks for that @TheJulianJES) in release 0.0.107 (which has now been merged into Home Assistant version 2023.12.0), a new quirk has been added for the device with id
lumi.switch.l2aeu1
.Unfortunately, it looks like not all functionality of the device is yet supported. Looking at the Zigbee2MQTT list of supported functionalities for this device it looks like some of the functionalities appear to not be available in this new quirk, like:
single_left
,double_left
,single_right
anddouble_right
appear to be working,single_both
anddouble_both
appear to not yet be working. Also thebutton_hold
event appears to be the same for both the left and right rocker, shouldn't these be different for each rocker?)Please add a comment or correct something if I am missing functionalities or have incorrectly labeled them here.
Solution description
I would like to see the quirk being updated to support the missing functionalities. I have tried looking into this myself, but unfortunately have not been successful yet. Especially the Operation mode (Decoupled or Coupled/Control_relay) functionality is important to me currently.
It does look like (some of) the functionalities have already been implemented.
For example: The quirk the device currently uses (
zhaquirks.xiaomi.aqara.switch_h1_double.AqaraH1DoubleRockerSwitchNoNeutralAlt
) has a base reference toXiaomiOpple2ButtonSwitchBase
, which itself has an endpoint of 1 and 2 with the input_clusterOppleSwitchCluster
. This input cluster contains a lot of the missing functionalities (like operation mode and switch type). I am wondering why they aren't showing up in the device when using this quirk then. I have yet to be able to determine the cause for this, maybe someone could clarify it.Screenshots/Video
Current functionality (since Home Assistant version 2023.12.0): (Looks like the image is not showing using the
<details>
syntax, so pasted it outside so it at least shows)Device signature
Device signature
```json { "node_descriptor": "NodeDescriptor(logical_type=Diagnostic information
Diagnostic information
```json { "home_assistant": { "installation_type": "Home Assistant OS", "version": "2023.12.0", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.11.6", "docker": true, "arch": "aarch64", "timezone": "Europe/Amsterdam", "os_name": "Linux", "os_version": "6.1.58-haos-raspi", "supervisor": "2023.11.6", "host_os": "Home Assistant OS 11.2", "docker_version": "24.0.7", "chassis": "embedded", "run_as_root": true }, "custom_components": { "grott": { "version": "1.1.0", "requirements": [] }, "volkswagen_we_connect_id": { "version": "1.0", "requirements": [ "weconnect==0.58.0", "ascii_magic>=2.0.0" ] }, "alarmo": { "version": "v1.9.13", "requirements": [] }, "hacs": { "version": "1.33.0", "requirements": [ "aiogithubapi>=22.10.1" ] }, "hass_agent_mediaplayer": { "version": "2022.5.6", "requirements": [] }, "afvalbeheer": { "version": "5.2.9", "requirements": [ "rsa", "pycryptodome" ] }, "multiscrape": { "version": "6.5.0", "requirements": [ "lxml==4.9.1", "beautifulsoup4==4.11.1" ] }, "dwains_dashboard": { "version": "3.6.0", "requirements": [] }, "hass_agent_notifier": { "version": "2022.10.25.1", "requirements": [] }, "webrtc": { "version": "v3.5.0", "requirements": [] }, "eufy_security": { "version": "7.7.4", "requirements": [ "websocket-client==1.4.2", "aiortsp==1.3.7" ] }, "watchman": { "version": "0.5.1", "requirements": [ "prettytable==3.0.0" ] }, "spotcast": { "version": "v3.6.30", "requirements": [] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "after_dependencies": [ "onboarding", "usb" ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly", "@TheJulianJES" ], "config_flow": true, "dependencies": [ "file_upload" ], "documentation": "https://www.home-assistant.io/integrations/zha", "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp", "universal_silabs_flasher" ], "requirements": [ "bellows==0.37.1", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.107", "zigpy-deconz==0.22.0", "zigpy==0.60.0", "zigpy-xbee==0.20.0", "zigpy-zigate==0.12.0", "zigpy-znp==0.12.0", "universal-silabs-flasher==0.0.15", "pyserial-asyncio-fast==0.11" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "0403", "pid": "6015", "description": "*conbee*", "known_devices": [ "Conbee III" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" }, { "type": "_uzg-01._tcp.local.", "name": "uzg-01*" }, { "type": "_slzb-06._tcp.local.", "name": "slzb-06*" } ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 11721, "manufacturer": "LUMI", "model": "lumi.switch.l2aeu1", "name": "LUMI lumi.switch.l2aeu1", "quirk_applied": true, "quirk_class": "zhaquirks.xiaomi.aqara.switch_h1_double.AqaraH1DoubleRockerSwitchNoNeutralAlt", "quirk_id": null, "manufacturer_code": 4447, "power_source": "Battery or Unknown", "lqi": 164, "rssi": -59, "last_seen": "2023-12-07T19:46:00", "available": true, "device_type": "EndDevice", "signature": { "node_descriptor": "NodeDescriptor(logical_type=Logs
Logs
I don't know if this is the correct piece of the debug logging, but here it is: ```python 2023-12-07 19:52:16.624 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'8160597e' 2023-12-07 19:52:16.627 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingMessageHandler: [Custom quirk
Not yet available
Additional information
I hope you can help me out figuring out how we can add these functionalities. I am willing to help create/improve the quirk, although I have been unsuccessful thus far. Thank you very much in advance for your help.