nrf5340 zigbee network steering join failed

[Elyxoft]

Product is a zigbee router.

Use nrf connect sdk 2.4, update it is not an option.

The zigbee join work fine most of zb3.0 coordinator, BUT with an old coordinator it failed:

15.4 association is ok

product request TC key

Coordinator response with "ZigBeeAlliance09" tc key

product signal network steering failed and leave network

How to configure stack to accept this tc key as a valid key ?

Regards,

Sébastien

[Amanda Hsieh]

Hi, 

Could you try this post?

Regards,
Amanda H.

[Elyxoft]

Hi,

If I enable legacy device support, then the tc link key exchange is not done and so the TC reject me !

My device announce he has a revision stack that is zb3.0 stack so the TC wait for a TC link exchange and au key confirm

I have not found an option to force my device to accept this tc link key.

another way can be to enable legacy mode and as soon as I am in the network manage by myself TC link key request and confirm exchange, is it a good way ?

regards,

sébastien

[Amanda Hsieh]

Hi, 

Can you provide more information about the old ZC? For example, which revision is it? If you enable legacy device support and the ZC is older than R21, then the TC link key exchange should succeed after receiving only the first TC key. 

Could you also provide the sniffer log? If the log is encrypted, please share the network key so we can decrypt it.

-Amanda H.

[Elyxoft]

Hi,

First test (capture :2025_10_21_capture_entry_network_failed_legacy_with_require_tclink_missing_key_confirm.pcapng , use key 5a6967426565416c6c69616e63653039)

code:

zb_set_network_router_role_legacy(CONFIG_ZIGBEE_CHANNEL_MASK);

zb_aib_tcpol_set_update_trust_center_link_keys_required(true);

error output :

<err> zdo_com_classic_prod: zdo_classic_handle_comm_signal, ZB_COMM_SIGNAL_TCLK_UPDATE_FAILED

2025_10_21_capture_entry_network_failed_legacy_with_require_tclink_missing_key_confirm.pcapng

[Elyxoft]

Second test, use same key for capture 2025_10_21_entry_zb3_failed_due_to_tclink_key.pcapng

code:

zb_set_network_router_role(CONFIG_ZIGBEE_CHANNEL_MASK);

2025_10_21_entry_zb3_failed_due_to_tclink_key.pcapng

[Elyxoft]

My understanding:

As our product announce with as rev22 of the stack (in node descriptor), I assume TC wait for a valid TCLink Key and Key confirm exchange.

In first case the tc link key is present (with failure) but not the key confirm, so the TC request we leave the network

In second case TC link exchange is present but it seems that our product refuse this key and decide to leave the network.

I can not change the behavior of the TC, how can I adapt my product code to do waht the TC want ?

Regards,

Sébastien