DIRIGERA Binding (IKEA Home smart)

Hi Bernd, thanks for your fast reply. The information view looks as following:

Thanks for the info. This is an important finding because recognition of plug type was really error prone!

I improved the detection and the updated binding version is available on Marketplace. Please perform the following steps

  1. remove the INSPELNING thing
  2. remove binding
  3. install binding from Marketplace again
  4. your plug shall now be detected as smart-plug

I just tried your new version, it works now completely flawless :slight_smile: ! Thanks a lot for the super fast fix!

1 Like

Hello @weymann,
I try to remove a few dirigera things. The thing status changes to “removing” and stays there. After an OH restart, the things are still on the list.
When I try force remove it I get a warning info about possible stability issues with the binding:

(…) is currently being removed but the binding has not confirmed it has finished the operation yet. Would you like to force its removal? Warning: this could cause stability issues with the binding!

Shall I force remove it?
I’m on OH 5.0.0.M2

I see this behavior during development e.g. if I created things with an older version of DIRIGERA binding, exchange then jar several times and then something seems to be wrong and the removal doesn’t works smooth and I’ve to force removal. Binding can handle this!

Any specific devices which shows this behavior? Maybe the same case as above - added with OH4 and removal in OH5?

Yes, all created in OH4 and removal in OH5. Dimmable-lights and contact sensor in my case.
Force-remove works fine.

Thank you for your great support.

1 Like

I’m currently testing the triggers on the Somrig remote control. Short presses and long presses are recognized without issue. But I have problems with the double press.

I can work with double presses in the IKEA app, but in openhab die channel doesnt switch.

Is this a personal issue with my configuration, or are others experiencing this as well?

Edit: Now it works for me. I don’t exactly know why, maybe removing it and adding it again.

A quick note about this functionality: by default, the channel is created as a switch, which doesn’t work here. If you set this to “string,” it works.

Did you check the trigger rule as described in readme?

A trigger channel isn’t connected to an item which is representing a state like light on or light off. It’s sending an event (trigger) and inside a rule you can perform corresponding actions!

Hello @weymann,

I got 2 of my bulbs (model: “TRADFRI bulb GU10 WW 345lm”) gone from Openhab after latest dirigera hub update.
I think they changed deviceType from dimmable-light to light for this model.
Current object data:
type: “light”
deviceType: “light”

Please support

Do you mean GONE as thing status?
If this is the case the bulbs are not longer paired with DIRIGERA hub.

  • Do you have IKEA Home smart running?
    If yes check if the devices are still present.
  • Are there new device discoveries from DIRIGERA in your thing Inbox?
  • If above points don’t apply I would simply try to execute the pairing sequence again and check if the things go back ONLINE

In raw json from DIRIGERA hub all bulbs, LED strips and panels are simply typelight. Binding decides which ThingType to use based on the canReceive capabilities. Below you can see the bulb canReceive isOn and lightLevel so Thing Type is Dimmabale Light.

  • Do you have IKEA Home smart running? - Yes, I can control the bulbs from the app

  • Are there new device discoveries from DIRIGERA in your thing Inbox? - No, I removed them but they are not discovered and not in the Inbox

Then let’s cross check the properties.

  1. What’s the Thing Type and Thing Properties of your handler? (Screenshot from my previous post)
  2. What’s the data of DIRIGERA hub?

I restarted both Opanhab and Dirigera hub and managed to add them back manually.
Solved, thank you for support.

Good to hear!
According to spec this should be color-light.

Any plans for implementing the new 2026 devices?

  • MYGGSPRAY – Bewegungsmelder für Innen- und Außenbereiche
  • MYGGBETT – Tür-/Fenstersensor
  • TIMMERFLOTTE – Temperatur- und Luftfeuchtigkeitssensor
  • ALPSTUGA – Luftqualitätssensor (CO2, PM2.5, Temperatur, Luftfeuchte, Uhranzeige)
  • KLIPPBOK – Wasserleckagesensor mit Alarm- und Benachrichtigungsfunktion
  • BILRESA Dual-Button Remote – mit zwei Tasten zum Schalten, Dimmen und für Szenenwechsel
  • BILRESA Scroll-Wheel Remote – mit einem Drehrad für die Licht- und Farbsteuerung
  • BILRESA Remote Kits – Sets in den Farben Grün, Rot und Beige (je drei Geräte pro Kit)

I tried to link two devices:

Klippbok works out, but Bilresa unfortunately not.

Sure, I’m on this topic.

The new devices have different deviceType definitions so they don’t work out of the box.

2 Likes

Marketplace version supporting new IKEA Matter devices is now updated to smapshot 4.3.10 which fits to latest OH4 and OH5 versions.

Some remarks

  • BILRESA scroll wheel is tricky to hanlde and it’s not exposing trigger events. Linking to other IKEA is possible but trigger channels are not working. Hopefully this will change in future with firmware updtaes
  • MYGGSPRAY light sensor is delivering suspicious values from 0 - 40.000. This doesn’t reflect real lux mesures. Zigbee VALLHORN sensors behaving the same. Again hopefully they can fix it with updates
  • KAJPLATS ligths delivered suspicious min / max light temperature boundaries, currently set to fixed values or you can configure them