Question

Ikea is a fair run from me, just just wondering if all the Tradfri GU10 (white selectable and not) and both remotes are ST compatible natively or not? And do WebCoRE support click, double click and hold like the ST buttons?  

Answer 1

@hamsun I don't have the GU10, but I can answer some of your other questions. I have the 5-button and 2-button Tradfri dimmers paired to ST, using the "Ikea Button" device handler (I believe that one is native now). Not sure on the WebCoRE side as I'm using the Advanced Button Controller smartapp for these remotes since processing is local vs cloud for WebCoRE, and ABC supports press vs hold detection.  

Answer 2

I have ikea bulbs and buttons that work flawlessly. I also ordered them online.  

Answer 3

My IKEA 5-button still runs in the cloud. WebCoRE only shows pushed and held statuses. Held is really just a “long press”. To really be useful they need buttons to report a held and released status so you could do something while a button is held.  

Answer 4

Cheers all. Bought the GU10 TRADFRI dimmable and 2 button dimmer. Both are recognised in ST which is great. Is anyone running automations/pistons to get held buttons to dim up/down?  

Comments

With the 5-button, I mapped two of the buttons to +/- 15% level for each press. With a 2-button, I'd map button press to +/- X% level and button hold to on/off. Trying to map button hold duration to increasing/decreasing dim levels is tough due to latency so you'll likely overshoot your desired level.  

---

Cheers Mike, I’ve seen some pistons on it but it seems a bit harder than just a hold doing a % dim as you want it to auto refresh so a button hold will keep dimming.  

---

There are two issues regarding held buttons. One is definitely latency. The second is knowing a button is being held down. The ST Button capability has a 'button' attribute with defined values for a large number of button events. Release and hold release are not among them, and nor is there any idle / standby / not pressed state. The de facto interpretation of this attribute is that it defines the last button event. There is no standard attribute that says whether the button is currently being pressed or not. There is nothing to stop device handlers using non-standard values, but equally apps have the right to not have a clue what to do with them. Custom attributes can also be used. However it still requires the button to report release or hold release events in the first place. My personal opinion is that it is horses for courses. Dimmer switches for continuous dimming, and buttons for dimming using preset levels.