Search for new devices in the Phoscon app (it wont show up there as the app is not updated yet). Just look into your devices in the Deconz Integration in Home Assistant. Once your device is listed you can use it via the blueprint. Its a little confusing right now but the button works fine.
Thanks for the blueprint. What’s the difference between yours and the one it is based on?
I am facing the same problem. Please give some solution to us.
this blueprint is for the new ikea Tradfri shortcut button while the one it’s based on is the ikea Tradfri on/off button.
they both work very similar except that the shortcut button only has one button while the on/off button has two.
Ups. Sorry I didn’t notice the title. Cool. I’ll try it.
Can you add my homeassistant button?
i might do this when I get some time on my hands, iam pretty busy atm.
you can add the blueprint this way:
copy url of this thread -> go to blueprints in the ui -> add template -> paste the link
Thanks. Yes I already added it that way and it works perfectly. In the current deconz version the button is detected and reported to HA but it is not visible in phoscon interface.
Suddenly Deconz started sending double events for the shortcut button. Does anyone have the same problem?
i haven’t experienced them yet. a quick fix would be to set mode to “single” and put a 1s delay after the choose condition.
That works perfectly. Thanks.
please help me.
i have error message in blueprint:
unknown tag !<!input> at line 33, column 31:
device_id: !input ‘remote’
Hi! Thanks for your work! I add shortcut button from phoscon beta, but in home assistnt i see only device (without entiies). I add your bluepint but not works. Log say “trigger missing”
Hey @Sam04,
Potentially dumb question, can the shortcut buttons support double and triple clicks at this early stage?
Cheers
Linton
Today I’ve added a shortcut button in HA via deCONZ. Next step was using this blueprint.
Unfortunately I’m not able to have this work properly. I receive this error:
Error: UndefinedError: ‘dict object’ has no attribute ‘event’
The only thing I did, was creating blueprint, add the button, add the device, and that should be it.
Also a normal automation doesn’t work.
This is my config:
mode: restart
max_exceeded: silent
trigger:
- platform: event
event_type: deconz_event
event_data:
device_id: df5f2d33873742bbfb77edd8bdee8bc9
action:
- variables:
event: '{{ trigger.event.data.event }}'
- choose:
- conditions:
- '{{ event == 1002 }}'
sequence:
- type: toggle
device_id: d07ead29591e4ad941226cff43833e7b
entity_id: switch.kantoor_ventilator
domain: switch
- conditions:
- '{{ event == 1001 }}'
sequence: []
id: '1629292114900'
alias: deCONZ - Tradfri Shortcut Button
description: ''
What am I doing wrong here @Sam04 ?
Thanks for your help
@Sam04 I’m on the latest version of Home Assistant (hassio/supervised), using the latest version of the deCONZ addon, and a Conbee II updated with the latest firmware - l’ve added/synced my (one and only) Ikea Tradfri Shortcut button in Phoscon (successfully from what I can tell). Home Assistant lists it as well, I can see the battery level (100%) but it does not work in automations, not by event nor via blueprint - what can I do/check to try and resolve this?
Hmm, dunno why but after debugging events in Home Assistant (dev tools, events, listen to ”deconz_event”) and not seeing any events for this particular button/switch I removed and te-synced it a couple of times… finally it works as intended. But many times it just registered in Phoscon, showed up in deconz/visible by vnc, but no events… not working when added as a switch to a group in Phoscon either…
Anyways, perhaps helps someone else to know
Hi @Sam04
Is it possible to set a delay fort short press.
From time to time it fires dubbel events, switch on and the switch off in a second.
Could se that someone did for the blueprint in zha.
Maybe 300ms delay.
/Peter
@alundstroem
I’ve faced the same situation where adding the Shortcut button was successful, available in Phoscon and HA, but no triggered events would be detected through the Dev tools. By leaving it still for two hours in this state, it solved by itself and was then able to see triggered events! No need to re-sync it several times, being patient seems to be the key.
I was plenty patient (; it didnt heal on its own ));
But, its been working like a champ ever since I got it up and running