Hi, I have the IKEA TRÅDFRI Control Outlet plug with the accompanying remote.
I had no problem adding the plug itself in deconz but for the life of me I cannot add the remote. I’ve seen it briefly as “IKEA TRÅDFRI On/Off Switch” but it has never been successfully added. I have IKEA TRÅDFRI Motion sensors and the round IKEA TRÅDFRI Dimmer remote connected successfully.
My plan is to use the On/Off switch as a generic Zigbee switch and in fact not controlling the Outlet plug at all. Therefore I have not connected the remote to the outlet plug.
Can someone give me a step-by-step description on how to add the remote in deconz? I’m running hass.io on an RPi2 with the deconz addon and I have the Raspbee controller.
I integrated into Phoscon (Deconz) and I was able to make on/off in a Phoscon grup, but in HA only appears entity of battery: “sensor.living_on_off_switch_battery_level” .
What can i do to to see real entity and use in HA automations?
You have to listen to events. Turn on debug, click on button and you will see the event in the log to use in automation. Check the attributes for sensor.living_on_off_switch_battery_level and there you will find the event id to use. The documentation for deconz component has the specifics.
Did you all use the Switch category and then “other” to make it work? I have tried “Other” and “Ikea” (and chose a on/off remote though) and also as a light - no luck. I tried to reset it, but didn’t seem to make any difference.
I am using Hassio with the marthoc addon version 2.05.63.
Yes this is currently the only way to add it. Please consider updating deCONZ to the latest version 2.05.64 and the respective latest firmware version.
While switch search is running you need to press the small button next to the battery quickly 4 times, so that the LED flashes.
Thanks for the fast reply - but I could not really find anything useful in the component documentation.
The way this button works is that the single 1001 event should trigger something that will gradually increase the (e.g.) light until a 1003 event (or possibly a timeout) is reached.
I was interested in how that should be handled in Appdaemon (or an automation) - I guess just looping with a 1 second sleep timer until a 1003 is received would be a bad thing.