[7.4.x] SLZB-06M inconsistencies when setting config IDs on startup

[Nerivec]

Reporting this since I've seen a few logs now, from different users, that show this. (I don't have the device myself, so I can't run any test.) Seems something is going wrong, that first one is the first being set during startup sequence, and is set to the same as the firmware default. Not sure why it would return as out of memory at that point?

[2024-05-05 12:07:00] warning: zh:ember: [EzspConfigId] Failed to SET "ADDRESS_TABLE_SIZE" TO "16" with status=ERROR_OUT_OF_MEMORY. Firmware value will be used instead.
[2024-05-05 12:07:00] warning: zh:ember: [EzspConfigId] Failed to SET "APS_UNICAST_MESSAGE_COUNT" TO "32" with status=ERROR_OUT_OF_MEMORY. Firmware value will be used instead.
[2024-05-05 12:07:00] warning: zh:ember: [EzspConfigId] Failed to SET "NEIGHBOR_TABLE_SIZE" TO "26" with status=ERROR_OUT_OF_MEMORY. Firmware value will be used instead.
[2024-05-05 12:07:00] warning: zh:ember: [EzspConfigId] Failed to SET "SOURCE_ROUTE_TABLE_SIZE" TO "200" with status=ERROR_INVALID_VALUE. Firmware value will be used instead.
[2024-05-05 12:07:00] warning: zh:ember: [EzspConfigId] Failed to SET "MULTICAST_TABLE_SIZE" TO "16" with status=ERROR_OUT_OF_MEMORY. Firmware value will be used instead.

_I'm guessing the ERROR_INVALID_VALUE for SOURCE_ROUTE_TABLE_SIZE is a bug in silabs firmware, reporting the wrong status, and is likely really ERROR_OUT_OF_MEMORY too._

When the device is in a state where it does this during startup (it doesn't always do it seems like), it then misbehaves in various ways. Any ideas?

[darkxst]

Its strange that is only happening with SLZB-06M, and for settings that are already set! however I can easily reproduce here on 7.4.1.

Also tried with 7.4.2 I only get a single error (which is actually the only value that is changed compared to firmware):

[2024-05-06 00:18:34] info:     zh:ember:ezsp: ======== EZSP started ========
[2024-05-06 00:18:34] warning:     zh:ember: [EzspConfigId] Failed to SET "APS_UNICAST_MESSAGE_COUNT" TO "32" with status=ERROR_OUT_OF_MEMORY. Firmware value will be used instead.

Now I have updated settings to match ZBDongle-E

https://github.com/darkxst/silabs-firmware-builder/raw/4.4.3/firmware_builds/slzb-06m/ncp-uart-hw-v7.4.3.0-slzb-06m-115200.gbl

(7.4.3 doesnt appear to have any changes in Zigbee firmware compared to 7.4.2)

Let me know if that resolves the issues for people.

[itwtds]

Its strange that is only happening with SLZB-06M, and for settings that are already set! however I can easily reproduce here on 7.4.1.

Also tried with 7.4.2 I only get a single error (which is actually the only value that is changed compared to firmware):

[2024-05-06 00:18:34] info:     zh:ember:ezsp: ======== EZSP started ========
[2024-05-06 00:18:34] warning:     zh:ember: [EzspConfigId] Failed to SET "APS_UNICAST_MESSAGE_COUNT" TO "32" with status=ERROR_OUT_OF_MEMORY. Firmware value will be used instead.

Now I have updated settings to match

ZBDongle-E

https://github.com/darkxst/silabs-firmware-builder/raw/4.4.3/firmware_builds/slzb-06m/ncp-uart-hw-v7.4.3.0-slzb-06m-115200.gbl

(7.4.3 doesnt appear to have any changes in Zigbee firmware compared to 7.4.2)

Let me know if that resolves the issues for people.

This is happening on the Skyconnect as well on 7.4.x (all tested).

`[2024-05-10 21:35:31] info: zh:ember:ezsp: ======== EZSP started ========

[2024-05-10 21:35:32] warning: zh:ember: [EzspConfigId] Failed to SET "APS_UNICAST_MESSAGE_COUNT" TO "32" with status=ERROR_OUT_OF_MEMORY. Firmware value will be used instead. [2024-05-10 21:35:32] info: zh:ember: [STACK STATUS] Network up. [2024-05-10 21:35:32] info: zh:ember: [INIT TC] NCP network matches config. [2024-05-10 21:35:32] info: zh:ember: [CONCENTRATOR] Started source route discovery. 1248ms until next broadcast. [2024-05-10 21:35:32] info: z2m: zigbee-herdsman started (resumed) [2024-05-10 21:35:32] info: z2m: Coordinator firmware version: '{"meta":{"build":0,"ezsp":13,"major":7,"minor":4,"patch":3,"revision":"7.4.3 [GA]","special":0,"type":170},"type":"EmberZNet"}'`

Thanks

[GigiPompieru]

Hi, just updated today and saw this in the logs. any update on fixing it?