IKEA Trådfri Remote (and motion sensor)

[jsve]

IKEA has launched some more products in their Trådfri line. I have gotten the lights to work, but not remotes. They also have motion sensors now, which I guess will not work either.

de_web_plugin.cpp has a comment about IKEA remote not being supported yet. Is this because of the web-plugin of the core of deCONZ? Is there some work being put in to make this compatible?

I have managed to get the remote to show up in the deCONZ GUI and it has that blue indicator-dot that blinks when I push buttons. So something seems to be working at least. The logs (using --dbg-aps=2) shows the proper cluster being activated when i push the respective button, but there is nothing indicating if it was (for instance) brightness up or down that was pushed.

[manup]

Hi, in a few days we will release a new beta update which adds basic support for the Trådfri Remote in the REST API and realtime event notification in a new WebSocket interface. The button events can be used in rules to control lights and groups. We've made some tests with the Remote (firmware from 2016) and so far we haven't managed to find a stable way to join it into the gateway network — by pressing the setup button 4 times, sometimes it works, sometimes not. Hopefully the firmware will improve with the wider release.

We haven't testet the motion sensor yet, due the lack of a device, but expect support in the next few releases.

[jsve]

Awesome! My experiences with the remote is similar. Somehow it just pairs after a lot of tries. Not sure, but it seems to help if i spam the buttons shortly after the pair (or at the same time). Might just be a coincidence though.

Guess thats fine if you know about the issue. I think it would be OK if it was available in the web-gui as an option, but with the disclaimer that it might take a few tries.

Is there any way for me to test the beta when it comes out?

[manup]

Sure, you can download beta versions from https://www.dresden-elektronik.de/rpi/deconz/
the source code will be updated here too. Right now only stable version is kept here but we will provide a new branch (beta?) with the next beta release wich is in sync with the binary version.

Be aware that the next beta will only advance the REST API, not the WebApp itself. So using the IKEA switch and others is possible but a bit hacky.

[manup]

The beta is released now, with basic support for IKEA Trådfri motion sensor and remote control

https://github.com/dresden-elektronik/deconz-rest-plugin/releases

[yene]

Is it technically possible to talk directly to a light, or is always a remote required?

[manup]

Yes every light can be controlled directly through /lights REST API.
The remotes are just a further way to control them.

[binomie]

Hi, I managed to join the remotes, but how do i join a light. After joining the remotes to raspbee they don't join the lights by long press any more. I have the Tradfri LED E27 1000 lm.

[manup]

The lights need to be brought into the network first. If they were paired to the remote before you need to reset them. In case of IKEA lights they can be resettet with 6x on/off powercycle the light.

Or you can reset lights under Menu > Settings and then Scan for Devices > Reset.

After that bring the lights into the network as usual with Open Network. Once they are in the network you can pair them with the remote or simply put them in the remotes group.

[binomie]

Many thanks, worked well. I always tried to pair with 10 seconds press like Ikea mentions in their description, now i understood to open Network and then reset the light (6x on off) or button (4x press on back button).

In sensor.cpp i saw only two ikea sensors.
I have the dimmer as well:

IKEA Dimmer
On Youtube

DeCONZ does show it on the map, but it does not get a name and is not shown in the webinterface.
Is it not yet supported?

[manup]

Yes the integration into API will take some time and testing, the dimmer is more complicated to handle than for example the remote.

However since it's already in the network you can pair lights, which are also in the network, to it with the physical pairing button of the dimmer.

[ebaauw]

I couldn't resist and got myself a Trådfri light and remote. Both connect to deCONZ without any issues. The buttons on the remote cause WebSocket events, very nice! As far as I can tell, the value of /sensors/<id>/state/buttonevent matches the WebSocket notifications. I like that it uses similar buttonevent values to the Hue dimmer switch.

I do see some inconsistencies on the use of buttonevent, though:

