The ID & Event from buttons 1 & 2 changes depending on which buttons I last used… If I pressed buttons 9 or 10, the ID & Event will be from that couple of buttons, if I pressed 3 or 4, it will come from those. The ContextID always changes btw. I wander how this is implemented with other Icasa components, not really sure tbh…
Well that still leaves me with 8 working buttons I guess
I’ve got the same remote. Buttons 11 and 12 do show up for me, event codes 9002 and 10002. So that’s 10 out of 12 on deconz version 2.05.72 / 12/12/2019, firmware 264A0700
Currently I’m not using the remote anymore, but I agree it’s a nice looking remote at a fair price (think I paid 27€), would be great if we could use it better…
An obligatory welcome to the community is in order
I’m using deconz to pair most of my remotes, but this one I cannot.
The only way around this, atm is to couple actions to the dconz events sent to HA, so under developer tools > events you need to listen to events to find out what event codes are sent to HA (you can use the ones above from me and renze) than create automations in HA itself… can’t really post screens as I don’t have it configured now. I much prefer doing the pairing in deconz as opposed to HA…
Don’t worry, just an inside joke Whenever someone posts for the first time, there’s a message that states: it’s the first time this user posts, make sure to welcome them… You’ll notice it soon…
Yeah, it’s a great looking remote. We all hope it gets supported in deconz directly… at least I do as I prefer the pairing in deconz anyway. I can recommend the Ikea remotes, very cheap and work out of the box with deconz.
Yeah just noticed it’s on the dresden wiki as well, but it states it’s possible that though the rest api is working, the device might not be in the phoscon app just yet…
You could play around with selecting ‘other’ in the vendor list… if you succeed let us know
I have the remote now too, and also looking for more info. Search is not helping me much, hoping you all can point me in the right direction.
Pairing worked but was not straight firward as the device pairs from phoscon without being detected by the pairing process itself. It is visible on the deCONZ VNC connection via HomeAssistant.
I can capture events for the buttons, trying to get some actions linked to them now…
And several searches later, I did find something that helps a bit.
Buttons AllOn/AllOff (1 and 2 from OP) cannot be controlled specifically. They send multiple commands, by design, for buttons 3 to 10 depending on previous press.
Buttons 3 to 10 send event 100? to 800?, where ? is 2 for a short press, 1 for long press and 3 for release after long press.
Buttons 11 and 12 send event 9002 and 10002; no long press actions for these available.
ID for my remote is iczb_rm11s_2
I created an automation trying to turn on/off a light with the remote, but the actions are not quite what I expected, yet.
Will play with it some more and report back if I find something that really works for me.