I have two Aqara H1 WRS-R02 (WXKG15LM) Zigbee double rockers connected to Home Assistant which is running as HAOS on a Pi4 and a SSD, via a Sonoff Zigbee 3.0 USB Type P dongle and Zigbee2MQTT.
Everything is updated and running smoothly. When I set up an automation in HA to use one WRS-R02, the lights connected to the other WRS-R02, are also reacting, thinking they have been turned on by the WRS-R02’s automation they’re set up to work with.
I don’t understand why the one WRS-R02 can interfere (or whatever it actually does) with the other. They don’t have the same name, nor entity name. I primarily don’t use Z2M, I only use it for five devices which are not supported in deCONZ with ConBee II.
When I look up what’s triggered the lights, it’s indeed the automation with the WRS-R02 I didn’t click. What does this indicate regarding what’s interfering with what?
Automation test
alias: Right LED test
description: ""
triggers:
- domain: mqtt
device_id: c132c02c2635a44994b4b97e015dd6bf
type: action
subtype: single_right
trigger: device
conditions: []
actions:
- type: toggle
device_id: af4074162d15296bf3ed6fd88ba52b17
entity_id: e0164b2d9db9b7c4a8e4e1dfdbb4a23c
domain: light
mode: single
I must admit after many many read throughs of that post, I still don’t get it.
Using the entity_id name (not a bunch of numbers and letters), didn’t make any difference.
For the WRS-R02 buttons actions I don’t understand how to find the entity IDs, so I can’t give them proper names. Probably because mqtt is quite alien to me.
I tried removing device_id, but the automation needs device_id, if not, it won’t save. Got this error: Message malformed: Unable to determine action @ data[‘actions’][0] I searched, but only found out what I meant. Not how to relate it to my case. I usually can make out what’s wrong in YAML after much searching and testing, but not this.
With a proper entity_id name, the other automation still got triggered. Probably because that’s a blueprint and I don’t know how to rewrite that, so it can use proper names and not device_id. But I’m just guessing if that really is the reason.
Anyhow, I can’t use anything other than the UI’s automations with these rockers. Then it works fine. With device IDs and everything. I don’t get any advanced functions though. Double push and hold and such.
Sadly all this worked before Z2M 2.0.
Conclusion: I need to learn more about mqtt and blueprints.
I am not sure how you configured the WRS-R02 and if they even support it but one idea that comes to mind for me is device binding in Z2M. Might it be that the lights are somehow bound to the switch? You should be even able to test this by just tapping the rocker without any automation in place. Does the light toggle?
Hm ok. I just read through your last reply again. I don’t really understand the following part:
Anyhow, I can’t use anything other than the UI’s automations with these rockers. Then it works fine. With device IDs and everything. I don’t get any advanced functions though. Double push and hold and such.
You state that you can’t use anything other than the UI’s automations. But it is an automation that has issues, right? Do you have by any chance any other automations that incorporate any of the lights and rockers you try to use? If so, could you disable them and try again?
Also the Z2M about page of both rockers might be helpful.
Yup, that paragraph could use some clarification, hehe. Sorry.
What I meant is the only way for me to automate with those two rockers, is by making automatons in the HA UI. I can’t use the blueprint I used before, because I don’t know how to edit blueprints property nor do I understand mqtt very well.
And here I should post the blueprint maybe, since it could be the reason for this behaviour, maybe. That was not my initial thoughts for this strange behaviour.
I think I attacked this problem the wrong and the hard way. There’s so much I don’t know enough about in this scenario, so I’ll try and get these Aqara rockers connected to HA through deCONZ. There’s been an update to the integration since I tried the first time. (And Blakadder says it’s confirmed working with deCONZ.)