1. When pressing the On/Off button, a 1002 buttonevent is emitted. In Hue speak this would mean a release (after press) of the On button. A press would bebuttonevent 1000. When holding or releasing the On button, no additional events are emitted;
2. Similarly, when pressing the Dim Up or Dim Down button, a 2002 or 2003 buttonevent is sent. I'm not sure if this is linked to the press or to the release (after press), though. When holding the Dim Up or Dim Down button, a single 2001 or 3001 buttonevent is emitted. In this case, the Hue dimmer switch would emit 2000 or 3000 (on press) followed by series of 2001 or 3001 while holding the button. When releasing (after hold) the Dim Up or Dim Down button, a 2003 or 3003 buttonevent is sent, just like the Hue dimmer switch.
3. When releasing (after press) the Next (right) or Previous (left) button, a 5002 or 4002 buttonevent is emitted. Again, no equivalent 5000 or 4000. No event is emitted at all when pressing, holding, and releasing (after hold) these buttons. On the Hue dimmer switch, the 400x range is used for the Off button. The Hue dimmer switch has no equivalent for Next or Previous buttons.

While the current behaviour seems to match the Trådfri remote's functionality as a standalone dimmer, I would like to get the same series of buttonevents as for the Hue dimmer: x000 and x002 for press/release, and x000, x001, ..., x001, x003 for press, hold, ..., hold, release. I'm not sure if this is technical feasible, though: the remote doesn't seem to have an equivalent cluster to the Hue dimmer switch's FC00.

[ebaauw]

Somehow it just pairs after a lot of tries. Not sure, but it seems to help if i spam the buttons shortly after the pair (or at the same time).

@jsve I don't think this is a coincidence. I find reading attributes from the Trådfri remote as well as from the Hue dimmer switches in the deCONZ GUI usually fails. Based on a remark by @manup in another thread, on battery-powered devices being mostly asleep, I started hitting a button while reading the attributes... with increased success rate (but still not 100% by far).

Probably related to this: The config for the Trådfri remote doesn't show battery. Some of my dimmer switches don't show battery. I did a clean installs for all.

[Hypfer]

I have 6 Tradfri remotes. Adding the first one to the network did work well. However, all the other remotes just get hex values as their names and never show up as remotes.

Why is that?

Update:

It seems that the network wasn't completely open for adding new nodes. I have no idea why.

However pressing "Scan for devices" and then 5 seconds later "Open Network" followed by factory resetting the remote and mashing its buttons did work.

[ebaauw]

I put the Trådfri light in the Trådfri remote group and it reacts to On/Off, Dim Up, and Dim Down. It doesn't react to the Previous and Next buttons, thought. When paired directly, the light changes it's colour temperature on these buttons. I finally managed to create a binding of the Scenes cluster (from the remote to the light), but that doesn't seem to change anything.

[philipptrenz]

Short question.
I'm on v2.04.35, pairing a Trådfri lamp worked fine. But I'm struggling with adding a remote. Do I have to upgrade? To which version, or even HEAD?
Thanks!

[manup]

https://github.com/dresden-elektronik/deconz-rest-plugin/releases

The remote has early support in the latest beta release version 2.04.40, it creates a group to which you can add lights. Currently only on/off and dimming works.

[ebaauw]

One of my users has a 1000lm Trådfri bulb, which deCONZ (v2.04.35) reports as On/Off light, even though it's dimmable:

{
  "etag": "f8679f2533edfc067b383abbc7bf34bf",
  "hascolor": false,
  "manufacturer": "IKEA of Sweden",
  "modelid": "TRADFRI bulb E27 opal 1000lm",
  "name": "Decken-Lampe",
  "pointsymbol": {},
  "state": {
    "alert": "none",
    "bri": 0,
    "effect": "none",
    "on": false,
    "reachable": true
  },
  "swversion": "1.1.1.0-5.7.2.0",
  "type": "On/Off light",
  "uniqueid": "00:0b:57:ff:fe:xx:xx:xx-01",
  "manufacturername": "IKEA of Sweden"
}

I noticed the ZigBee device ID for a ZHA On/Off light is the same as that for a ZLL Dimmable light. I suspect our Swedish friends think they use the ZLL device ID, but that gets interpreted differently on the ZHA endpoint?

[ebaauw]

On google, I found the location of the Trådfri firmware: http://fw.ota.homesmart.ikea.net/feed/version_info.json. I downloaded the files for my bulb and remote and renamed them to end with .zigbee, but the deCONZ OTAU plugin doesn't seem to recognise them. Is it at all possible to use deCONZ to upgrade the firmware of non-dresden-elektronik devices?

[manup]

