"Failed to ping" on 2 devices (out of 25)

[merlinpimpim]

What happened?

Hello,

Among my 25 devices, I often get "failed to ping" messages on only 2 of them. I don't know why. All 2 are devices connected to the power supply and are routers.

This one: https://www.zigbee2mqtt.io/devices/4058075729308.html

But the 1st problem is that it is not recognised as such by Z2M. Once paired, Z2M detects it as such: https://www.zigbee2mqtt.io/devices/AB3257001NJ.html#osram-ab3257001nj

Then the recurring warning message is as follows: Warning 2023-12-16 09:51:49Failed to ping 'ALLÉE - Prise connectée ext. - Osram/Ledvance' (attempt 1/2, Read 0x7cb03eaa0a0c81ba/3 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 51063 - 3 - 170 - 0 - 1 after 10000ms))

And this one: https://www.zigbee2mqtt.io/devices/ZBMINIL2.html#sonoff-zbminil2

Warning 2023-12-16 10:01:00Failed to ping 'SÀM - Plafonnier - Module SonOff' (attempt 1/2, Read 0x84ba20fffee241d4/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 5 - 1 - 175 - 0 - 1 after 10000ms))

What did you expect to happen?

• Recognition of the right device.

• Stop "failed to ping" warning messages.

How to reproduce it (minimal and precise)

Nothing special, just pair the devices and read the logs.

Zigbee2MQTT version

1.34.0 commit: unknown (!?)

Adapter firmware version

7.3.1.0 build 0

Adapter

Skyconnect / EZSP v12

Debug log

No response

[OUARZA]

Hello, I have exactly the same problem with my connected socket since the last update https://github.com/Koenkk/zigbee2mqtt/issues/20100#issuecomment-1866876752

@Koenkk

[coco673]

I have the same problem and even if i apply a backup nothing change. The issue seems to be only for device which can be set because all my aquara sensor are working well

Any idea where the bug come from @Koenkk ? Connection with mosquitto is working, m2z is running

[Koenkk]

This error means the device is not reachable, I guess setting the state is also not working?

Regarding the device detection, LEDVANCE uses a generic model ID for multiple plugs, therefore we cannot distinguish them (it's only a cosmetic thing)

[merlinpimpim]

This error means the device is not reachable, I guess setting the state is also not working?

Yes. And that's what I thought too.

But the problem is that it only happens on those 2 devices that are close to the coordinator. And these 2 devices are active devices (connected to the power supply). What's more, I've got 25 devices and other battery-powered peripherals, known to be less reliable (like Xiaomi Aqara), don't have this problem! How is this possible?

[merlinpimpim]

With Z2M 1.35.1 it continues. Only these 2 devices (active and routers) out of 25 (including several on battery and further away from the coordinator...) I don't understand why.

Note: I created an HA automation that restarts Z2M if the state of one of these 2 devices changes to Unavailable for more than 2 minutes: It works, as soon as one of these 2 devices stops responding, restarting Z2M makes them work again immediately.

Any ideas @Koenkk ?

Note2: It seems that when these problems start to appear in the logs (sometimes several hours after the last reboot of Z2M), the CPU used by Z2M suddenly increases from a few percent to > 25%.

Warning 2024-01-08 03:32:52Failed to ping 'ALLÉE - Portail - Module Nodon' (attempt 1/2, Read 0x9035eafffed8d440/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (sendZclFrameToEndpointInternal error)) Warning 2024-01-08 03:32:55Failed to ping 'ALLÉE - Portail - Module Nodon' (attempt 2/2, Read 0x9035eafffed8d440/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (sendZclFrameToEndpointInternal error)) Warning 2024-01-08 03:33:33Failed to ping 'SÀM - Plafonnier - Module SonOff' (attempt 1/2, Read 0x84ba20fffee241d4/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (sendZclFrameToEndpointInternal error)) Warning 2024-01-08 03:33:36Failed to ping 'SÀM - Plafonnier - Module SonOff' (attempt 2/2, Read 0x84ba20fffee241d4/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (sendZclFrameToEndpointInternal error))

[merlinpimpim]

Just in case: one of the 2 devices (Nodon SIN-4-1-20 module) is also the one mentioned in this bug: https://github.com/Koenkk/zigbee2mqtt/issues/20202 (Warning 2024-01-09 15:16:26 OTA: Firmware on '0x9035eafffed8d440' is newer than latest firmware online).

[Koenkk]

@merlinpimpim I think it's due to an issue with the adapter, updating it's firmware may help (the adapter you are using is not fully supported yet)

[merlinpimpim]

@merlinpimpim I think it's due to an issue with the adapter, updating it's firmware may help (the adapter you are using is not fully supported yet)

@Koenkk : You mean wait for the next firmware release? Because right now I'm on the last available fw for the Skyconnect adapter (I think).

[OUARZA]

Same problem here https://github.com/Koenkk/zigbee2mqtt/issues/20100

In addition, when I look at the latest communication from my equipment, I see that I have equipment that works without problems like my Philips lamps

[merlinpimpim]

@OUARZA Bonjour cher ami Français ! :)

In addition: does anyone know why the LQI column is always 255?

[merlinpimpim]

@merlinpimpim I think it's due to an issue with the adapter, updating it's firmware may help (the adapter you are using is not fully supported yet)

@Koenkk : I think it's best to avoid updating to the latest version of SLM in any case (SLM updates the firmware automatically if necessary)! 😅

[Koenkk]

@merlinpimpim the multiprotocol firmware is experimental from what I understood, It's recommended to use the non-multiprotocol version (just Zigbee)

[merlinpimpim]

You're right. (but it would be nice if one day it came out of experimental mode, because it's been around for a while now...)

[github-actions[bot]]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days