The tradfri remote also works with the development version of zigbee2mqtt. I set it up two days ago and it works like a charm. Pairing not just only to a bulb and so freely configurable in HA.
If it works like that with deCONZ, it should be possible with zigbee2mqtt also. The current procedure (while very nice for the tinkerer) does not seem suitable for the broad masses.
In zigbee2mqtt the tradfri remote control is defined as mqtt sensor as all information is sent as (JSON formatted) payload to the configured topic. Some exmaple payloads:
I paired my tradfri remote with deconz and I can see it on Phoscon software. It works when I set up an automation on Phoscon. I don’t see the device on HA though, in the list of deconz devices (I can see other devices there).
How can I set up and automation with this switch?
I cannot setup the automation suggested by @rtenklooster because I don’t have an entity_id.
Thx. I guess you are referring to this. I’ve read it. I’m still missing the device id though. My remote appears as " TRADFRI remote control" in Phoscon, but what device id should I expect to get in the event parameter of the deconz_event? Should I expect to see the remote somewhere in HA UI?
Ok, but how can I know the name of the device which will come in the deconz_event?
I enabled debugging for deconz as described here but I don’t see anything.
I thought so too… I don’t know what I’m doing wrong. I wrote this automation. I know that the action is ok, I’m using it elsewhere. I also renamed the device on Phoscon to be TRADFRI_remote_control.
The remote does work when I set up the automation on Phoscon directly. Also the connection between deconz and HA is working since I have other sensors and devices on deconz which are working fine.