I noticed the ZigBee device ID for a ZHA On/Off light is the same as that for a ZLL Dimmable light. I suspect our Swedish friends think they use the ZLL device ID, but that gets interpreted differently on the ZHA endpoint?

This is a HA/ZLL glitch in the ZigBee spec, I think they clarified that in the ZigBee 3.0 spec.

The new commit f0f3e95 fixes the issue, IKEA bulbs now have proper type 'Dimmable light'.

Is it at all possible to use deCONZ to upgrade the firmware of non-dresden-elektronik devices?

Yes, the plugin just uses standard ZigBee OTA, It was already testet with OSRAM, Busch-Jaeger and JUNG/GIRA devices. However the OTA firmware files of these are not publicly available (yet).

The firmware files of IKEA are raw data, not packet into an standard OTA file format. So in order to use them the .zigbee format binary header must be put before the data payload as described in the spec. Right now it's not worth the efford, because the version referenced in the JSON file is only the 'old' shipped version (1.1.1.0-5.7.2.0). I guess you're looking for the new ZLL certified version ;-) to my knowledge it's not online yet.

Once it's online (and downloadable like the current version) I'll give it a go for an update test.

[ebaauw]

The remote has early support in the latest beta release version 2.04.40, it creates a group to which you can add lights. Currently only on/off and dimming works.

Still some issues in v2.04.46:

• config.battery is missing for the Trådfri remote;
• When you use the Trådfri remote with a group from the Web GUI, the light reacts as expected, but this is not reflected in the API light nor group state. Only when the light/group is polled, the API state gets updated. With the Hue dimmer switch, the API states are updated immediately;
• When I set ct for the Trådfri bulb to an unsupported value (e.g. "ct": 500), the API light state shows the requested value (500) instead of the actual value (454). Again, the state is only updated to the actual value on the next poll cycle. Not sure if this is specific for the Trådfri bulb or generic for deCONZ, but the Hue bridge immediately reflects the actual ct value for Philips Hue and OSRAM lights. However, for the xy value it doesn't. I still haven't setup ZigBee sniffing so I'm not sure if the command to set colour temperature returns the actual value or if the Hue bridge queries the light after sending the command.

[perler]

Ok, I am still a bit unclear. I can bind the Tradfri remote to the deConz gateway in a way that it appears in the app but not in the webui. How can I control devices now?

[manup]

Normally it should create a new group to which you can add lights in the webapp.

[perler]

it didn't.. but I added the switch in 2.0.35 (when support was not really there for it), is there a way to force/delete it first?

[manup]

Please try the following with a recent deCONZ version:

• in webapp settings open the network (I recommend 10 minutes, 1 might be too short)
• while the network is open remove the switch battery
• press large button a few times
• insert battery again
• press large button a few times more

It's a bit hacky but now a new sensor should be created in the API and the group should also be created.

[perler]

that didn't work unfortunately. I really would like to remove the device from deconz first. is there a db where I can simply delete it?

[manup]

Yes it's a SQLite database

.local/share/data/dresden-elektronik/deCONZ/zll.db

It can be edited with tools like sqliteman, deleting the file is also possible but this would discard lights and groups settings as well. The switch if present is listed under sensors.

While modifying the database deCONZ shall not run.

[perler]

I did a complete factory reset and this looks more and more like a bug to me.

the tradfri remote is visible in the GUI (it blinks blue (in the GUI)) when a battery is inserted but it is nowhere to be seen in the web gui and so no group is created and controlling devices with the remote is not possible.

[manup]

Can you please try out the new version 2.04.52, it should improve the discovery of the remote.

• open network in webapp settings (even if the remote is already on the network!)
• press large button on the remote
• after a few seconds there should be a new group in the webapp

http://www.dresden-elektronik.de/rpi/deconz/beta/deconz-2.04.52-qt5.deb

Further if this worked so far, please press the large button again for more than 5 seconds to finish setup for the arrow buttons (control color temperature).

[ebaauw]

Deleted the Trådfri remote resource through the API, deleted the node it from the deCONZ GUI, deleted the record (with status deleted) from the database, installed 2.04.52.

Opened the network through the Webapp, pressed the On/Off button. The Trådfri remote appears as a node in deCONZ GUI. Another press or two and sensor resource is created. Read the attributes of the Basic and Power Configuration clusters in the deCONZ GUI, just to be sure. A group was created, and linked to the remote (through the group's devicemembership attribute and through the sensor's config.group attribute). I got web socket notifications for the creation of the sensor and for the buttonevents (1002, 2002, 2001/2003, 3002, 3001/3002, 4002, 5002), as expected.

