Error during network map loading

[MikeBlueG]

Describe the bug

This beug appeared when I try to create a map with zigbeemap (https://codeberg.org/dan-danache/ha-zigbee-map)

And seems to be linked to the fact that my zibee coordinator soonoff dongle max do not accept a query to check is LQI.

-->[ FAIL ] Probing 0x4c5bb3fffe83b0f5 # error: Delivery failed for '2503'. — stacktrace: Error: Delivery failed for '2503'. at EmberOneWaitress.deliveryFailedFor (/app/node_modules/.pnpm/zigbee-herdsman@9.0.2/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:100:31) at EmberAdapter.onMessageSent (/app/node_modules/.pnpm/zigbee-herdsman@9.0.2/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:459:42) at Ezsp.emit (node:events:519:28) at Ezsp.ezspMessageSentHandler (/app/node_modules/.pnpm/zigbee-herdsman@9.0.2/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:5082:14) at Ezsp.callbackDispatch (/app/node_modules/.pnpm/zigbee-herdsman@9.0.2/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:734:26) at Ezsp.onAshFrame (/app/node_modules/.pnpm/zigbee-herdsman@9.0.2/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:387:22) at UartAsh.emit (node:events:519:28) at Immediate. (/app/node_modules/.pnpm/zigbee-herdsman@9.0.2/node_modules/zigbee-herdsman/src/adapter/ember/uart/ash.ts:1179:45) at processImmediate (node:internal/timers:485:21)

To Reproduce

call the map of zigbeemap

Expected behavior

a map

Affected browsers

Microsoft Edge

Stacktrace

Current url: http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/#/logs/0
Previous url: http://192.168.0.48:8123/45df7312_zigbee2mqtt


Error type: Error
Error message: Minified React error #31; visit https://react.dev/errors/31?args[]=object%20with%20keys%20%7Bmessage%2C%20stack%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings.



Error: Minified React error #31; visit https://react.dev/errors/31?args[]=object%20with%20keys%20%7Bmessage%2C%20stack%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at kc (http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:37816)
    at ge (http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:39765)
    at Ge (http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:41282)
    at Vt (http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:43510)
    at http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:44005
    at Ir (http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:67964)
    at q0 (http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:83508)
    at u4 (http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:117661)
    at uU (http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:116701)
    at Ov (http://192.168.0.48:8123/api/hassio_ingress/4h8gn77Vhai5utOMBdagjxSuTZs39JfJZ471I3RG6l0/assets/index-D6vDWXD3.js:15:116531)

[Nerivec]

-->[ FAIL ] Probing 0x4c5bb3fffe83b0f5 # error: Delivery failed for '2503'. — stacktrace:

This is not a Z2M error, it has been modified/wrapped by something (that custom component?).
If something is sending unknown messages to the frontend's websocket, that can definitely cause errors in Z2M frontend, as only stuff coming from Zigbee2MQTT is expected.

[MikeBlueG]

Yes you are right it is not a direct Z2M error but a message that indicate my sonoff dongle max do not accept a query to check is LQI.

If you have no particular advice to help me in this case you could close the ticket, thanks for your answer.

Best regards.

[Nerivec]

The relevant bit is Delivery failed for '2503', which indicates that device (0x09c7 in hex form) could not be reached. It's not about the coordinator.
That error usually indicates a device is sleeping (if end device), is offline, or you are getting interference.
Check which device that is, and maybe try requesting the map directly in the Z2M frontend to see if you get the same problem.

Note: that error, and the error you see in the frontend (Minified React error) are two different issues.

[MikeBlueG]

Thanks for you answer, my coordinator is that device 0x09C7 and yes you re right the Z2M frontend map indicate also the same issue with LQI (see the image) [image: image.png] I just receive toda Le sam. 7 févr. 2026 à 14:15, Nerivec ***@***.***> a écrit :

…

*Nerivec* left a comment (Nerivec/zigbee2mqtt-windfront#429) <#429 (comment)> The relevant bit is Delivery failed for '2503', which indicates that device (0x09c7 in hex form) could not be reached. It's not about the coordinator. That error usually indicates a device is sleeping (if end device), is offline, or you are getting interference. Check which device that is, and maybe try requesting the map directly in the Z2M frontend to see if you get the same problem. Note: that error, and the error you see in the frontend (Minified React error) are two different issues. — Reply to this email directly, view it on GitHub <#429 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGLQWMH266DSMJ5DQIUNZDD4KXQOTAVCNFSM6AAAAACUHF5PTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNRUGQ4TMNZYGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[MikeBlueG]

sorry end of my last sentence failed, I have just received a new firmware for my coordinator perhaps it could help... Best regards. Le sam. 7 févr. 2026 à 15:52, Michel Gagliardone ***@***.***> a écrit :

…

Thanks for you answer, my coordinator is that device 0x09C7 and yes you re right the Z2M frontend map indicate also the same issue with LQI (see the image) [image: image.png] I just receive toda Le sam. 7 févr. 2026 à 14:15, Nerivec ***@***.***> a écrit : > *Nerivec* left a comment (Nerivec/zigbee2mqtt-windfront#429) > <#429 (comment)> > > The relevant bit is Delivery failed for '2503', which indicates that > device (0x09c7 in hex form) could not be reached. It's not about the > coordinator. > That error usually indicates a device is sleeping (if end device), is > offline, or you are getting interference. > Check which device that is, and maybe try requesting the map directly in > the Z2M frontend to see if you get the same problem. > > Note: that error, and the error you see in the frontend (Minified React > error) are two different issues. > > — > Reply to this email directly, view it on GitHub > <#429 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGLQWMH266DSMJ5DQIUNZDD4KXQOTAVCNFSM6AAAAACUHF5PTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNRUGQ4TMNZYGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[Nerivec]

my coordinator is that device 0x09C7

The coordinator is always 0x0000 in Zigbee.