None in display data/map

[MSL-DA]

I have two Philips HUE devices, LST002: https://www.zigbee2mqtt.io/devices/915005106701.html#philips-915005106701 and LTW001: https://www.zigbee2mqtt.io/devices/8718696548738.html#philips-8718696548738

On these two devices I get None (15) and an unrealistically high LQI

Can anyone explain "None" and why it only happens on these two HUE devices?

[Nerivec]

First glance, would be broken logic in the guilty devices firmware (table incorrectly filled somehow). Since it's two Philips, makes it more likely they would have the same code, hence same bug. Any chance you have another of same model with exactly the same firmware version? It should do the same if that's the case.

Also, did you check the response payloads, just to make sure there isn't some weird bug on our side? It's pretty much a 1:1 translation from the payload sent by devices to the display, but just to be sure...

[MSL-DA]

Thanks for the quick response :)

I do, and it’s the same error on these two devices LTW001.

Spisebord and Sofabord

I also have two LTG002 devices: https://www.zigbee2mqtt.io/devices/929001953301.html#philips-929001953301 with a different firmware that behave as expected.

Can I do anything about it, or is it a firmware bug? Does it affect my Zigbee network, or is it just cosmetic?

[Nerivec]

Apart from a firmware upgrade that could fix the bug... not much you can do.
You could try removing all offending devices (assuming you won't have a range problem then), let the network settle for a day, see how the map looks then. And re-introduce them one by one...

Network maps are unreliable in general when it comes to the actual shape of the network, too many devices have small quirks (wrong LQI, wrong link type, etc.) that skew the end result.

[MSL-DA]

It may be a bit too early to claim that the Philips HUE devices in question made my Zigbee network unstable. However, after replacing these devices, I no longer see any errors in my log. Previously, I experienced that other devices did not respond or timed out; I no longer experience that.

[MSL-DA]

I think it says ATmega2564RFR2

[MSL-DA]

@Koenkk As mentioned, they are quite old units. But I’m happy to disassemble the HUE 9290012001 if that can make a difference.

[Koenkk]

I see, so no CC2531, would you mind making a PR for the docs to document this? Go the device page and scroll down to make a PR.

[MSL-DA]

I'm a bit unsure of what this PR should contain?

[Koenkk]

Info that these devices can cause instabilities on the network.

[MSL-DA]

They are “old” devices (+8 years), so I don’t know how relevant it is, but they have definitely had a negative impact on my Zigbee network - I’m no longer in any doubt about that.

Previously, I would get 30-40 errors a day. I should mention that I use Adaptive Lighting in Home Assistant, which has probably contributed to the high number of errors I experienced. However, all the errors were on non-Hue router devices and their child devices.

I haven’t had a single error in the last 5 days, which I’ve never experienced before. And I haven’t had any devices fail to respond. So now I think I can conclude that they were negatively affecting my network. I’m not knowledgeable enough to say exactly what …