IKEA KAJPLATS Light bulbs E26 1100 lumens white spectrum (Matter over Thread)

IKEA KAJPLATS Light bulbs E26 1100 lumens white spectrum (Matter over Thread)

Approximate price: $9 for the bulb, + $1 gets a BILRESA button

Most recent firmware: 1.2.0

Link to community driver with health status (@kkossev+AI)

Link to product page at IKEA (E26 1100 lumen white spectrum)

Link to user manual

My take:

Defaulted to the Third Reality Matter Multi-Function Light in Hubitat, which worked with respect to on/off/level control. I did not see a way to adjust white temperature. Switched to Generic Matter CT light and that seemed to be a better match. I then moved to the community driver listed above, and it allows setting temperature. Even though this community driver is intended for bulbs that are RGBW, I'm probably going to stick with this one even for white spectrum. Use the Generic Matter CT if you don't want the health check, and don't like commands shown that don't actually work.

Works great for the price. One of the few IKEA products where it don't have issue with its size, as I do with the battery powered devices.

Note that there are other variants of KAJPLATS such as 1600 lumen white, 1100 lumen RGBW, 450 lumen white, and other bases.

I bought this bulb as a starter kit which simply means it includes a BILRESA button for $1 more.

2 Likes

Does the BILRESA button do anything Hubitat wise? Or is it just for control of the bulb directly?

Does anyone know how to change the power restore behavior?

The default (from what I see) is ON with a lowered brightness…

As far as I know, the “starter kit” is simply a SKU that gets both the bulb and a BILRESA button in the same box. The button looks identical to a standalone BILRESA and it doesn’t seem to me to be likely they would lock it down.

[Edit: I’ve had the chance to test it now. The BILRESA in the “starter kit” may be initially paired to the light bulb from the factory, but it joins Apple Home and shares to Hubitat as an independent BILRESA button device.]

1 Like

I hate when that happens. Yes, it does seem to default to on after a power outage, restoring the last color/temperature state. I don’t know why some bulbs (and a few smart plugs) insist on that behaviour.

The power restore behavior is configurable: ON, OFF, Previous State.

The problem is that Apple Home does not expose that setting, neither Hubitat drivers.

I don't have Dirigera, thus cannot run Ikea app. Would like to know if Ikea app has that option available

2 Likes

Good info. I checked both the built-in Generic Matter RGBW and the community IKEA KAJPLATS driver, and neither one exposes that preference as you said.

1 Like

@juker you can test the updated "IKEA KAJPLATS Matter RGBW Bulb w/ healthStatus" community driver :

  • Last edited: 2026/07/04 - added power-restore preferences + StartUpOnOff/StartUpCurrentLevel configure/parse support

Thanks for working on this!

It doesn’t seem to restore previous state of off for me. I did make sure I was using the User driver that I had updated, not the System or generic RGBW drivers. And I did initialize. But after power outage, the light came on even though it was off when the power outage began.

Similarly, when set to power on to Off, it still comes on.

My model is KAJPLATS E14 CWS globe 806lm, maybe there are differences? :thinking:

Observe the Debug logs when you change these new preferences, do you see confirmation coming from the bulb?

greatly appreciated !!!

will test it later 2night

1 Like

Study Lamp Power restore behavior 'previous' requires nullable StartUpOnOff write, which is not supported here; skipping

but then switching to off ..

1 Like

Can you try the 'toggle' option? Will it work for your bulb model?

Do you mean a Toggle command or toggle as an option for Power restore behavior? Either way, I don’t have it.

Scroll the drop-down menu to the bottom of the list.

The bulb should turn on and off alternately each time you cut and restore the power supply.


Update: Please update the driver manually to the new version Last edited: 2026/07/05 . Thanks to Fable 5 for catching and fixing the bugs:

  • 'Previous state' now actually works via the experimental TLV Null (0x14) write;
  • WriteAttributes acks are handled properly in parse(), ending the preference flip-flop;
  • The read-back race is closed with the delayed read and write-before-refresh ordering.

I’ve updated to 07/05 version and saved. Setting previous state preference then saving ..

Bulb was off and shows off in current state. After cutting power for 15 seconds and restoring, the bulb came on but it shows current state shows off until I Refresh ..

Thank you for the logs!. They look OK to me, what I see are the expected events.

Can you please try to summarize what is working and what not (for the new preferences only)?

From the perspective of the hub, everything appears to be working. I can set the preferences. If I have the preference set to restore state after a power outage, it appears to work as viewed from the device page. The bulb shows off before and after power fail.

However, the bulb comes on after the power fail even though it was off prior.

Sorry, I wasn't clear... I meant a summary of this type :

  • Power restore behavior : 'Do not configure' - works or not?
  • Power restore behavior : 'Previous state / device default' - works or not?
  • Power restore behavior : 'Off' - works or not?
  • Power restore behavior : 'On' - works or not?
  • Power restore behavior : 'Toggle' - works or not?
  • Power restore brightness: 'Do not configure' - works or not?
  • Power restore brightness: 'previous/default level' - works or not?
  • Power restore brightness: 'Current level' - works or not?
  • Power restore brightness: 'Custom level' - works or not?

Maybe the confusion comes from the unknown behavior of the 'Previous state / device default'. What I understood so far, is that this option actually does not restore the previous state. It configures the bulb to activate the 'device default' state, which is programmed by IKEA to be ON? So, the label of the 'Power restore behavior' must be changed to 'device default' to avoid confusion.

Also, seems that the driver needs to send automatically a refresh() command after the bulb power supply was turned off and on, because the on/off state is not updated automatically in this case?

that is my observations as well :

- device default is ON at low brightness

- the state is not updated

1 Like