Added the Trådfri bulb to the group. The light now changes colour temperature on the Previous and Next buttons! When changing the colour temperature, I even get two web socket notifications (as expected): one for the sensor state.buttonevent and one for the light state.ct.

Still some issues, though:

• The Trådfri remote still doesn't show under Devices in the Webapp;
• The light (and group) state.on and state.bri aren't updated on the On/Off, DimUp, or DimDown buttons;
• The light state.ct reflects the value sent to the light, not the actual value of the light (e.g. it reports ct in the range of 153..500, where the Trådfri only supports ct of 250..454). When the light is polled, I receive a new event for the correct state.ct value.
• config.battery is still missing from the sensor resource.
• Probably more a caveat than an issue: The Previous / Next buttons react differently from when the remote is linked directly to the light: in that case, Ikea only support three values for ct and the value rotates (e.g. pressing Next on the max value switches over to the min value).

[ebaauw]

You could already use a CLIPPresence sensor for that.

[snillevilla]

@ebaauw How what where? Please explain in more detail! :)

[ebaauw]

Create a CLIPPresence sensor and set the duration you want on that sensor. Then create a (series of) rule(s) that sets the CLIPPresence sensor when the ZHAPresence sensor becomes true. Base your rules to update the lights or other devices on the CLIPPresence sensor. We also used this workaround to trigger a HomeKit camera from a switch, see ebaauw/homebridge-hue#179

[snillevilla]

@ebaauw Looks good as an interim measure, but the duration parameter was SO much more convenient. :)

[jonatanolofsson]

I have been trying today to make the remote work with V2_04_91, and the remote shows up alright in the network, but the only response from the buttons I get is from the big button, which yields an "ikea remote toggle button" in the log, but nothing else - nothing in the gui and nothing on the websocket. I just spent the night updating the firmware of the remote OTA, but it made no difference.

Any ideas on how to continue debugging? Or on what I'm doing wrong?

[jonatanolofsson]

Nevermind, after a few reparings in the webapp it started working.

[manup]

Normally the events are just forwarded based on the group commands the remote sends. The webapp doesn't show the button events currently, but at least the websocket messages should be visible.

@ebaauw tool dc_eventlog can also be used to get some more debug output for the events.

https://github.com/ebaauw/dc_eventlog

Also I recommend to update to 2.04.92, sadly 2.04.91 had some serious issues.

[aradmidias]

I also ran into trouble, trying to connect my IKEA TRADFRI Remotes, TRADFRI Motion Sensors and FLOALT Panels. The Web-IU reports software version 2.04.99 (which appears to be a beta?).
(Note: When I talk about the "Web-UI" I refer to the one, that is provided besides the REST-API, regarding Phoscon app, see notes below)

Anyway: After several days of trial and error I figured the following procedures to connect the devices:

For the Remote:

1. Open the Back of the Remote
2. Reset it (by pressing the pairing-button at least four time in a row)
   You can see if it succeeded, when the red light at the front flashes
3. Wait for the flashing to stop
4. Remove the battery
   Apparently the Remote can hang after being reset, causing successive connection attempts to fail
5. Wait 5 seconds
6. Open the Zigbee-Network (if it is not already open) to allow new devices to join
7. Re-Insert the batteries
8. Hold the Remote close to the RaspBee and press some buttons
   You can see the green LED on the RaspBee flashing and blinking
9. After some seconds the Remote appears in the "Control" section of the Web-UI
10. Assign a light to the Remote to test the on/off, increase brightness and decrease brightness buttons work in that group.

For the Motion Sensor:

1. The sequence is the same as with the Remote, just that it'll need some motion for the Motion Sensor to sense some motion (duh)
   I waved my hand in front of the Sensor.

For the Panels:

1. Reset the light (turn it on and off, six times in a row; when turning it on again, wait for a moment to see that it is reset)
2. Turn the light off
3. Open the Zigbee-Network (if it is not already open) to allow new devices to join
4. Turn the light on
5. It will be added automatically

Notes:

