IKEA TRADFRI remote control, color temperature not working

[ripperle]

Hello,

after updating to the latest coordinator firmware (stable, January 2019) I was able to connect my IKEA TRADFRI floalt panel und the Ikea 5 button remote control...

Over zigbee2mqtt I have full control to the IKEA light panel (on/off, brightness, color temperature)

With the remote control I lost the ability to change the color temperature... So I can only switch it on and off and change brightness...

Very weird behavior... 😁

Somebody any idea how that can be happen and how to solve it.?

[Koenkk]

Did you try this: http://www.zigbee2mqtt.io/information/binding.html#ikea-tradri-remote-control-e1524 ?

[ripperle]

No, not yet,

I don't want do use the remote in zigbee2mqtt so I thought that wouldn't be necessary

[tim-devel]

@Koenkk I am having a similar issue. I have followed the cc sniffer guidance and bound the switch to a light fitting with three bulbs. The on/off switch and brightness work flawlessly but the change colour buttons do not change colour temperature like they used to when using the tradfri hub.

[ripperle]

I noticed that the normal IKEA panel supports only 3 different color temperatures...

With zigbee2mqtt I can set more than that! Maybe the firmware of the panel gets in an unknown state or something?!

[Koenkk]

I've just checked and indeed setting colour temperature is not possible using this method. Perhaps some extra setup is done, need to do some more sniffing..

[tim-devel]

I have just paired a second remote to a full colour tradfri bulb. Set up went well and it integrates well with home assistant but the arrow buttons do not change colour with this bulb too

[didiht]

In my environment the IKEA remote control works very well with the IKEA bulbs, inclusive setting of the color temperature.

What I've done

• Complete new setup after two crashes due to tests of the reporting feature (but that's another story)
• Paired some IKEA bulbs
• Paired IKEA Remote Control
• Found out and added the group number of the Remote Control
• Added the bulbs to the group of the Remote Control (no bind!)
• every feature works well

zigbee2mqtt version 1.2.1 (commit #e5ca977)
Coordinator firmware version: '20190223'

Great Job!
Thanks to Koenkk and all contributors!

[ripperle]

@didiht
So you don't paired the remote directly with the IKEA lamps?
Are the remote working without the zigbee2mqtt coordinater?

[didiht]

@ripperle
No, I did not pair the remote directly with the IKEA bulbs.
Yes, the remote control works with the IKEA bulbs, even without the zigbee2mqtt coordinator.

I made following test:

• Delete the lamp from the group of the IKEA remote control -> IKEA remote does not work with the bulb anylonger
• Add lamp again to the group of the IKEA remote -> it works again, toggle, brightness, color temperature

With the 'bind' feature I had no success to set the color_temperature with the IKEA remote previously, but I didin't test this with the current version.

[bjobo]

@didiht
I tried exactly your setup: reset everything, pair control and lights to cc2530 controller, sniff the group, add lights to group. Switching on/off and changing brightness works like a charm. However: setting the color temperature via IKEA remote control ist not working.

Can I help doing some sniffing? When I press the arrow buttons on the IKEA remote control I receive the following message in Wireshark: ZCL Scenes: Unknown Command, Seq: xx There ist no "response" from the "receiving" lamp.

Frame 581: 55 bytes on wire (440 bits), 55 bytes captured (440 bits) on interface 0
IEEE 802.15.4 Data, Dst: 0xa041, Src: 0xf909
ZigBee Network Layer Data, Dst: Broadcast, Src: 0xf909
ZigBee Application Support Layer Data, Group: 0xb62e, Src Endpt: 1
    Frame Control Field: Data (0x0c)
    Group: 0xb62e
    Cluster: Scenes (0x0005)
    Profile: Home Automation (0x0104)
    Source Endpoint: 1
    Counter: 7
ZigBee Cluster Library Frame, Mfr: Unknown (0x117c)
    Frame Control Field: Cluster-specific (0x05)
    Manufacturer Code: Unknown (0x117c)
    Sequence Number: 88
    Command: Unknown (0x07)
    Payload

zigbee2mqtt version 1.2.1 (commit #e5ca977)
Coordinator firmware version for CC2530 (via USB): '20190223'

[didiht]

@bjobo
Maybe I have to mention that before pairing to z2m all IKEA devices were paired to the IKEA bridge to get the newest firmware.

I also sniffed an arrow-left-click and identified two frames:

• The first one with external source address of the remote (Frame 2)
• The second one with external source address of the bulb (Frame 4)

Frame 2: 115 bytes on wire (920 bits), 115 bytes captured (920 bits) on interface 0
Internet Protocol Version 4, Src: 192.168.1.3, Dst: 192.168.1.3
User Datagram Protocol, Src Port: 17754 (17754), Dst Port: 17754 (17754)
ZigBee Encapsulation Protocol, Channel: 11, Length: 55
IEEE 802.15.4 Data, Dst: 0x6e92, Src: 0x0409
ZigBee Network Layer Data, Dst: Broadcast, Src: 0x0409
Frame Control Field: 0x0248, Frame Type: Data, Discover Route: Enable, Security Data
ZigBee Application Support Layer Data, Group: 0x7a2a, Src Endpt: 1
    Frame Control Field: Data (0x0c)
    Group: 0x7a2a
    Cluster: Scenes (0x0005)
    Profile: Home Automation (0x0104)
    Source Endpoint: 1
    Counter: 25
ZigBee Cluster Library Frame, Mfr: Unknown (0x117c)
    Frame Control Field: Cluster-specific (0x05)
    Manufacturer Code: Unknown (0x117c)
    Sequence Number: 77
    Command: Unknown (0x07)
Data (4 bytes)

0000  01 01 0d 00                                       ....


Frame 4: 115 bytes on wire (920 bits), 115 bytes captured (920 bits) on interface 0
Internet Protocol Version 4, Src: 192.168.1.3, Dst: 192.168.1.3
User Datagram Protocol, Src Port: 17754 (17754), Dst Port: 17754 (17754)
ZigBee Encapsulation Protocol, Channel: 11, Length: 55
IEEE 802.15.4 Data, Dst: Broadcast, Src: 0x6e92
ZigBee Network Layer Data, Dst: Broadcast, Src: 0x0409
Frame Control Field: 0x0248, Frame Type: Data, Discover Route: Enable, Security Data
ZigBee Application Support Layer Data, Group: 0x7a2a, Src Endpt: 1
    Frame Control Field: Data (0x0c)
    Group: 0x7a2a
    Cluster: Scenes (0x0005)
    Profile: Home Automation (0x0104)
    Source Endpoint: 1
    Counter: 25
ZigBee Cluster Library Frame, Mfr: Unknown (0x117c)
    Frame Control Field: Cluster-specific (0x05)
    Manufacturer Code: Unknown (0x117c)
    Sequence Number: 77
    Command: Unknown (0x07)
Data (4 bytes)

0000  01 01 0d 00                                       ....

Maybe that helps.

If I can do any further investigation just tell me.

[didiht]

@ripperle @bjobo
Now I had the same issue: Removing, and pairing again (6 x powercycle) lost the ability of changing the color_temp with the (grouped) remote.

But following procedure leads in my environment to the expected functionality:

• remove the bulb from the zigbee2mqtt bridge
• stop zigbee2mqtt bridge
• pair the bulb to the IKEA bridge with the IKEA remote via Tradfri app
• remove the bulb from the bridge via Tradfri app
• power off the bulb
• start zigbee2mqtt bridge
• power on the bulb nearby the CC253x (no powercycle!)
• add the bulb to the group of the IKEA Remote
• SUCCESS color_temp is working again with the IKEA remote

It seems there is a (small?) difference of the initial states (reset with powercycle, reset by pairing and removing from IKEA bridge) that leads to the variance of functionality.
Could you test this please?

@Koenkk
Maybe we could give a hint in the documentation after others have tested this procedure and confirm that it works?

[Koenkk]

So it seems the tradfri hub does some special setup, could you sniff the zigbee traffic when pairing it to the hub? http://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

[ripperle]

@didiht
I have no IKEA gateway or IKEA app 😁

[didiht]

@Koenkk
Finally I could sniff the traffic during pairing. Involved components are IKEA hub, IKEA App, IKEA remote and IKEA bulb LED1545G12 (white spectrum).
But I don't have the Khow How to analyze.
What next? Shall I upload the WS file?

[bjobo]

@didiht
Hooray! Today I finaly got time to test your procedure. I can confirm that color changing now ist working.
I'd support your hypothesis that the key aspect is not to powercycle the bulb after removing it from the TRADFRI app.
However, this evening I was not able to filter the IKEA TRADFRI connect from the zigbee traffic due to too much 'noise' of other zigbee devices (and missing experience with wireshark and the zigbee protocol). If necessary I'v to try again at the weekend.

But following procedure leads in my environment to the expected functionality:

* remove the bulb from the zigbee2mqtt bridge

* stop zigbee2mqtt bridge

* pair the bulb to the IKEA bridge with the IKEA remote via Tradfri app

* remove the bulb from the bridge via Tradfri app

* power off the bulb

* start zigbee2mqtt bridge

* power on the bulb nearby the CC253x (no powercycle!)

* add the bulb to the group of the IKEA Remote

* **SUCCESS** color_temp is working again with the IKEA remote

It seems there is a (small?) difference of the initial states (reset with powercycle, reset by pairing and removing from IKEA bridge) that leads to the variance of functionality.

[Koenkk]

@didiht could you upload it here?

[didiht]

@bjobo
I am glad to be able to help 😄

@Koenkk here it is:
Ws.zip

[djusHa]

Hi,
same problem here.

Is there an Solution without Tradfri Bridge?

Devices are LED1624G9 and LED1546G12.

coordinator_firmware 20190223

Zigbee2MQTT version1.3.1

After reset the bulbs and tradfri remote
to factory and pairing with Zigbee2MQTT, no more ability to change colors / color temp with the remote.

After adding the bulbs to Tradfri remotes group, even no luck.

Same sniffer output like #1232 (comment)

On/Off and brightness on Tradfri remotes working good.

[Koenkk]

I've did some further investigation but didn't manage to decrypt the network.

I think the only hope to ever solve this issue is that IKEA shares the required Zigbee commands. I've asked them here: https://www.reddit.com/r/tradfri/comments/bpx9qf/what_magic_setup_does_the_e1524_ikea_tradfri/, fingers crossed..

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[vogler]

Does the coordinator know which bulbs the remote is paired to?
Maybe introduce a device option for the remote to emulate the original behavior by sending commands to change the color temperature on left/right button presses?

[BafHS]

i have the two problems.

1. Colortemp
   my steps:

• http://www.zigbee2mqtt.io/information/binding.html#ikea-tradri-remote-control-e1524
• pair the Device check
• toggle check
• brightness check
• color temp not working.
  in FHEM i see, press arrow_left_click or arrow_right_click but no change of color temp.

2. lamp state

• in FHEM the power state not changing, when i switch the lamp with the remote control???
  what can i do?

[Koenkk]

@vogler I think the whole idea of this is that it works when zigbee2mqtt is down, note that your solution can already be achieved via e.g. a home assistant automation.

@BafHS for 2 you can use the reporting feature: http://www.zigbee2mqtt.io/information/report.html

[martin-g-it]

Hmm, some new developments on the color temperature of IKEA bulbs using binding with E1524/E1810 remote..

After upgrading the firware to 2.3.080, the binding of the remote does not work for groups anymore, but should be done to devices directly; this is in line with documentation on E1524/E1810 - binding. The color changing option however now only works for the first device bound to the remote. Any subsequent bulbs/spots that you bind, won't change its color temperature anymore according to the predefined scenes.. Tried several things like adding/removing the 'magic' 65289 group, adding/removing the scenes, bind/unbind, etc. but nothing worked so far...

After some time I noticed only the first(!) device that was bound to the remote responds to the 'left/right click' color changing feature.

[ctankep23]

Ive had my RPi4+HA for about a month now. I have an Ikea bulb and a Styrbar E2001/E2002 4 button remote in my bedroom which worked fine up until yesterday I think. Now only the on/off and dimming functionality is working, the color temp/scenes is not working. Im using Zigbee2mqtt Edge (as that solved the problem according to another thread, though didnt work for me), and I have Zigbee2MqttAssistant as well.

Can I ask for help about that here?

[lionhe1966]

Apparently, in my case, this issue does not apply.
I am using a remote E1524/E1810 with 4 IKEA LED1537R6/LED1739R5 bulbs.
I updated with the frontend the remote firmware to 2.3.080 and the bulbs to 2.3.087.
I reset the remote and re-added to the zigbee2mqtt coordinator. I performed the binding to each of the 4 bulbs and I can switch between 3 white color temperatures with the left and right buttons.

[martin-g-it]

The color changing option however now only works for the first device bound to the remote. Any subsequent bulbs/spots that you bind, won't change its color temperature anymore according to the predefined scenes.. Tried several things like adding/removing the 'magic' 65289 group, adding/removing the scenes, bind/unbind, etc. but nothing worked so far...

Gave it another try since it does seem to work for others and it turns out that binding the 'Scenes' feature specifically (next to 'LevelCtrl' and 'OnOff') makes it work for multiple devices at the same time.. Makes sense in the end.. lol

[GregWoods]

Was there a reason this was closed? Nothing I do can get those left/right buttons to do anything.
My most resent attempt got binding to work, but only for on/off and brightness.

Lamp is https://www.zigbee2mqtt.io/devices/LED2035G10.html#ikea-led2035g10
Remote is Strybar: https://www.zigbee2mqtt.io/devices/E2001_E2002.html#ikea-e2001%252Fe2002

The button presses are being recognised in z2m
MQTT publish: topic 'zigbee2mqtt/REMOTE01', payload '{"action":"arrow_right_click","battery":null,"linkquality":21,"update":{"state":null},"update_available":null}'
But doesn't work when binding

[martin-g-it]

Did you bind the scenes function as well? (And set those scenes up)

[endreigesund]

When my remote was running fw 2.3.014 i got this working by:

1. Creating a group with the bulb and remote in it
2. Binding remote to the group

Everything was working including temperature - no scenes. Did this for 2 remotes on two different lights.

Then one remote was upgraded to 2.3.080. No i can't get temperature to work after rebinding directly to the light - no groups supported.

Any way to downgrade the fw again?

[endreigesund]

And i think issue should be opened until fixed :)

[martin-g-it]

@endreigesund Did you bind the function/cluster 'Scenes' as well between remote and bulb?
Basically you need to:

1. Add lights to the magic group 65289
2. Go to remote and bind the light including feature/cluster 'Scenes'
3. Add the scenes to the bulb/group via eg.:

• {"scene_add":{"ID":1,"name":"Cold temp","transition":1,"color_temp":250}}
• {"scene_add":{"ID":2,"name":"Neutral temp","transition":1,"color_temp":370}}
• {"scene_add":{"ID":3,"name":"Warm temp","transition":1,"color_temp":454}}

Then you should be able to switch through the scenes via the 'left/right click' on the remote.

[endreigesund]

@martin-g-it thanks - so this works for the latest fw on the remote?

if i have several remotes controlling different lights - can i make several 65289-groups or add all lights to the same group?

And binding the remote should be directly to the bulb and not the group - right?

[MattWestb]

IKEA have blocking firmware downgrading in all (known) controller firmware so its not possible doing it with OTA.

My and some users have doing it by flashing the last good with group support but its need SWD flashing and opening the remote for doing it.
We are using the original OTA files from IKEA only tripping the signing away so its only one "pure" flash file.
How to do it is in this discussion zigpy/zigpy#660.

[TheJulianJES]

@MattWestb Likely won't work but Xiaomi devices also try to prevent downgrading, but the OTA image version in the header file can be bumped up (the actual OTA image isn't modified).
Maybe that works for IKEA devices too?

[martin-g-it]

@martin-g-it thanks - so this works for the latest fw on the remote?

if i have several remotes controlling different lights - can i make several 65289-groups or add all lights to the same group?

And binding the remote should be directly to the bulb and not the group - right?

Yes
You can only create one unique 65289 group. Add all lights to the same 'magic' group.
Yes

[MattWestb]

@TheJulianJES I think it shall work only that we need fixing the broken signing of the OTA file but perhaps our @puddly is knowing if its possible patching the OTA header without braking the signing.

I think you is having some IKEA controller can you trying patching and see if its possible getting the device flashing it after have downloading it ?

[stefan-oskamp]

The main problem with the Tradfri remote is that, to get the scenes working, there are quite a few details that you need to get right.

I, too, have it working with the most recent firmware now. One key element (for my setup) was to not bind the remote to any group.

[Caine72]

@endreigesund Did you bind the function/cluster 'Scenes' as well between remote and bulb? Basically you need to:

1. Add lights to the magic group 65289
2. Go to remote and bind the light including feature/cluster 'Scenes'
3. Add the scenes to the bulb/group via eg.:

• {"scene_add":{"ID":1,"name":"Cold temp","transition":1,"color_temp":250}}
• {"scene_add":{"ID":2,"name":"Neutral temp","transition":1,"color_temp":370}}
• {"scene_add":{"ID":3,"name":"Warm temp","transition":1,"color_temp":454}}

Then you should be able to switch through the scenes via the 'left/right click' on the remote.

Hi!
I still cannot get this to work... I have an ikea Floalt and an IKEA E1524/E1810.
I cannot seem to figure out what I am doing wrong.

Currently i am running the latest firmware on both devices.

Before I found this guide.
I simply bound the controller directly to the light (with the scenes cluster) and I magically had three scenes already available.
They appear similar to the ones above.
But three scenes where not so popular with the family... they wanted more ..
So I went searching for a solution and found this thread.

So this is what I have done so far.
Step 1, Step 2.

Step 3. This is where I get stuck:
Do I add the scenes to the magic group or the light directly?
And does it work if I do it directly via z2m GUI, or do I have to do it via json?

What i have tried so far:
If I add scenes to the light, via z2m GUI, I only get the three for free scenes.
No matter how many more I add. They are ignored.

If I add scenes to the magic group, the scenes do not even activate and nothing happens.

Any Idea what I might be doing wrong?

[Caine72]

Figured it out.
Step 3. Add it to the magic group, and do it via json.

Seems like when if I manipulate the sliders via the the GUI the color change does not stick.
Only the brightness.
I.e. In the group via the GUI I add 5 scenes where I manipulate the lights color and brightness.
Only the brightness is changed when I scene transition via the controller buttons.

If I add the same scenes to the same group via JSON with the same values, it works.

Is this possibly a bug?

[Caine72]

Added second light to the magic group.
It did not work.
Removed all scenes, added them again.
Suddenly that now works as well.

My Styrbar however still does magical things. ( connected to one of the lights in the m.group)
It seems to jumpskip scenes.
I have five scenes, it goes 0, 2 ,4 ....

[endreigesund]

2. cenes
@Caine72 how do you bind the remot to the light including the "scenes" cluster. i don't see scenes as an option when binding from the remote.

[Caine72]

@endreigesund
Well... I actually did not manage to do that. But it still seem to work. Somehow.
Although it's traversing the scenes as 0,2,4 instead of 1,2,3,4 and 5.

[dayt47]

I also don't see a "Scenes" cluster at the binding tab (device: E1524). But I see a "groups" cluster. When I try to bind it with the groups option to my osram lamp it doesn't work. Already created a group with the id 65289 and added a lamp to it and created some scenes with different light temps. I could not figure it out how to link the remote control to this group.

[bjobo]

@martin-g-it thanks - so this works for the latest fw on the remote?
if i have several remotes controlling different lights - can i make several 65289-groups or add all lights to the same group?
And binding the remote should be directly to the bulb and not the group - right?

Yes You can only create one unique 65289 group. Add all lights to the same 'magic' group. Yes

@martin-g-it (or anyone else with current firmware)
Just to make sure: The binding to the magic 65289 still works also with the new firmware which can only be bound to devices not groups, correct?

My remote ist still on firmware 2.3.014 and I#m unsure if I should go for the latest firmware or stick to 2.3.014.

[martin-g-it]

I don't believe the firmware of the remote is key in this matter. I believe it is related to the Z2M version...
Anyhow, running all latest stable versions and binding still works between IKEA remotes and devices such as Tuya plugs and bulbs.

[bjobo]

My result: Scene switching works.
I currently use Zigbee2MQTT version 1.30.2-1. It works with the older firmware 2.3.014 as well as with the current firmware 24.4.5.

With the 24.4.5 firmware I additionally had to bind the Scenes cluster, with the 2.3.014 firmware just LevelCtrl and the OnOff cluser. I did not have to create and bin a "magic" group 65289.

[agsola]

Appart from switching scenes with the left / rigth button, is it possible to directly bind any button from any device to a scene? Or must the device be able to do that?

For example, bind the power button to a specific scene.

[bicalordman]

Hi , it happened to me after updating the E1821 button that I don't see the button in homekit. I had it paired before, for example, with a Shelly light or bulb, is there any way to solve this problem? I see it in homebridge, but it doesn't show up in homekit

[bchevreau]

This answer should be added to Styrbar remotes as well, as it just worked for me FINALLY !!!

1- Create a group called ikea_lights (or any name) with ID 65289
2- Add lights AND remote to the magic group 65289
3- Go to remote and bind the light including feature/cluster 'Scenes'
4- Add the scenes to the bulb/group via MQTT in your Home Assistant:
Easy mode: Go to MQTT > Configure > Publish a packet like the screenshot at the bottom of this post.
(You can also perform the same thru Developer tools > Services > Call service)

Topic: zigbee2mqtt/ikea_lights/set
Payload (add each line one by one before you publish for safety)

{"scene_add":{"ID":1,"name":"Cold temp","transition":1,"color_temp":250}}
{"scene_add":{"ID":2,"name":"Neutral temp","transition":1,"color_temp":370}}
{"scene_add":{"ID":3,"name":"Warm temp","transition":1,"color_temp":454}}

Then you should be able to switch through the scenes via the 'left/right click' on the remote. Enjoy !

[larsnygard]

4- Add the scenes to the bulb/group via MQTT in your Home Assistant:

Topic: zigbee2mqtt/ikea_lights/set Payload (add each line one by one before you publish for safety)

{"scene_add":{"ID":1,"name":"Cold temp","transition":1,"color_temp":250}} {"scene_add":{"ID":2,"name":"Neutral temp","transition":1,"color_temp":370}} {"scene_add":{"ID":3,"name":"Warm temp","transition":1,"color_temp":454}}

Wow, finally. On step 4 I used a little bit of time before I realized it was in the developer toos --> services --> MQTT-publish.

Wonder if its possible to set up more steps, or change the preset temperatures, but now it finally works, and I don't want to touch it again .... yet.

[bchevreau]

Wow, finally. On step 4 I used a little bit of time before I realized it was in the developer toos --> services --> MQTT-publish.

The easier way is thru Devices > MQTT > Configure button, so I edited my post to reflect that, but call service works just fine as well indeed.

I'm in the same boat as you, haven't risked tinkering with adding more scenes, but it should in theory work just the same... Altho this remote has a life of its own.

One thing is you can completely delete those scenes and republish, I did it multiple times to make sure it was working fine, so don't be scared to tinker a bit.