Only use this blueprint if the advanced one doesn’t work for you: zha-ikea-tradfri-shortcut-button
This automation blueprint is for the Ikea shortcut button. This only works if u use ZHA integration to connect the shortcut button. You can add any action to the button for a short press or a long press.
It actually does trigger the actions for me. The lights turn themselves on every hour. I just realized the blueprint I’m using is a different one than in this post. I’m using the one here: ZHA - IKEA Tradfri On/Off Switch
Wait maybe not. LOL. It looks like Ikea motion sensors send the same hourly checkin events as well, and those were triggering my lights, not the button automation.
The checkin events from the button do trigger my blueprint automation every hour, but I haven’t watched long enough to see if that actually turns my lights on.
I’m still new to all this, but from what I’ve read so far, these blueprints create automations that are triggered by events, and any event from the Ikea button will trigger the automation, including those ‘checkin’ events.
Once the automation is triggered, the event’s data is evaluated against conditions that determine what actions should happen. The ‘checkin’ command doesn’t match any conditions in the automation, so it just gets ignored and nothing should happen.
It would be great if we could filter out those specific events so the automation doesn’t even get triggered, but I haven’t had luck editing the blueprint.
Thank you for this explanation! Makes sense. I’d also like to find a way to get rid of these events, it’s harder to track actual usage of the buttons with these periodic events.
I’m still getting multiple triggers of my automations in one second with this blueprint. If I want to increase the delay of the debounce do I just change this part?
So I’ve tried the original blueprint and this one and I’m not getting any response. I’ve even checked zha_events in developer tools and I get nothing. I’ve removed and paired the button and it is seen in HA but it doesn’t show any kind of trigger. Any thoughts.
I had this issue too. I tried again today, removing the device from the zha list, then re-adding it. This time it works and I can trigger events. Unfortunately I am seeing the multiple events per press this automation aims to solve, but at least I can get short and long press.
Actually I made a small change to the blueprint to allow a third “hidden” action. The code looks for a long press after a short press already, but currently just triggers the long action. I modified it to have a unique action for short then long press.
That way, the checkin commands (which have cluster_id: 32) won’t trigger automations built from this blueprint. A similar fix (adjusting cluster_id to account for other possible commands) could be applied to blueprints for the other IKEA buttons like this and this.