[ZIGBEE] Doesn't receive "Transport Key" in rejoining.

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Marte Myrvold — Tue, 24 Aug 2021 06:15:01 GMT

Hi,

That is great to hear, and I am glad that we could help 🙂

Best regards,

Marte

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Tue, 24 Aug 2021 01:42:39 GMT

It works. Thanks for Nordic Team. 🙂

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Mon, 23 Aug 2021 09:19:31 GMT

Thanks, Myrvold.

I'm so appreciate it! I'll reply back after testing.

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Marte Myrvold — Mon, 23 Aug 2021 07:38:04 GMT

Hi,

Sorry for the delay, but we now have a workaround for you to try. Let me know if you have any issues with it.

devzone.nordicsemi.com/.../TC_5F00_rejoin_5F00_workaround.zip

Best regards,

Marte

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Mon, 21 Jun 2021 13:24:39 GMT

Okay Thanks :(

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Marte Myrvold — Mon, 21 Jun 2021 08:37:24 GMT

Hi,

The only update from our developers is that they are still waiting for a workaround from DSR, unfortunately.

Best regards,

Marte

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Mon, 21 Jun 2021 04:07:13 GMT

Any update on this?

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Marte Myrvold — Wed, 09 Jun 2021 14:10:59 GMT

Hi,

I have forwarded this to our Zigbee team, and I am waiting for a response from them to hear if there are any other possible solutions.

Best regards,

Marte

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Wed, 09 Jun 2021 00:53:07 GMT

Hi, Marte.

I already know that ZBOSS's sleepy device only change a new network key when it should be received by a new encrypted APS ACK. I updated a sniffer file of this process.

The problem of this solution is that the coordinator should be ZBOSS's coordinator. The other coordinator doesn't work in this way. I currently have developed a interface with silicon labs's coordinator.

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Marte Myrvold — Tue, 08 Jun 2021 15:57:16 GMT

Hi,

Edvin is out of office, so I will update you on this.

Our Zigbee team does not have a solution to the issue, but the following should help in some cases:

You can implement the sleepy end device to periodically send a ZCL frame with APS ACK requested to the coordinator. When the network key is switched, the device will receive a frame encrypted with the newest NWK key from the coordinator, which should trigger the device to switch to the new key. This assumes that whenever a new NWK is sent, the device receives the key, and some time later, the device switches to the new key when ZCL packet is sent to the coordinator and APS ACK is received. This will not work if the device does not have the new NWK key.

Best regards,

Marte

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Tue, 08 Jun 2021 05:27:49 GMT

Hi, Edvin.

I couldn't get any support by RSM. So, I tried to connect ZBOSS DSR.

DSR says it will be fixed, but, the schedule continues to be delayed.

Is it not possible to fix this issue for the nordic zigbee team?

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Edvin — Tue, 30 Mar 2021 13:20:30 GMT

Well, all I can tell you is that they will ask our stack provider about a workaround. I don't know if/when they will provide it. I agree that the RSM can't say when at this point, but perhaps they can do the digging for us and ask the right people.

I can't put the RSM contact info in this ticket, because it is a public ticket. Send me a PM here on devzone (click my username and then send me a message).

If not, we can wait and see when/if the workaround comes, which is also fine. I will let you know when I hear anything in the internal ticket.

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Tue, 30 Mar 2021 08:45:42 GMT

I don't have RSM contact information. The Company is located on South Korea.

[quote userid="26071" url="~/f/nordic-q-a/72279/zigbee-doesn-t-receive-transport-key-in-rejoining/302496#302496"]Perhaps they have some input on the timeframe.[/quote]

I don't understand your mention. Isn't RSM not only responsible for sales?

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Edvin — Tue, 30 Mar 2021 07:38:23 GMT

[quote user="_maibi"]2) Since the zigbee team has recognized this issue, will this be fixed in the future? If so, how long will it take?[/quote]

