CC2530: ZED proper join procedure, and rejoin.

Basically, Z-Stack 3.0.2 end device would do rejoin automatically every 10 seconds when it loses network connection. You don’t have to do anything in your application unless you want to change the rejoin period.

how about joining the network ? Is it correct to call bdb_StartCommissioning(BDB_COMMISSIONING_MODE_NWK_STEERING) to join network after boot up of the end device to get auto join functionality ?

Yes, it is correct.

and how about the newtwork in case where coordinator will die ie. cause of power loss ? Will it work properly after coordinator comes back to life ? From my observation i can say that it doesn't work. My end devices are no longer avilable after ZC boots up again. Any hints to this ?

As I replied, end device should join automatically when ZC is back. If it doesn’t happen in your case, I suggest you to use sniffer to check what happens over the air.

This is what happens when my end device loss its parent. It starts to send data requests to 0xfffe. The ZC seams to respond on that with some broadcasts, any hints what i should look for ?

Those are MAC layer retries. What are you actually looking for?

The problem is, that after parent loss i can't communicate to the end device anymore. It looks like it can't change the parent ? Im looking for any hint where i could start debugging to solve this problem.

After power cycling your Zigbee2mqtt + ZC based on cc2530, would it keep previous network and don’t start new one?

I think it does I have fixed PAN ID on both of the devices, ZC and ZED. I saw yesterday that sometimes my coordinator works after it comes back. In this scenario when I would unplug the router device which is parent of my ZED after ZC is available again, my ZED is no longer available in the network. I presume that as the coordinator is alive again, my end node should change its parent back to ZC right?

So the sequencs of lifecycle of the devices are:

ZED , ZC up

ZED joins the network using coordinator as a parent

Router up

ZC - power down

ZED - switch its parent to coordinator

ZC - power up

ZED - is working because it switch its parent to some router device

Now router goes down.

ZED is no longer avilable in the network. On the screenshot from yesterday you can see the place where it happens.

Yes, ZED should rejoin ZC as its new parent node when ZR is turned off.

Make sure that the ZC shows the same PAN ID when it comes back online.  Does the ZC respond to the ZED's Beacon Request (after entering an orphan state) and Network Rejoin (if one is provided)?  Please provide the full sniffer log if possible.

Regards,
Ryan

Hi.

Here is my full sniffer log. In text file, and on the screenshots. I can see that i got some Beacon response from the ZC but this is all. I also tried to use ext pan id but it didn't change anything.

sniff_output.txt

Can you attach sniffer log in pcapng format?

snif.zip

Thanks Ryan! It works. That was what i was looking for. I didn't know where to start debugg...  The problem was that i modified part of logic that was responible for the buttons/interrupts and There is a code that restores network parameters. It was triggered all the time. Now everything works perfect. Thanks!