DIRIGERA Binding (IKEA Home smart)

[rpwong (Russ)]

Are you also using the IKEA app? Some APIs (e.g. Tuya) will only maintain one connection at a time, so it’s advised to only use the native apps when necessary.

[phui (Patrick)]

Anyone know if this Dirigera gateway works with Xioami sensor?
I’m currently using the Xiaomi gateway with sensors and wanna get rid of the Xiaomi gateway but still using all the xiaomi sensor.
Thanks.

[Pedro_Liberal]

@phui assuming the xiaomi sensors are zigbee why not move to zigbee instead?
The price is probably the same and ikea uses mostly zigbee too

[PePe (Pawel)]

Same here, happened today.
Restarting Dirigera Gateway Thing helped.
So far can’t replicate

[weymann (Bernd Weymann)]

@Fechado

One thing I noticed is the different speed settings. In the IKEA-app I’m able to choose a speed from 1 to 5 in 0.5 steps. It is possible to choose a speed of 2.5. Other than this it’s the same.

Please check latest version on Marketplace. I have to change several channels due to preparing release version so you need to adapt some channels and items.

I added channel fan-speed for manual setting. I’m interested

• is it working as expected?
• how does it affect fan-mode channel?

[weymann (Bernd Weymann)]

@phui

Anyone know if this Dirigera gateway works with Xioami sensor?

No, I cannot confirm this because I don’t have any foreign devices connected. I already saw some different light bulbs which can be connected with DIRIGERA gateway but I cannot test it.

Question is what sensor do you have? Is it fitting to some categrory which is mentioned in readme sensor section?

[weymann (Bernd Weymann)]

@g_g_rich

I find the Binding looses sync with device states after a few days, then becomes unresponsive for sending commands. I can’t seem to consistently replicate it, restarting the Binding solves it.

@PePe

Same here, happened today.

I fully agree: stability and reliability are causing me the biggest headache right now! I see DIRIGERA gateway is going to some kind of Stealth Mode after a while. Calling gateway directlly via API it says everything is fine, websocket is up and pings are answered. In reality it doesn’t give updates anymore.

This is also fitting to IKEA Release Notes from Nov 5th:

The update from Nov 18th is also not promising. The sentence We’ve been working hard translates to me We’re not finished yet!

When you’re recognize such a situation please check channel statistics from gateway. There’s an entry lastPing which shouldn’t be older than 15 minutes. Otherwise something went wrong in binding.

[weymann (Bernd Weymann)]

@rpwong

Are you also using the IKEA app? Some APIs (e.g. Tuya) will only maintain one connection at a time, so it’s advised to only use the native apps when necessary.

I wouldn’t say that. I’m penetrating DIRIGERA gateway from

• binding
• IKEA App and
• curl commands

In principle if you send commands from any of these channels the response is fine and the corresponding channels (binding, App, API) are properly updated. The problem raises if you’re keep the connection for a long time and then something wents wrong.

[g_g_rich]

Interesting.
Just for info I’m also using the matter binding as well and don’t notice these state disconnects there. I have experienced the ikea app not synching but it has been very rare and doesn’t always coincide with the dirigera binding hanging.

Testing the new version in the marketplace, on/off commands for dimmer items working great now and in sync with the power channel.

[weymann (Bernd Weymann)]

@g_g_rich

Just for info I’m also using the matter binding as well and don’t notice these state disconnects there

That’s also interesting.

It’s still valid that you can trick gateway with one curl command.

1. Turn a bulb ON and swicth it to green - with IKEA App, DIRIGERA binding, matter binding, whatever you want!
2. Switch light OFF- via App, binding whatever you want
3. Place curl command which switches color to violett

curl -X PATCH https://$YOUR_IP:8443/v1/devices/$DEVICE -H 'Authorization: Bearer $TOKEN' -H 'Content-Type: application/json' -d '[{"attributes":{"colorHue":280,"colorSaturation":1}}]' --insecure

• $YOUR_IP - ip address of DIRIGERA gateway
• $DEVICE - bulb id you want to control, take it from configuration
• $TOKEN - shortly stop / start DIRIGERA bridge and search for obtained token

Switch power to ON via IKEA App, binding whatever you want.

• IKEA App and DIRIGERA binding is showing violett light bulb but it’s shining green. ==> Does matter binding showing it correctly? <==

[weymann (Bernd Weymann)]

@PeWi @g_g_rich
Any news regarding stability?

Have it now running for 6 days and 1 watchdog recovery happened.

2024-11-28 01:33:05.599 [WARN ] [era.internal.handler.DirigeraHandler] - DIRIGERA HANDLER Watchdog Ping Pong Panic - 2 pings not answered
2024-11-28 01:33:05.601 [DEBUG] [.dirigera.internal.network.Websocket] - DIRIGERA WS onDisconnect Status 1006 Reason Disconnected
2024-11-28 01:33:10.800 [TRACE] [era.internal.handler.DirigeraHandler] - DIRIGERA HANDLER WS restart necessary
2024-11-28 01:33:10.807 [TRACE] [.dirigera.internal.network.Websocket] - DIRIGERA Websocket start wss://192.168.1.26:8443/v1
2024-11-28 01:33:10.830 [DEBUG] [.dirigera.internal.network.Websocket] - DIRIGERA WS onConnect