1. Regarding the Remote and the Motion Sensor: I did not test, whether the short distance is a necessity.
2. The Remote is not listed in the "Devices" section of the Web-UI, therefore it can not be configured (though both, the Remote and the Motion Sensor are included in the returned JSON)
3. The previous / next Buttons on the Remote do not work out-of-the-box, even if a Panel is in the Remote's group, though the events, that are triggered by pressing the buttons, are registered and visible in the JSON that is returned when opening the "Devices" section in the Web-UI.
4. I did not do these tests with the Phoscon App, though it visualizes the Remotes and Motion Sensors. It also provides a way to assign scenes to the next and previous Buttons, but right now, I could not get them to change the scene.

So from what I can tell, the Remote(s) and the Motion Sensor(s) can be paired and do work with 3 out of 5 buttons.

Since I wanted to control one light with multiple Remotes and Motion Sensors, which is possible, by adding the light to the respective groups, I achieved what I wanted to achieve. 😄

[ebaauw]

The Web-IU reports software version 2.04.99 (which appears to be a beta?).

Could be - haven't seen that version yet.

Regarding the Remote and the Motion Sensor: I did not test, whether the short distance is a necessity.

Probably not, but it seems prudent while pairing to have end devices connected directly to the gateways instead of through the ZigBee mesh network.

The previous / next Buttons on the Remote do not work out-of-the-box, even if a Panel is in the Remote's group, though the events, that are triggered by pressing the buttons, are registered and visible in the JSON that is returned when opening the "Devices" section in the Web-UI.

Yes, still don't know why. See my comments above and #96 (comment).

So from what I can tell, the Remote(s) and the Motion Sensor(s) can be paired and do work with 3 out of 5 buttons.

Actually all five buttons work when using gateway rules. If you hold the On/Off button for 10 seconds, deCONZ will create some default gateway rules to change the colour temperature of lights in the corresponding group (also non-IKEA lights). The remote sends the commands when pressing the Previous or Next buttons, but the IKEA lights simply doesn't seem to react to these when connected to the deCONZ gateway.

[xibriz]

I'm having a really hard time with my Trådfri Motion Sensor (TYPE: E1525).

Can't get it to report motion. Any way to get some logs/debug info?

I'm running deCONZ 2.04.99 / 12/15/2017 on Raspbian Stretch 4.9 / 2017-11-29 (Headless installation)

Sensor info:

{
  "config": {
    "alert": "none",
    "battery": 87,
    "duration": 60,
    "on": true,
    "reachable": true
  },
  "ep": 1,
  "etag": "b002180869295a690b6df4a7abc6fda4",
  "manufacturername": "IKEA of Sweden",
  "modelid": "TRADFRI motion sensor",
  "name": "TRÅDFRI Motion sensor",
  "state": {
    "lastupdated": "1970-01-01T00:00:00",
    "presence": false
  },
  "swversion": "1.2.214",
  "type": "ZHAPresence",
  "uniqueid": "00:0b:57:ff:fe:46:9f:68-01-1000"
}

[ebaauw]

Indeed, looks like state has never been updated. Also config.group is missing. When detecting motion, the sensor sends a On command to its associated group. deCONZ listens in on this command and sets state.presence when it occurs. deCONZ resets state.presence after config.duration seconds, without any further interaction with the motion sensor.

My best guess is that the sensor somehow dropped from the network. I'd try reading the attributes of its Basic cluster from the deCONZ GUI, but that's kinda hard in a headless installation. Best delete it from the REST API, reset it, and pair it again with deCONZ, while continuously waving in front of the sensor to keep it awake during the pairing.

[xibriz]

Thanks for the info @ebaauw .

I have paired it many times with no luck. Some thing that I noticed is that the config.battery is updated, but not the config.duration. Assuming config.duration reflects the physical setting on the motion sensor.

If I restart deCONZ the config.reachable is set to false. I then have to take out the battery from the sensor to get the status to true again.

[ebaauw]

Assuming config.duration reflects the physical setting on the motion sensor.

Yes, but it only gets updated through the command the sensor sends when it detects motion.

If I restart deCONZ the config.reachable is set to false. I then have to take out the battery from the sensor to get the status to true again.

So deCONZ does receive the device announcement when the sensor is powered on. No clue why the command isn't received. You could try and power off all your lights, and move the sensor close to the RaspBee, so it connects directly instead of through the mesh network.