We have asked our stack provider to provide a workaround for this. Unfortunately, I don't have a timeframe for the workaround. Firstly it is hard to say because we rely on this external company, and secondlywe don't really discuss roadmap plans (although this is not roadmap). Do you have any RSM (Regional Sales Manager) contact information? If not, let me know in a PM where you are located, and I can provide it to you. Perhaps they have some input on the timeframe.

Best regards,

Edvin

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Mon, 29 Mar 2021 14:44:21 GMT

Hi, Edvin. Thank you so much for answering. I've been waiting for a long time. 🙂

[quote userid="26071" url="~/f/nordic-q-a/72279/zigbee-doesn-t-receive-transport-key-in-rejoining/302346#302346"]Our investigation showed that this seems to be an unhandled case in the stack. We have taken it for further investigation. Unfortunately, the only workaround at the moment is to join the network again, when the key is lost.[/quote]

We will provide our product to the hotel, If the pairing is broken, our staff must be dispatched, so it is impossible to launch a product with this problem.

[quote userid="26071" url="~/f/nordic-q-a/72279/zigbee-doesn-t-receive-transport-key-in-rejoining/302346#302346"]I would also think that another workaround would be to wake up more often, so that the parent has the chance to transmit the key change before it is too late. Does your device wake up regularly? If so, on what interval?[/quote]

I set it to 5 seconds. However, the exact reason is not known, but if the sleep continues for a long time, there is a problem that the data request is no longer sent. I think this has to do with a stack overflow or problem of duplicated resource usage, but I have no idea how to start debugging.

1) Is there a resource table used by zigbee stack?

2) Since the zigbee team has recognized this issue, will this be fixed in the future? If so, how long will it take?

3) As I said before, The workaround you mentioned only works when using the nordic coordinator. Even if sleepy zed receives a transport key (even after switch key), it always uses the old key. When the coordinator receives the packet sent with the previous key and sends APS with the updated key, sleepy zed starts to use the updated key. However, in this way, the feature of sending a response to the previous key after the coordinator changes the key is a special way that works only in nordic, and the workaround does not work because the other coordinator does not send a response to the previous key after the key update.

If sleepy zed doesn't receive a response encrypted with updated key, sleepy zed never update his key.

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Edvin — Mon, 29 Mar 2021 10:53:33 GMT

I received a reply from our Zigbee team today:

"Our investigation showed that this seems to be an unhandled case in the stack. We have taken it for further investigation. Unfortunately, the only workaround at the moment is to join the network again, when the key is lost."

I would also think that another workaround would be to wake up more often, so that the parent has the chance to transmit the key change before it is too late. Does your device wake up regularly? If so, on what interval?

BR,

Edvin

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Wed, 24 Mar 2021 08:20:08 GMT

Any update on this? Anything they say is good, so please forward it.

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Thu, 18 Mar 2021 09:18:47 GMT

