any updates on this, like youn all i bought these switchs for the whole reason of being able to decouple and som my smart bulbs where poered all the time. also if there was a power cut they can be put into relay mode by holding the left button. I payed out a lot of money to replace my moes switchs which done the job as i bypassed the switch so my bulbs were permantly on and controll was dont by the switchs and automations. What is the point of decoupled mode if the switchs do nothing. im hoping ive missed something obviouse.lol
No update really… I tried a single button model, same problem.
I messed the set-up of mosquito broker and zb2mqtt and the mqtt integration to make sure they all used my mqtt-user. No change.
I remain convinced it is an implementation problem, not a hardware problem, as I’ve seen on various YouTubers videos showing the power usage and actions with single and double presses.
Just run out of helpful set-up guides
I just managed to get this to work - but it involved flashing the firmware of my CC2531.
Previously I was on version 20190608 and I flashed it to the latest 20211115 and this all just started working!
I wasn’t aware that the device firmware was a possible reason this wasn’t working. Another side effect is the power monitoring and temperature monitoring features of the switch started working.
after flashing your dongle you need to remove the broken switches and add them again. Also, when flashing i’d recommend the video on youtube that shows you how to enable bootloader mode. Good luck, wasted a lot of time beforeni thought to delete and add again!
I’ve been happily using the Aqara WS-EUK03 single button with Neutral for around a year or more in decoupled mode, using the action of single press to toggle a shelly dimmer module controlling my ceiling lights.
I’ve setup WLED to the room, so bought the WS-EUK04 to replace my existing switch, so that I can use both left and right buttons in decoupled mode, one for my ceiling lights, one for WLED.
I figured it would be a straight swap, just wiring up as before and only using L1 wired to the dimmer as before. Although the new switch works in relay mode, to control my dimmer that it is wired to, when i try to use decoupled mode, neither side is reporting any button click actions to HA. I came across this thread, and some Github posts about it, but the only answers I could find relate to updating firmware/zstack. I’m using the Sonoff ZB Bridge, running Tasmota 13.1.0. This handled the single button click in decoupled mode fine on my WS-EUK03.
Can anyone suggest how I can get this working?
Ahhh! Darn just gone down the same rabbit hole. Brought a couple of the WS-EUK02 models. All works fine in HA but cant decouple them! get an error when I try. Sounds like I’d be wasting my time anyway! For me it’s no big problem if the relay is trigged as a duel switch one is physically connected to ceiling light the other is unconnected and just used a trigger to a smart plug for a bedside lamp. I have the M2 Hub as well to experiment with. So may have to use that and the Aqara cloud anyone know if decoupled mode works that way?
PS: This may have been picked by others but on the duel models say L1 = Left and L2= Right. You would assume that is as you look at when mounted on the wall! Nope! Its as you look from the rear when wiring up. So swap them round if you want if correct when looking from the front
Hulo, first post here, but thought it was worth chiming in…
We’ve just had our whole house completely refurbished and I decided, perhaps foolishly, to go all in on HA without ever having used it. I also very much wanted to do both smart bulbs and smart switches… it’s such an obviously useful combo that I can’t believe it’s not more common. As such I just went straight ahead and had the builder put Aqara H1 switches on prettymuch every switch (except some multi-point ones - I’ll figure them out myself later) and Innr spotlights in every room (and outdoor lights too).
This last week I finally got to getting started with HA and it’s been… challenging… to say the least. At several points I came to the conclusion that the H1/decoupled thing just didn’t work, which was gutting because I had based so much of how I wanted the house to work around it… but… I got there in the end!!! They’re working now - in all their decoupled glory. I still have many hours of setting up automations ahead of me to have them set up as I want, but the bare-bones functionality is there. As such I wanted to share what my set up is and a couple of the key hurdles in case it’s any use to anyone else.
Setup: I’m running HAOS via Proxmox on a Lenovo Thinkcentre Mini. I started off with ZHA but almost immediately realised I needed to pivot to ZigbeeMQTT to have any hope of getting decoupled work. My dongle is a Sonoff Dongle-P. I Initially got a Dongle-E before realising that was a bad move… it might be that decoupled can work with the E, but it didn’t for me. I also had a bear of a time getting ZMQTT set up due to some glitch where it wasn’t saving the config during setup, but that’s a whole different story and I got there in the end.
My Aqaras are a mix of WS-EUK03 and 04.
Right, all that done I got the first of my Aqara switches paired to ZMQTT, working as switches, but… no decoupled. I read many forums, jumped through many hoops, nearly gave up multiple times, but in the end I think the two critical moves I made were as follows:
- Updating the dongle firmware. Again this was a bear of a process because the bootloader button on the dongle refused to work so ended up going the Python route which was a bit outside of my comfort zone, but there was an excellent guide on youtube.
Once I had done the update suddenly my H1s were showing the decoupled option, and could be decoupled, with the switch no longer cutting the power… but still I was seemingly getting no report of switch presses, and no option to use switch presses as a trigger in automations.
- Again I went round in circles for hours and almost gave up. And then I came across a post on reddit (I wish I could credit the user but I’ve lost the post in my sea of tabs and now can’t seem to find it). The gist of it was: The H1s will not initially show their switch responses, you have to ‘train’ ZMQTT on what they are capable of. You literally single click on the switch a half dozen or so times in succession, then do the same with double clicks, and only then will single and double click (and supposedly long click but we’ll get to that) will show up in HA.
I thought “surely it cannot be that simple?!!”… but I went to my nearest switch and single clicked it a bunch of times (a couple of seconds between each), then the same with double click… I went back to HA and there they were 
According to the same user, the one caveat is that they will be forgotten after a reboot, so if you reboot you have to go round and do the same little training procedure for all your switches. A bit of a ball ache but a small price to pay to have them working. Also the reddit poster reported having single, double, and long press working - I have single and double working on all mine without issue, but can’t seem to get long press trained in. Still, it’s a niggle and far from the end of the world - the core function is there and that’s all I care about.
So there you go… maybe useful to someone. It’s such an amazing setup if you can get it working - you can be so creative with how the switches work, all while not having to worry about ever changing their batteries, and not having your smart bulbs ever power down & drop off the network. Perfection.
2 Likes
Interesting, thanks for posting that information. Glad you managed to get there in the end! Sounds like there is hope for decoupled mode in that case. There are several Aqara decoupled mode issues on Z2M Github, including the one I raised myself, but have’t had any response. I also came across some info after reading online about requiring coordinator firmware updates which update the zstack on the USB dongles, but I am running the Sonoff ZBBridge with Tasmota. I’ll certainly give the ‘training’ of the single/double clicks a try and see if it makes things work, and if so, i can add that to my support issue in case it helps.
Hey thanks for your post.
Can I ask, are you using the H1s with neutral or without neutral? I bought 2 H1s without neturals and settled on my kitchen lights just using the normal mode, but I was hoping to switch my landing light to the H1 without neutral to be used with my IKEA smart bulb but because the decoupled mode didn’t work, I gave up.
Thanks
Ah, they are with neutral… sorry, I totally meant to mention that. I actually specifically requested that the house was wired with neutral as I remembered seeing somewhere that the with-neutral H1s play better with decoupled mode (might be that it’s standard to have neutral now anyway, but I wanted to make sure).
Well I tried with my WS-EUK04 (double rocker with Neutral) using the several presses of single, double or hold, but couldn’t get anything to actually register. It is just empty strings of " " being sent for a single or double press, and a ‘NULL’ being sent for hold on my switch when in Decoupled mode.
I had no problems with my WS-EUK03 (single rocker with Neutral) in Decoupled mode, so it’s frustrating that the double rocker won’t play nicely in Decoupled mode!
Same situation for me. Only getting empty strings for action on H1 double rocker without neutral. Useless unfortunately
@mkolar This is the issue I raised, if you can add anything to it, although yours is without neutral:
Same Issue here,
I’m using Conbee III with zigbee2mqtt and on decoupled mode is not sending any actions.
I updated my Conbee FW to the latest (0x26500900) but no luck.
I even tried controlling the switch by removing z2mqtt and using ZHA but still the same problem.
Have you tried deleting the switch from z2m completely and then re-adding it since updating your Conbee firmware? I’ve just bought a Sonoff dongle-P to replace my Sonoff ZBBridge, which im hoping will allow the decoupled mode on this switch to work. I just need to bite the bullet and take down my zigbee network and rebuild it from scratch with the new dongle…
I tried even reinstalling everything(VM,HA etc). I don’t care about losing any devices on HA cause I just started using it and this switch was the reason. Thing is, I found out that also in coupled mode the device doesn’t send any signal even though I can control it from HA/z2m. I have set one automation to turn on/off one lamp irrelevant from the switch power and when I change the switch from HA it does work like supposed to( I even hear the click from the switch so it receives the command), But when I press the physical switch it does only change the power(you can hear the click) but doesn’t change the state on HA so the automation doesn’t work.
Hey I saw the reddit post as well, but only until now, I know how to “train” the switches, thanks to you.
But now I have two issues:
- Some switches were trained successfully (mostly double rocker switches), while others didn’t seem trainable (three rocker switches). All of my switches are D1 with neutral and all updated.
- When physically pressed, some of my switches update their status in mqtt immediately, and others don’t update until I click the refresh button.
Have you seen those issues or have any idea how to fix them?
I have 1 aqara switch with neutral and its working for 6 months. I bought 6 more from the same seller and they don’t work in decoupled mode. I think there was some training. But what… Holding bother buttons or what. I think at some point the light indicator went red. Hope there is a way to make them work
It worked. Can’t say how i trained it. Had to hold the 2 buttons until they went red. (I think that’s disconcting and trying to connect again). From Zigbee2MQTT can to refresh it, remove it. Did this 5-6 times. Maybe pressed one of the buttons some times. Really hard to remember it all. Will try with the rest 5 switches and try to find some pattern. Hope it will help you and future me!
I stumbled upon the same issue, but I made it work. So if anyone faces the same issues, I hope this helps:
Setup:
- Home Assistant 2024.5.5 on Raspi 4
- zigbee2mqtt with SLZB-06 (FW 0.9.9) as Coordinator
- Aqara H1 WS-EUK04
The Wall Switch is set to decoupled mode for both switches since it controls a Hue Lightbulb and has the State set to ON for the Left Button (thats where the wire runs).
When pressing the button, I do not receive any actions in the Z2M logs, however the Home Assistant Entity reports its status in the Logbook of the Settings → Devices → Detail Screen (the “Action” Entity is the one):
In my case, I pressed the right button, which causes the Action entity to report a change to “single_right” and immediately followed up by an empty one. And after 10 seconds the status is set to “None”. (This ties into FAQ | Zigbee2MQTT)
So now that it was confirmed, that the Switch indeed sends an update, I modified the blueprint from Z2M - Aqara H1(WRS-R02) - Wireless remote switch(Double Rocker) (Updated) - Single/Double + Single/Double/Hold so it works with the H1:
Modifications I made:
- remove the triple and hold actions, since the H1 does not support it
- and removed the attribute: action trigger selection, so it takes the state as it is sent
Here is my working blueprint:
blueprint:
name: Z2M - Aqara H1(WS-EUK02) - Wall switch (double rocker)
description: Scene & device control using Aqara two button wall switch
domain: automation
input:
button_sensor:
name: Aqara switch
description: Aqara switch to use
selector:
entity:
domain: sensor
integration: mqtt
multiple: false
single_left:
name: Left button - Single press
description: Action to run on a single press of the left button
default: []
selector:
action: {}
double_left:
name: Left button - Double press
description: Action to run on a double press of the left button
default: []
selector:
action: {}
single_right:
name: Right button - Single press
description: Action to run on a single press of the right button
default: []
selector:
action: {}
double_right:
name: Right button - Double press
description: Action to run on a double press of the right button
default: []
selector:
action: {}
single_both:
name: Both buttons - Single press
description: Action to run on a single press of both buttons
default: []
selector:
action: {}
double_both:
name: Both buttons - Double press
description: Action to run on a double press of both buttons
default: []
selector:
action: {}
hold_both:
name: Both buttons - Hold
description: Action to run when both buttons are held
default: []
selector:
action: {}
source_url: https://community.home-assistant.io/t/z2m-aqara-h1-wrs-r02-wireless-remote-switch-double-rocker-updated-single-double-single-double-hold/455665
mode: restart
max_exceeded: silent
trigger:
- platform: state
entity_id: !input "button_sensor"
action:
- variables:
command: "{{ trigger.to_state.state }}"
- choose:
- conditions:
- "{{ command == 'single_left' }}"
sequence: !input "single_left"
- conditions:
- "{{ command == 'double_left' }}"
sequence: !input "double_left"
- conditions:
- "{{ command == 'single_right' }}"
sequence: !input "single_right"
- conditions:
- "{{ command == 'double_right' }}"
sequence: !input "double_right"
- conditions:
- "{{ command == 'single_both' }}"
sequence: !input "single_both"
- conditions:
- "{{ command == 'double_both' }}"
sequence: !input "double_both"
- conditions:
- "{{ command == 'hold_both' }}"
sequence: !input "hold_both"
That allowed me to setup conditions so the left button triggers Daylight Scene, the right one Nightlight Scene, and when pressing the button with the active scene again it turns the light off again (I can post the details on that if you are interested).
Hope this helps!
3 Likes