^^^this.
Add this driver to App Code, then set the Number of buttons, push the Recreate Child Devices and Configure in the device. One or two (based on the number of buttons) child switches should be created, and sending on/off commands to those child switches should control the relays. At least this is how it's working for me. 
In Devices it should look like this:
you folks are Rock Stars! Thank you. 
Its working. I need to rewrite a few rules to pull these lights into the groups, and I can do away with some individual bulbs now. makes everything so much simpler!
I was wondering what the child parts did... makes perfect sense. I completely missed how to put it together.
To be clear Péter (@guyeeba) is the Rock Star. I'm just a groupie that's been to enough shows, so I know how to get back stage. 
Well, I am still in the wrong concert ! Your help has told me which stadium to be in ... (sorry I love cheesy puns and stuff)
Ok, changed a few rules, thinking it would be better to change from bulbs in a group to a switch, and there is up to a 4 second delay now between the "Standard lamp" (Ikea bulb) turning on and the first wall switch, then a further 23 seconds before the next switch turns on.
If I have the bulbs turning on and off themselves, then it negates the switch... but is faster.
Is this just a case of the speed the code runs, and the order it runs in (All in the same room as the hub) or can is there something else I am missing?
(see... different concert!)
Odd. Instant for me with the relay. Can you post your rule please?
Is there a delay when you press on/off on the device page of the switch?
I have only one switch of this kind, and it can be slow (even though it's mains powered, it's a sleepy end device, not a router - as far as I remember), but the worst delay I ever experienced was about 2 seconds, not 4, or 23...
sorry not 23 but 2-3 seconds. And yes, when I click the switch in the child device it does pause a couple of seconds. Also, one happens, and then the other.
All mine are instant using the ABC mapping. I have a double switch which is wired to an overhead light but the second switch turns on and off a hue bulb, by the hue light I also have a Philips button which when pressed toggles the wall switch and is Instant.
Hi Guys,
Apologise in advance if this has been answered above. But just wondering if someone can confirm if this zigbee switch will work with HE?
if someone has purchased it can confirm then that'd be great. Also does it have temperature sensor like aqara? Thanks
(ZIGBEE VERSION)
Huh. I wonder if there's a battery in them. Maybe they don't leech power from the load, and instead use a battery like a typical sleepy end device.
I don't know the reason of the delay, but the QBKG11LM and QBKG12LM switches (the ones that require both live and neutral wires) are routers, and are not suffering from this issue...
Strange, I have got the Philips remote working, for some reason the aqara double button that I have that is wireless is not showing the number of buttons it has on the ABC controller, so my first test failed.
The Phillips has all 4 buttons picked up so I assigned an Ikea bulb and both wall switches to button 4.
It takes up to 5 seconds to turn all 3 items on or off. If I take off the lamp, that responds fastest, the two switches are still slow, so I guess it must be the hardware.
If it shows as a button controller in RM, then perhaps @stephack didn't add support for it to ABC.
Sorry @SmartHomePrimer, dont have time to read the entire thread but are you referring to the fact that the aqara device does not show the number of buttons it supports?
If so, this isn't a function of the app but of the driver. The ABC app reads the numberOfButtons attribute of the device driver. If the device does not do this (it should be edited by the dev as that is a necessary part of a button device on HE) you can still manually set this under advanced options. To confirm if the driver supports this, simply open the device page and look for the numberOfButtons attribute on the right.
No problem. I'm just jumping into the thread myself and offering some advice. You hit it on the head. Now that I think about that driver for that wall switch, it exposes two child devices that appear as switches, not buttons!
Yeah... Buttons don't have to be child devices, as all the button capabilities (pushable, holdable, etc...) have their attributes that contain the ID of the button that triggered the event, and the push() command also has a button ID parameter - therefore multiple buttons can be handled by one device.
The On() and Off() commands of the Switch has no such parameter, and the switch attribute contains only the current state on that single switch, so it is incapable of handling multiple relays by itself.
Of course I could've put the XXXButton capability into the child devices, but there must be a reason that these Button capabilities support multiple buttons, so I decided to implement it the way it was intended to be used. I've already made a few composite device drivers with this method, and it worked for me every time. 
I think your problem is the Aqara changing state on the relay is not seen as a switch, I have also a Zwave wall switch which is also seen as a switch so I can create a rule that says if the relay changes then do x
So this is my rule for the zwave wall switch
But the Aqara isn't seen as a switch.
@stephack. well, I have gone back to your button controller and it sees both buttons without having to add the number in advanced options for the QBKG03LM
But not for the QBKG02LM.. thats the one without wires. When I manually add the 2 buttons, they do not work. Its minor as there are work rounds. The controller is a great bit of Kit though.
bottom line is I have the switches turning off with other buttons at last, even if they are very slow to respond. And I think its the hardware.
Download the Hubitat app