[xibriz]

Now I can't get the motion sensor paired with deCONZ at all. Have tried far to many hours now. It gets paired with the IKEA gateway right away with now problems.

[mattiasflodin]

@xibriz I managed to pair my motion sensor by removing the battery, opening the gateway, then reinserting the battery.

[xibriz]

@mattiasflodin Witch version does your motion sensor report?

I tried opening the gateway and reinserting the battery. The sensor was included right away :) But still does not seem to detect motion :( I have the latest deCONZ installed.

Vendor: IKEA of Sweden
Product: TRÅDFRI Motion sensor
Version: 1.2.214
Battery: 87 %
Motion: none
Refreshed: Invalid Date

[dxxxm]

By chance I had to re-pair the motion sensor today. No trickeries required. Didn't remove battery.
Sequence as by the book: Phoscon, 'add new sensor', 'IKEA', quickly press 4-times the rear link button, wait a bit until phoscon app replies with a 'ready' and a green 'tick' symbol.
"config": { "alert": "none", "battery": 47, "duration": 600, "group": "25463", "on": true, "reachable": true }, "ep": 1, "etag": "cdfzzza7xxxxxc0f2529yyy0050dd", "manufacturername": "IKEA of Sweden", "modelid": "TRADFRI motion sensor", "name": "TRÅDFRI Motion sensor", "state": { "dark": false, "lastupdated": "2018-03-13T20:45:15", "presence": true }, "swversion": "1.2.214", "type": "ZHAPresence", "uniqueid": "00:0b:57:ff:ss:xx:yy:zz-01-1000" }

[FezVrasta]

Is it just me or the remotes go into some kind of standby mode after a while?

I notice that I have to press the button twice to make it trigger the event, but after that, everything works just fine.

Is this a known limitation?

[mattiasflodin]

@FezVrasta I used to have this issue before when I only had a couple of remotes in the network and no light bulbs. After adding all the light bulbs as well, it doesn't happen anymore. Perhaps it has to do with not finding neighbor devices in a close enough range, or perhaps a non battery-powered device is needed to keep the mesh active.

[FezVrasta]

Thanks for the reply @mattiasflodin, I have recently added a Osram Smart Power Plug for this very reason, the situation got better but still sometimes I have to press twice.

Anyway I'm going to move most of my lights to DeCONZ this weekend so I'll see if anything gets better!

[ebaauw]

or perhaps a non battery-powered device is needed to keep the mesh active.

The mesh is maintained by ZigBee routers (yellow nodes in the deCONZ GUI), which typically are mains powered. ZigBee end devices (most battery powered devices, grey nodes in the deCONZ GUI) connect to only one (typically the nearest) router in the mesh. When that connection is lost, the end device needs to find another router, which might lose the notification of the first press.

[FezVrasta]

@ebaauw the fact is that one of my remotes is exactly between my Osram plug and the DeCONZ, approx 3 meters from each side... I doubt there's lack of coverage in that particular position.

[ebaauw]

I’m lost in the technical details, but there’s more to it than radio signal coverage. IKEA, OSRAM, Philips all use a slightly different way to build up the mesh, sometimes causing devices from one vendor not to play well with routers from another vendor. Also, a router only supports a limited number of concurrently connected end devices. And if you power-cycle a router, the connected end devices are orphaned.

My network consist of 42 lights (routers), which are powered on always, and still my Hue motion sensors sometimes blink red, (presumably) indicating they’re re-connecting to the mesh network.

[FezVrasta]

I see, thanks for the info. On my DeCONZ I just have 3 remotes and the Osram plug so I thought that would be enough to have a stable network.

I hope that adding more bulbs things will get better.

[olemr]

Just updated to 2.05.32 (beta) and added an Ikea 5 button remote.
Added 2 ct bulbs to the group and on/off and dimming works well, even with deconz gateway offline.
I have read above about problems with the < > buttons controlling the color temperature and that is still not working out of the box.
What is the latest take on this?

I can see in the REST API that the buttons produces both press, hold & release events so rules are an option, but it would be nice if it worked with the gateway offline as well.
Before resetting the remote, I tested that ct change worked even when the Ikea Gateway was offline, so this direct control is possible, somehow.

[manup]

Should work with recent versions of deCONZ, closing the issue for now.