If by “scenes” you mean toggling multiple lights at once, then use Z2M groups. It’ll work more reliably & faster than HA groups.
If you’re actually referring to Hue scenes (like effects & stuff), then I can’t comment since I don’t use Hue lights over here, but Z2M does has support for effects too.
What I’m getting at is - you probably won’t even need your Hue hub if you switch to Z2M.
I wrote earlier in this thread about the switch disconnecting on hold. I’m honestly getting quite annoyed that these switches do not work properly.
Whenever holding down any button it will start to send the hold request. If that hold is too long (well sometimes you wanna send the hold action for some time without having to count to 5 at the same time…) the whole switch leaves the zigbee network which is monumentally stupid. Anyone else got this to work or are the switches just completely idiotic?
Also the top buttons don’t seem to be able to send hold actions at all even in decoupled mode. So lazy to not finish the FW for an otherwise great device…
If you’re using ZHA, it might not be implemented. However the Z2M device page explicitly mentions that hold is implemented for both the top & bottom buttons
Have this switch got any zigbee updates?
So it seems there was an update for the switch that was not showing in Z2M. I updated the firmware by connecting to the Aqara hub I had lying around. Now it seem at least the switch doesn’t reset whenever I press and hold. So that’s a good start.
I have the 4 button version of the switch so this should be the correct documentation: Aqara WS-K08E control via MQTT | Zigbee2MQTT
Even though the multi press actions are mentioned for the upper buttons they do not happen. For the bottom buttons there are options to set multi click to enabled. But no such option exists for the top buttons… 
I think this is the bare minimum but also the leds are RGB or at least multi color but with no way to change the color and or set it manually. The HW has so many unused potentials which makes me a bit sad.
Yeah, you reminded me I had posted this a few months ago Aqara H2 EU wall switch - #19 by ShadowFist
To be fair, this has never been possible with any Aqara switch. Each colour represents a specific state or error.
Sad as you might be, I don’t think it’s reasonable to expect something from an integration when the manufacturer never advertised or supported it under the hood
Oh that’s good to know. I have also been waiting for it. It was annoying not being able to use the hold because it would reset the switch. I don’t have an aqara hub, but hopefully I can update using the app with Bluetooth
Since you have an aqara hub, is the multi click working there for the up buttons? What about hold? Like stated above, I think that is unfortunately by design, even if theoretically possible in decoupled mode
So if you do want to reset the switch for any reason, how do you do that now?
The actual way the instructions say. Click, click, hold 5 sec.
Previously it reset on just hold 5 sec.
I am not sure as I basically just connected the switch to update it. Maybe I can check this later if I find some time.
Maybe you are right you can simply update using bluetooth. Otherwise it should basically be almost free to get an E1 hub as it’s really cheap and often come in package deals. I think I have 2-3 of these in at the moment…
No, you are right. I just assumed it would be possible since one can use the app to switch the firmware between matter and zigbee. However, I checked the app, and there is no option to simply update the firmware.
It also does not seem to be possible to switch back to matter firmware without a thread border router (which I also don’t have). My theory was to switch to matter and switch back to zigbee, hoping it would install the latest.
I’ll just wait for the new firmware to be available in z2m, or maybe buy some used hub, if I happen to find one.
Someone needs to create a PR with an entry for the H2EU (lumi.switch.aeuXXX) in the OTA index before it’ll show up in Z2M.
If you managed to get the upgrade file from Aqara themselves, you could host it locally and apply the update without a hub. However, note that this is extremely risky and comes with a warning in the Z2M docs
Hi,
i managed to update firmware to v1.6 build 6 (from 1.3) by switching to thread firmware and back.
Unfortunately, the direct binding still seems not working.
Reviving this thread because it might reach some h2 owners 
Does anyone have a full example of how to make the h2 work in decoupled mode ? If I understand correctly, the lights should always be live no matter if you press the top button or not.
I would also truly appreciate if someone could share their blueprint and/or automation of how to then make the top button toggle the smart lights on the relay + some other unrelated ones ?
Would allow me to start experimenting but at this point I’m stuck using the switch like a dumb switch.
All inputs welcome !
Depends how you integrated the switch.
Matter: not possible (manufacturer limitation - see screenshot I posted further up in this thread)
ZHA: Should be possible but it might not be exposed in the dashboard. You might have to issue a cluster command to set it to decoupled mode.
Z2M: Exposed in Z2M dashboard & HA device page. Just click the button.
Thanks for your reply.
Yes I know how to decouple it in Z2M I meant more after that.
I have decoupled it and i see the events flying in when I use the top and bottom buttons.
What I’m confused by is how to then link those events to stuff happening to the lights.
Let’s take a (hopefully ) straightforward example.
I would like to replicate the behaviour of the top button when it is not decoupled: press on it, all lights of this room turn on, press again all lights turn off. How would one go about doing that ?
Hey @Jonybat (and anyone who would want to help out ) - Thank you very much for this.
I have tried to use the single rocker version to create an automation but I can’t find my switch in the list of entities.
It is there in my device list in MQTT though
Am I missing something obvious here ?
@ShadowFist
I have tried this automation:
But no luck and I don’t know how to debug it really… Any pointers would be greatly appreciated !
Those blueprints are meant to be used with Z2M 2.0+ and you have to enable experimental_event_entities in Z2M settings