Okay. Thank you for a reply. I'm not glaring at you, but it's painful because of my pressure on the project. I hope your zigbee team will get an answer as soon as possible. :(

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Edvin — Thu, 18 Mar 2021 08:52:37 GMT

Hello,

I have forwarded this to our zigbee team, but I have not received a reply yet. I'll ping them.

Trust me, if I knew what was wrong I would tell you.

Let me try to get some input from our Zigbee team and get back to you rather quickly.

FYI: Your ticket has had the status "open" all the time, so the intention is to solve this issue before we close this ticket.

Best regards,

Edvin

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Wed, 17 Mar 2021 08:37:29 GMT

Edvin,

It has already been a month since I started asking questions on this issue.

However, I am not getting a single satisfactory answer to this question. I don't even know if it's covered by your Zigbee team.

Please let me know how it is going.

I will upload the sniffer logs. Both are light switch examples, one is sdk 3.2.0 and the other is sdk 4.1.0.

devzone.nordicsemi.com/.../nrfcli_2D00_lightswitch_2D00_sdk3_5F00_2_2D00_nwkkeychange3times_2D00_failed_2D00_rejoin.pcapng

devzone.nordicsemi.com/.../nrfcli_2D00_lightswitch_2D00_sdk4_5F00_1_2D00_nwkkeychange1times_2D00_failed_2D00_rejoin.pcapng

sdk 4.1.0 only sends request rejoin to the previous key after switch key and does not do any other action, but sdk 3.2.0 sends request rejoin to the previous key and receives the APS of the updated key sequence and performs unsecure rejoin.

I checked this and downgraded the sdk in the project, but it seems that the execution condition of unsecure rejoin should receive the APS or Rejoin-Response of the updated key sequence. If the coordinator fails to APS or Rejoin-Response response to the previous key after several key updates, even this cannot be performed.

I don't know if you have checked the previous logs, but try adding them again. You may be busy, I hope that good communication does not lead to misunderstandings.

Our project has been delayed a lot. and We are considering silicon labs chips as well. But we don't want to add silicon labs chip as an additional communication module just because of this software problem. Please tell me your milestone. Please let me know if it is possible to modify it or not.

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Mon, 15 Mar 2021 07:46:45 GMT

Any update on this issue?

I have tried to test emberznet zed example which is made by silicon labs with nrfcli for a coordinator.

I attach a sniffer log that zed handles properly during the network key change process.

In this log, After switching key, zed tried 3 times of secure rejoining request. and finally tried to unsecure-rejoining request.

The zed also received transport key encrypted with TC-Link Key.

After this, the zed broadcasted Device Announcement encrypted with updated network key.

devzone.nordicsemi.com/.../nrfcli_2D00_emberznet_2D00_join_2D00_rejoin_2D00_pwroff_2D00_nwkkeychange_2D00_rejoin2.pcapng

The Nordic Stack must also behave the same.

And although not exactly, it seems that there is an overflow inside the stack. I am not able to find a way to do anything because I am not able to debug right now.

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Thu, 11 Mar 2021 00:48:13 GMT

Thanks for your reply. I will wait for your response.

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

Edvin — Wed, 10 Mar 2021 15:24:19 GMT

Let me check with our Zigbee team how to approach this issue.

I will get back to you as soon as I hear from them.

Best regards,

Edvin

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Wed, 10 Mar 2021 01:05:58 GMT

In my opinion, firstly, the transport key message should be decrypted with the trust center link key, but it seems that the decryption is attempted with the previous network key.

secondly, I think zed should receive and execute the trasnport key message instead of receiving and executing the subsequent APS Ack message.

What's going on on this issue right now?

RE: [ZIGBEE] Doesn't receive "Transport Key" in rejoining.

_maibi — Tue, 09 Mar 2021 13:45:04 GMT

[quote userid="26071" url="~/f/nordic-q-a/72279/zigbee-doesn-t-receive-transport-key-in-rejoining/298711#298711"]I interpret the rejoin with trust center as a "forget network and join the network as if it was never part of the network". Or do a "factory reset" if you want to call it that.[/quote]

As far as I can understand, trust center rejoin is a common rejoin method to request in case zed lose or miss network key.

[quote userid="26071" url="~/f/nordic-q-a/72279/zigbee-doesn-t-receive-transport-key-in-rejoining/298711#298711"]If the key update is lost because the ZED was sleeping, then it is no longer part of the network, and it doesn't have the correct keys, right? So it can't use the old keys to re-attach to the network.[/quote]

yes it is. I made this condition by turning off zed and perform switch key.

[quote userid="72896" url="~/f/nordic-q-a/72279/zigbee-doesn-t-receive-transport-key-in-rejoining/298543#298543"]nrfcli-join-pwroff-switchkey-rejoin.pcapng[/quote]

After the power is turned on, the zed requests rejoin method without security.

The coordinator responds to rejoining request with success.

and it send Transport Key message.

this message encrypted with Trust Center Link Key which exchanged in joining has new network key.

-> Trust Center Link Key In Joining

Since the new key was encrypted with the exchanged key in joining called Trust Center Link Key, although zed can decrypt the key, but the key is not updated at all.

the zed always uses old key sequence and value.