[g_g_rich]

I had it stop updating after 4 days. Didnt see anything in the logs.
Restarting the binding fixed it.

[jwiseman (Mr. Wiseman (OH 4.3.5 Stable on Pi4))]

Thank you for this binding; just got it to discover the bridge, the repeater, the blind and the remote.

My main need for it is the battery levels to proactively swap them vs. them just being dead one day.

Best, Jay

[Fechado (Marco)]

I will test it next week. I’m quiet busy right now.

[g_g_rich]

Other than having to do a restart a week ago, it’s been solid ever since. All device status are in sync.

[weymann (Bernd Weymann)]

@g_g_rich @jwiseman @Fechado
Thanks for testing and keep on doing it.

I took binding into my productive environment because it should be quite stable now from channel definitions and implementation. Binding is now in review status for next OH releases and milestones.

[jwiseman (Mr. Wiseman (OH 4.3.5 Stable on Pi4))]

Just upgraded to OH 4.3 Stable and I’m using Market Place binding version last updated 12/25/24.

I’m getting these errors during startup now. I’m only linking to the battery sub-item on each device.

2024-12-29 15:43:32.001 [WARN ] [org.openhab.core.thing.internal.ThingManagerImpl  ] - Channel types or config descriptions for thing 'dirigera:blind:192-168-0-43:c701d569-c335-4b3f-ab93-c19d010d4f1a_1' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-12-29 15:43:32.012 [WARN ] [org.openhab.core.thing.internal.ThingManagerImpl  ] - Failed to normalize configuration for thing 'dirigera:blind:192-168-0-43:c701d569-c335-4b3f-ab93-c19d010d4f1a_1': {thing/channel=Type description dirigera:text-veto-advanced for dirigera:blind:192-168-0-43:c701d569-c335-4b3f-ab93-c19d010d4f1a_1:links not found, although we checked the presence before.}
2024-12-29 15:43:32.075 [WARN ] [org.openhab.core.thing.internal.ThingManagerImpl  ] - Channel types or config descriptions for thing 'dirigera:blind-controller:192-168-0-43:dcead722-16cb-4cc1-8976-aa87aa5353f5_1' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-12-29 15:43:32.086 [WARN ] [org.openhab.core.thing.internal.ThingManagerImpl  ] - Failed to normalize configuration for thing 'dirigera:blind-controller:192-168-0-43:dcead722-16cb-4cc1-8976-aa87aa5353f5_1': {thing/channel=Type description dirigera:text-veto-advanced for dirigera:blind-controller:192-168-0-43:dcead722-16cb-4cc1-8976-aa87aa5353f5_1:links not found, although we checked the presence before.}

Any advice?

Best, Jay

[weymann (Bernd Weymann)]

@jwiseman

Any advice?

This comes with the latest update where link channel turned into a dynamic channel.

@weymann

Version 0.5-beta

• Channels
  – Plugs & Ait Purifier disable-light channel moved to disable-status-light
  – all ota and link channels are now dynamic - if device supports feature channels will appear automatically

So even if you don’t connected an item to these channels during binding startup it reports the channel definition isn’t found. Sadly I cannot avoid this during development and fixing upcoming review comments.

But there’s light at the end of the tunnel - binding is declared now as beta status and there’s no intention for further structural changes other than fixing bugs.

tl;dr
If you shortly delete thing and create it again the message during startup shall disappear.

[MagnusN (Magnus Nordin)]

Thank you so much for this binding, it opens up for a lot of affordable quality devices!

In your table you have BADRING and VINDSTYRKA marked as not tested so I did that today. (Pi4 8GB, Openhabian, OH 4.3.1, DIRIGERA Binding 2024-12-25)

BADRING (6 channels) and VINDSTYRKA (8 channels) show same data as the IKEA app and updates directly on all tested channels (excluding the three OTA and custom-name).

The OTA channels show as expected 0 (interpreted as “Up to date”, “Ready to check” and 0%). I can’t trigger changes to check them updating but I saw “Check in progress” for a short while initially, so I believe they update as expected.

“custom-name” shows the name from the discovery, even after changing it in the IKEA app. The README.md is clear that it does not update from OpenHAB to Dirigera, but it does not seem to update from Dirigera to OpenHAB either, so maybe that should also be commented.

For VINDSTYRKA the binding has the added benefit of showing VOC as a number and not only an indicator (on the device) or no information (app).

Again, thank you for your great work!

[OpenPatrick (Patrick)]

Today I tested the VINDSTYRKA sensor. This worked very well for me.
Thank you for your work and the instructions! So it worked very easily even for me as a beginner.