Replies: 4 comments 1 reply
-
For now, I was able to create a custom quirk that fixed this, by making the double rocker a light switch once again. |
Beta Was this translation helpful? Give feedback.
-
Also see this section for modifying the device type without using a custom quirk: https://www.home-assistant.io/integrations/zha/#modifying-the-device-type The switches should behave the same though and quirks should be fixed. Changing the device type will be a breaking change for users though. |
Beta Was this translation helpful? Give feedback.
-
I think should would be great, as long as mention the breaking change in the release changelog. Anyway, just wanted suggest notifying the writer of Home Assistant release notes when zha-quirks get bumped there so that they mention it under their "Breaking changes" section. |
Beta Was this translation helpful? Give feedback.
-
FYI, related consistency issue now also reported here -> home-assistant/core#101093 |
Beta Was this translation helpful? Give feedback.
-
For some reason, the 2 versions of the Aqara US Wall Switch No Neutral, lumi.switch.b1naus01 (Single rocker) and lumi.switch.b2naus01 (Double rocker) behave in different ways under HA.
I've tracked the reasons for a long time, and apparently while the "b1naus01" are just handled as any zigpy device, "b2naus01" is handled via a quirk (zhaquirks.xiaomi.aqara.opple_switch.XiaomiOpple2ButtonSwitchFace2)
This means that, while the "b1naus01" switch is treated as a Light (ON_OFF_LIGHT = 0x0100), the "b2naus01" switch is treated as a generic Switch (ON_OFF_SWITCH = 0x0000).
This obviously means that half the switches in the house are handled one way, while the other have are handled differently
I'm not sure if this should be fixed through a modification of the XiaomiOpple2ButtonSwitchFace2 Class; trough adding a new class to handle the b1naus01, or just through a local quirk.
For reference, here are the different signatures each device have:
B1NAUS01
B2NAUS01:
Beta Was this translation helpful? Give feedback.
All reactions