Post edge migration IKEA bulbs are sluggish

Post edge migration I’m finding some of my routines using IKEA bulbs a bit sluggish.
These IKEA bulbs initially migrated as zigbee switch.
I’ve since moved them to Zigbee Light Multifunction Mc.
But to be honest there’s not a massive difference.
I turn the lights on or off either by pressing a button on an IKEA 5 button remote, or by using alexa via a scene.

Prior to migration the lights changed pretty close to instantly. Now the lights come on with a range of delays From maybe a fifth of a second to maybe 2 seconds at worst.
Also, the lights Come on “in turn” rather than all together.

It’s not a dealbreaker, it’s just not as good as it used to be. Any ideas if anything can be done to speed it up.
The button press doesn’t use a scene and the Alexa usage does, but there’s no obvious speed differences between the two.

Hi @Declankh

Since you are using this driver, you can use the groups function that I added to solve the problem of slow routines with multiple lights that we currently suffer with the new local execution.

in the link is how to use the function, basically it is:

  • In any bulb of the group that you want, you create a virtual device that will control the entire group manually, routines and scenes.
  • In Preferences, enter the same group number in all the bulbs that you want to be in that group, including the virtual control device.
  • On each device activate the capability Mirror group Function, including the control virtual device.

Now from the control device you can manage all the functions of the bulbs in the group at the same time from the driver, manually, routines or scenes sent only to that control device. Much easier and faster.

You can continue to control each bulb independently from the device itself.

You can disable the whole group dynamically by disabling the Mirror group function in the control virtual device.

You can also disable it on some device individually if you need.

You can create up to 10 groups and 10 different control devices with devices paired to the driver.


Thanks Mario, I’ll investigate this in the next few days.
The thing that surprises me is that the edge architecture was sold as being local and hence faster than DTH. So I was expecting everything to be as fast as it was or faster, not slower. Do we know why these are slower with Edge rather than DTH even on the stock Zigbee Switch edge driver?

They would have to explain it themselves, but my opinion is that the driver is not the culprit.

I think that the hub with the workload that it now has does not give more of itself.

It has to share its execution times with the drivers, local DTH, local routines, in/out communication with the API and serve the local wifi, zigbee, zwave networks.

Before, most of the time was dedicated to serving its local networks and the API, which did much of the heavy work that the hub now has to do, without being freed from anything hub did before.

I don’t know if the new smartthings station is designed for this new architecture and is more efficient than the legacy hubs.

With the execution by groups within the driver itself, you will see that these routines of multiple devices are greatly accelerated, since the execution process, which is sequential, eliminates several steps in the execution and the driver executes them without interruptions to receive and execute the commands. for each device.


That @Mariano_Colmenarejo
I tried the virtual device and the lighting group, and got it working after changing routines and scenes to control the virtual device.

It’s definitely faster, but one of the devices in the group of 4 IKEA bulbs lags behind the others. I know this bulb is newer than the others which are about 3 plus years old.

Maybe it has a different hardware and or firmware.

1 Like