-
Notifications
You must be signed in to change notification settings - Fork 720
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] Decoupled mode for lumi.switch.l1aeu1 #1693
Comments
Same with the two rocker version (lumi.switch.l2aeu1). As for the temperature it seems Z2M exposes a calibration field, it'll probably be way off until we can get that calibration into HA. I've tried modifying the handler from the above PR to match the two rocker version but I can't get it picked up, not sure what I'm missing but I can't get it to work sadly.
|
Hey guys. Seems these EU buttons without neutral share the same clusters and attributes as their counterparts with neutral from #1391. Only the endpoints are a little bit different. By tweaking the endpoints descriptors slightly I was able to match signature of both 1 and 2 face devices and the OppleSwitchClusterer seems to work fine. What worked for me:
If you want to try you can create a folder
to your configuration.yaml and restart HA. I haven't written any python code ever before this attempt and also I'm not really familiar with zha and contribution guidelines, so I don't expect I will be making it official PR just yet. This way you can at least test it or use it until official support is done. |
Hey @moroz-slavomir, You succeeded where I failed, and I can see why, I forgot these are hexadecimal .. I was so close. I do wish these had a way to override the decoupled mode to force the relay without going through home assistant and supported binding, but that's nothing to do with the quirk. |
This has been working well, any chance to get that merged in ? |
Hi! |
@ardstuebck Maybe if you have also an aqara hub, try updating the firmware. It changed the endpoints on my switch. Before the update the quirk would not work. |
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 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. |
I tried using your quirk for my b2laus01 with no luck. Any ideas on what I can do to troubleshoot? I don't have a hub - it's connected directly to my HA setup. Is there a way to update firmware? |
I can confirm this was also the case for me. Needed to update the firmware first. After that the endpoints on the device have changed and quirk started to work. |
Hi, @moroz-slavomir witch device do you have and which firmware? I have a lumi.switch.l2aeu1 (Aqara H1 EU Double Rocker without Neutral) with Firmware 0.0.0_1411. I bought a Aqara E1 Hub to update the Firmware, but 0.0.0_1411 is the latest. The device Signatur in HA{
"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": "0x0104",
"device_type": "0x0100",
"input_clusters": [
"0x0000",
"0x0002",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0x0009"
],
"output_clusters": [
"0x000a",
"0x0019"
]
},
"2": {
"profile_id": "0x0104",
"device_type": "0x0100",
"input_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006"
],
"output_clusters": []
},
"242": {
"profile_id": "0xa1e0",
"device_type": "0x0061",
"input_clusters": [],
"output_clusters": [
"0x0021"
]
}
},
"manufacturer": "LUMI",
"model": "lumi.switch.l2aeu1",
"class": "zigpy.device.Device"
} Anyone else with this issue? |
I'm sorry, but I can't verify aqara firmware version anymore as I don't have the hub. It's possible they might have removed the update. Your signature resembles what my device looked like upon purchase. With firmware upgrade it now looks like this: Signature{
"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": "0x0104",
"device_type": "0x0100",
"input_clusters": [
"0x0000",
"0x0002",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0x0012",
"0xfcc0"
],
"output_clusters": [
"0x000a",
"0x0019"
]
},
"2": {
"profile_id": "0x0104",
"device_type": "0x0100",
"input_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0x0012",
"0xfcc0"
],
"output_clusters": []
},
"41": {
"profile_id": "0x0104",
"device_type": "0x0100",
"input_clusters": [
"0x0012"
],
"output_clusters": []
},
"42": {
"profile_id": "0x0104",
"device_type": "0x0100",
"input_clusters": [
"0x0012"
],
"output_clusters": []
},
"51": {
"profile_id": "0x0104",
"device_type": "0x0100",
"input_clusters": [
"0x0012"
],
"output_clusters": []
},
"242": {
"profile_id": "0xa1e0",
"device_type": "0x0061",
"input_clusters": [],
"output_clusters": [
"0x0021"
]
}
},
"manufacturer": "LUMI",
"model": "lumi.switch.l2aeu1",
"class": "switch_h1.AqaraSwitchH1NoNeutral_2G"
} The extra added cluster You could possibly create multiple Aqara accounts for other regions as well, (China, US, other EU country) and maybe this way to firmware update becomes available. FYI I'm situated in Czechia, if that helps. |
@moroz-slavomir Thank you for the tip. Unfortunately, there is no newer update for other regions either. I have also acquired an Aqara Smart Wall Switch E1 Dual Button. The same problem occurs here. Could it be related to my Zigbee stick? I am using a TI CC2531, Z-Stack Home 1.2. Thanks again for your support! |
I'm in the same boat - I didn't try other regions but the app reports I'm on the latest firmware. Decoupled mode exists in the official app but when I move the switch back to Home Assistant the signature is the same as before... I was hoping to keep everything in HA but I'd really like that virtual switch mode. Any ideas? |
The Quirk now works for me. I don't know if it's because I switched to the Sky Connect Stick. After repairing it several times it worked. Thanks for your help |
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 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. |
Still hoping this might happen |
I have a lumi.switch.l1aeu1 single rocker Aqara H1 EU switch without neutral wire paired with ZHA and it is missing a couple of things:
The on/off button is working well otherwise. It seems like Zigbee2MQTT is supporting this so it should be possible. Please let me know if any additional information is needed
Device signature
Diagnostic information
The text was updated successfully, but these errors were encountered: