[New device support]: Ikea Kajplats Bulb (not working)

[Cyanogenbot]

Link

https://www.ikea.com/nl/en/p/kajplats-led-bulb-e27-806-lumen-smart-white-spectrum-clear-globe-30611481/

Database entry

(the device never identifies or enters the DB but does show up as touchlink device)[12/14/2025, 8:49:57 PM] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/touchlink/identify', payload '{"data":{"channel":11,"ieee_address":"0x00f0fd45fff65122"},"status":"ok","transaction":"9f7d9-5"}'

Zigbee2MQTT version

2.7.1

External definition

- not possible yet

What does/doesn't work with the external definition?

• not possible yet

Notes

This device seems to be both thread and zigbee compatible (matter device), and is seen as potential touchlink device, but wont get into pairing. Not sure what is blocking the pairing process...

[github-actions[bot]]

🙏 Thank you for creating this issue and sharing your external converter!

In case all features work, please submit a pull request on this repository so the device can be supported out-of-the-box with the next release. For instructions on how to create a pull request see the docs.

If NOT all features work, please follow the How To Support new devices.

If you need help with the process, feel free to ask here and we'll be happy to assist.

[Koenkk]

This new IKEA Matter line is only marked as Zigbee compatible since it supports Touchlink which can only be used to reset the device, not the actually control it. So all new IKEA matter devices cannot be supported by z2m.

[Cyanogenbot]

Ahh thats annoying, thanks for informing me, guess that means I need a thread dongle...

[andrei-lazarov]

Apparently someone got the BILRESA remote connected to ZHA: Reddit?
I didn't find anyone who connected the lightbulbs though.

The pair button should work like this IIUC:

• press and hold to join Thread network
• press 4 times to pair with a light (Touchlink)
• press 8 times to join Zigbee network?

[r-vit]

I bought KAJPLATS E14 RGB light bulb today (406.085.72) and was not able to pair it with z2m. But then I started experimenting with it. Six on-off cycles (12 clicks) put the device in what seems to be a pairing mode when the light bulb blinked a few times with cold white light, but still wasn't able to pair. Then I repeated the reset cycle, but put the light bulb next to the coordinator where it successfully paired. The device is marked as unknown in Z2M but lets you fully control it. The generated configuration in dev. console looks like that:

export default {
    zigbeeModel: [''],
    model: '',
    vendor: '',
    description: 'Automatically generated definition',
    extend: [m.light({"colorTemp":{"range":[153,555]},"color":true})],
};

[andrei-lazarov]

This is awesome! Thank you @r-vit 🙂 @Koenkk please re-open

[andrei-lazarov]

@r-vit Can you interview + reconfigure again, then see if you get the model and vendor names in the external definition? Also please share the database.db entry for the bulb.

[r-vit]

Re-interviewing an reconfiguring the device doesn't change anything, unfortunately.

The database.db entry looks like that:

{
  "id": 103,
  "type": "Router",
  "ieeeAddr": "0x00f0fd45fffa3a84",
  "nwkAddr": 30546,
  "manufId": 4169,
  "manufName": "",
  "powerSource": "Mains (single phase)",
  "modelId": "",
  "epList": [
    1,
    242
  ],
  "endpoints": {
    "1": {
      "profId": 260,
      "epId": 1,
      "devId": 269,
      "inClusterList": [
        0,
        3,
        4,
        5,
        6,
        8,
        768,
        4096
      ],
      "outClusterList": [],
      "clusters": {
        "genBasic": {
          "attributes": {
            "modelId": "",
            "manufacturerName": "",
            "powerSource": 0,
            "zclVersion": 8,
            "appVersion": 0,
            "stackVersion": 0,
            "hwVersion": 1,
            "dateCode": "",
            "swBuildId": ""
          }
        },
        "lightingColorCtrl": {
          "attributes": {
            "colorCapabilities": 24,
            "colorTempPhysicalMin": 153,
            "colorTempPhysicalMax": 555,
            "currentHue": 181,
            "colorMode": 0
          }
        }
      },
      "binds": [],
      "configuredReportings": [],
      "meta": {}
    },
    "242": {
      "profId": 41440,
      "epId": 242,
      "devId": 97,
      "inClusterList": [],
      "outClusterList": [
        33
      ],
      "clusters": {},
      "binds": [],
      "configuredReportings": [],
      "meta": {}
    }
  },
  "appVersion": 0,
  "stackVersion": 0,
  "hwVersion": 1,
  "dateCode": "",
  "swBuildId": "",
  "zclVersion": 8,
  "interviewCompleted": true,
  "interviewState": "SUCCESSFUL",
  "meta": {
    "configured": 332242049
  },
  "lastSeen": 1765895603461
}

[thmedia2]

I also have 3 of those working in my network, but I think it's not 6 times but 12 times for the ZigBee mode, but not sure, and for me two of them paird without being close too the coordinator.

[r-vit]

I also have 3 of those working in my network, but I think it's not 6 times but 12 times for the ZigBee mode, but not sure, and for me two of them paird without being close too the coordinator.

yep, that is exactly what I posted - 6 off-on cycles, 12 clicks :)

great that it works without being next to the coordinator - maybe my network is simply overloaded and it wouldn't pair on the routers for some reason

[thmedia2]

no note quite what I meant, I mean 12 cycles, but really not sure. It was the last one that was playing up, so I tried several times with 6 cycles, but with that it would just blink and not pair, after a try with I think 12 cycles it paird.

[HG943]

This was inspiring so I ran a series of tests with the https://www.ikea.com/se/sv/p/kajplats-led-ljuskaella-e27-806-lumen-smart-vitt-spektrum-klar-globformad-30611481/ with ZHA on Skyconnect. Unfortunately, there were never any signs of pairing attempts. I tried the on-off procedures 4,5,...12 cycles and several times each and also tried with keeping the bulb close to the skyconnect. Even tried while trying to touchlink pair the remote. 100% out of luck. At 6 cycles, the bulb indicates reset by entering the flashing sequence, that doesn't happen at any other number of cycles.

So, is it ZHA, skyconnect or the bulb?

[thmedia2]

I would suspect the bulb, mine also did blink after 6 cycles but never paird, I know it sounds stupid but for my wildly turning it of and on got it to blink and pair, but as I said not sure about the amount of cycles

[marco-slr]

I could connect it with a 12 cycle via m2z, but could not control it. However, once I bind it to a Styrbar, I could control it.

[nordlings]

Does it matter which version you are on?

There seems to be different behaviours...

I am on z2m 2.6.2 and have not been able to pair the one device I have tried.

Blink after 6 on/off does occur but nothing more than that.

[Cyanogenbot]

@HG943 I think that bulb specifically doesn't support zigbee for other than touchlink resets. I ended up pairing it over matter with a thread dongle...

[HG943]

That may be, although it appears as if some have actually managed to pair it in zigbee mode.

I would really like to do that, so that the bulb can work both standalone directly paired with the remote as well as managed by HA. It makes the system more resilient and will work in the event HA is down for any reason. I would prefer not having to get new remotes for this purpose.

[PaddiWaddi]

I could connect it with a 12 cycle via m2z, but could not control it. However, once I bind it to a Styrbar, I could control it.

I just managed to get this to work repeatedly with two Kajplats e14 rgb (LED2409G6) by power cycling the lamp 12 times (on and off repeat 12 times / „24 clicks“).

After only 6 power cycles the lamp flashes 2 times in warm white (complete on off) but would not connect to z2m. After 12, it flashes 5 times in cold white (but would only dim) and then successfully pair without being close to the coordinator.

How would we go about adding device support? Is there any information I can share?

Unfortunately for me as well, zigbee model, model and vendor fields are empty.

Edit: I managed to connect an e27 rgb bulb as well. However failed on first attempt. So I first reset the bulb with 6 power cycles and then the 12 cycles worked. Note that they flash differently when they enter zigbee pairing mode.

[nordlings]

I could connect it with a 12 cycle via m2z, but could not control it. However, once I bind it to a Styrbar, I could control it.

I just managed to get this to work repeatedly with two Kajplats e14 rgb (LED2409G6) by power cycling the lamp 12 times (on and off repeat 12 times / „24 clicks“).

After only 6 power cycles the lamp flashes 2 times in warm white (complete on off) but would not connect to z2m. After 12, it flashes 5 times in cold white (but would only dim) and then successfully pair without being close to the coordinator.

How would we go about adding device support? Is there any information I can share?

Unfortunately for me as well, zigbee model, model and vendor fields are empty.

Edit: I managed to connect an e27 rgb bulb as well. However failed on first attempt. So I first reset the bulb with 6 power cycles and then the 12 cycles worked. Note that they flash differently when they enter zigbee pairing mode.

What is the model on the e27 that you managed to pair? I have a LED2401G5 which shows up in touchlink but refuse to pair.

[PaddiWaddi]

What is the model on the e27 that you managed to pair?

Mine is a LED2405G8 - that’s an e27 rgbw.

[thmedia2]

For me LED2408G10 that's e27 tw with 1521lm (all three that I have)

[GeorgeMn59]

Hey, also tried getting my bulb into zigbee mode. I have the LED2408G5. It resets after 11 clicks - just for clarification: when you say 6 or 12 on off cycles, do you end the cycle with the light being on or off? I suspect you leave it on at the 6th or 12th on-click, but since I can't get it to switch into zigbee mode, I'm just double checking.

Edit: in case it matters for your development, I did achieve connecting the bulb to my hue bridge via Touchlink in the hue essentials app.

[thmedia2]

Yes I did leave it in on state

[marco-slr]

On state, then it blinks. You should turn on (like for less than a second) and then off (around 1-2 seconds). The timing counts, at least for me.

Den tis 23 dec. 2025 13:03thmedia2 @.***> skrev:

thmedia2 left a comment (Koenkk/zigbee2mqtt#30211) https://github.com/Koenkk/zigbee2mqtt/issues/30211#issuecomment-3686404299

Yes I did leave it in on state

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/30211#issuecomment-3686404299, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALJZCN6ZC2AKJDCA5X76VT34DEVSNAVCNFSM6AAAAACPAHJOHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOBWGQYDIMRZHE . You are receiving this because you commented.Message ID: @.***>

[martinusGH]

I was preparing HA to support OTBR on SLZB so i purchased a Kajplats to run future tests. But after reading this topic, i just tried to pair the bulb on Zigbee using SLZB-06P7 and after 12 power cycles it paired immediatly first time without issues. No touchlink, not close to the coordinator. Although the device shows up as not supported i can fully control the on, off, dimlevel and white/warm color setting. So maybe i do not even need to move to using OTBR for the new Ikea range of products?

[wapolinar]

Just another successful pairing: I bought kajplats LED2405G8 (starter kit with bilresa remote). Could pair the LED successfully after 12 power cycles with my SLZB-06 and z2m. Does not pair after 6 power cycles (confirming the findings by @r-vit also database.db entry looks identical).

[marazmarci]

I also managed to pair an LED2408G10 (color temperature) bulb with 12 power cycles (meaning that I left it on when I turned it on for the 12th time).

I opened the dev console in Z2M and went through all the available attributes in the genBasic cluster. These are all the attributes which didn't throw an UNSUPPORTED_ATTRIBUTE error when reading:

zhc:tz: Read result of 'genBasic': 
{
  "appVersion": 0,
  "hwVersion": 1,
  "manufacturerName": "",
  "modelId": "",
  "dateCode": "",
  "deviceEnabled": 1,
  "powerSource": 0,
  "stackVersion": 0,
  "swBuildId": "1.0.7",
  "zclVersion": 8
}

There's not much information, as you see 🫤

[marazmarci]

Based on my current knowledge of Z2M, I don't think we can implement a proper converter for this bulb, because there's no way to identify the device.

But I have an idea for a workaround: 0. Have an external converter implemented

1. Pair the bulb
2. Stop Z2M
3. Modify state.json for the device to use the external converter
4. Start Z2M
5. Reconfigure the device, so reporting will be set up for the necessary attributes

Can this work?

[andrei-lazarov]

@marazmarci In that case I guess you could force the new bulb to use the converter of an older and supported IKEA bulb. I think it's database.db you have to edit. Example: "modelId":"TRADFRI bulb E27 WS globe 1055lm"

But I think the converter doesn't setup reporting anyway.. should be automatically set-up when you bind a remote to it.

Also don't know if you gain anything by using an external converter. Do you expect other options, than the light control and power-on-behavior, which I see are already working in the screenshot? I never used the 'execute if off' features.

[andrei-lazarov]

I have an idea, does the bulb report any imageType and manufacturerCode when you check for updates (enable debug logs and perform the manual check if possible) ? Maybe we could use those for identification.