IKEA lights occasionally lost connection

[JBS5]

Occasionally a light (mostly a Tradfri GU10) gets unavailable in the Phoscon app and can not be switched off/on via Phoscon (or HASS). Using deCONZ 2.05.55 and firmware 262F0500 on the Conbee now, but got same problem with older versions of deCONZ and Conbee firmware.

(Not always this light)

1. Any clue why?
2. Is it possbile to restore the connection other then disconnect/connect power?

[peer69]

Same here with 2.05.58. One Tradfri GU10 seems to be unresponsible atm:

Happened to me with a hue light strip as well a few days before so I dont suppose any IKEA specific issue. Devices have to be powercycled and are back as normal after that. Still annoying in some cases, mostly for my FLOALT Panels which are directly powered and do not have a wall switch to powercycle them.

[ebaauw]

1. Any clue why?

The REST API plugin marks a light as unreachable, when it doesn't receive a response for a couple of times when polling the light for its state. The cause of not receiving a response is, in order of likelihood:
a. The light's power has been cut (e.g. by a 20th century wall switch);
b. The Zigbee network has a hiccup (e.g. due to radio interference or routing issues in the mesh). In this case, the light still reacts to group commands;
c. The light's firmware has crashed.

2. Is it possbile to restore the connection other then disconnect/connect power?

In a) and c): no. In b): yes.

The REST API plugin marks the light as reachable, when it receives a message from it. Powering up the light causes it to send a Device Announcement message. In b), typically, the light comes back spontaneously, when the next poll succeeds. You can also select the node in the deCONZ GUI and press 0.

[thomas70]

Same problem also in version 2.05.59.

[rich710se]

I also have this problem, even after upgrading to 2.05.59. Today was one of my three outdoor-lights "gone".
Its Tradfri bulbs all threee of them.

[JBS5]

@ebaauw Thanks for your explanation.

a. The light's power has been cut (e.g. by a 20th century wall switch);

No wall switches available for these lights, so I am not able to accidentally disconnect power.

b. The Zigbee network has a hiccup (e.g. due to radio interference or routing issues in the mesh). In this case, the light still reacts to group commands;

The lights doesn't react on group commands when connection is lost (the lights are assigned to a Hue Dimmer in the Phoscon app and doesn't respond on the Hue Dimmer when connection is lost).

c. The light's firmware has crashed.

Firmware 1.2.214 is installed on all my IKEA GU10 spots. Got 20+ of them and a random light goes offline, let's say one in the 2-3 weeks.

[ebaauw]

You might try the latest deCONZ version with 48d2c39.

[tubalainen]

I had the same experience two times the last months with two different E14 IKEA bulbs (IKEA fw 1.2.214) .
Power cycling worked both of the times for me.

[manup]

c. The light's firmware has crashed.

When the lights don't react to even group commands it seems to looks like a firmware crash.

2.05.59 has adapted the IKEA gateway parameters to configure light state reporting. Mainly in the hope to not trigger any bugs by using configuration which IKEA itself doesn't test. Side note the change will cause no timers are used for reporting on the device anymore.

The new configuration will be applied once a light is power-cycled.

We still send some maintenance requests like group membership and neighbor table queries to the lights, and might restrict these further if stability doesn't improve with 2.05.59.

Keep in mind there might also be the possibility that a bug is in the light firmware which is not related to any requests the gateway sends.

[tubalainen]

c. The light's firmware has crashed.

When the lights don't react to even group commands it seems to looks like a firmware crash.

2.05.59 has adapted the IKEA gateway parameters to configure light state reporting. Mainly in the hope to not trigger any bugs by using configuration which IKEA itself doesn't test. Side note the change will cause no timers are used for reporting on the device anymore.

The new configuration will be applied once a light is power-cycled.

We still send some maintenance requests like group membership and neighbor table queries to the lights, and might restrict these further if stability doesn't improve with 2.05.59.

Keep in mind there might also be the possibility that a bug is in the light firmware which is not related to any requests the gateway sends.

+1 on "not necessarily related to deconz but rather the Zigbee network or manufacturer FW" in correlation with Zigbee standard interpretation in manufacturers FW.

[peer69]

I just updated to 2.05.59 and after restarting deconz the same light is not reachable again. Pressing 0 in gui doesn't bring it back. Any other light works. In my case this might as well be an issue with the light itself.

[JBS5]

@peer69 @thomas70 Did you power-cycled the light as this is needed mentioned by @manup in #1261 (comment) ?

The new configuration will be applied once a light is power-cycled.

[peer69]

Good hint, haven't done that. For now I had to go back to .58 for another reason (high cpu load turning the gateway unrepsonsive), will try this later today with .59 again and powercycle all ikea lights.

[jurriaan]

I'm also having this issue, it happened twice for the same GU 10 light. Currently running 2.05.59, and I did power cycle the lights after the update.

[jurriaan]

Forgot to add that it sometimes seems like it's the same bulb that keeps failing. A while ago I did have issues with another bulb, and it would always be that one to stop reacting.

[thomas70]

After power cycle my IKEA bulbs came back. But my IKEA FLOALT panel WS is still offline