End node rejoining issue on JN5169 with Zigbee 3.0 SDK

[dhvanil_patel1]

Hi All,

We are not able to rejoin the ZigBee end node to the JN5169 Host (with default IoT Control Bridge firmware) without erasing persistent data of JN5169 host module. For the first time, after a factory reset, We start the ZigBee network on the JN5169 host and start permit joining on host module to allow to join end node. In this case, the end node is able to join the ZigBee network. Now we remove or factory reset the end device and put it into discovery mode again and enable permit-join window on JN5169, Then Zigbee End device is failed to rejoin the ZigBee network until we erased persistent data of the host and start the network again on JN5169 host

We have tested with prebuilt binaries provided in the JN-AN-1216 package as well as compiled binaries from the default source of the  JN-AN-1216 package. We have tested it with Zigbee gateway user interface GUI Tool (ZGWUI tool)

Above mentioned issue faced with JN5169 module only but the same thing works well if we use JN5179 as a host(same source code used for both module testing).

Steps followed:

1. Flashed Host node(JN5169 DR1198 Dongle) with the prebuilt host binary(ZigbeeNodeControlBridge_JN5169_FULL_FUNC_DEVICE_1000000.bin) provided in  JN-AN-1216 package and also tried by building "ZigbeeNodeControlBridge_JN5169_FULL_FUNC_DEVICE_1000000.bin" image from default application note source.

2. We have started network on the Host node(JN5169 DR1198 Dongle) and enabled permit-join window. Then we have put ZigBee bulb(JN5179 Dimmable light bulb) in discovery mode and it has joined with the host and we were able to control the bulb.

3. Factory reset the ZigBee bulb and re-enable permit join window on the host. Observed that bulb is not joining the network.

4. If we erase persistent data of the JN5169 Host and then starting the network and enabling the permit-join then the bulb is joining the network.

5. We have performed the same scenario with the JN5179 as a host but it is working as expected and there is not any joining issue. 

[huparke]

Hi all:

          I have encountered the same problem, how do you solve it?

         if APP_vFactoryResetRecords(void) no  

// clear out the stack
// ZPS_vDefaultStack();
BDB_vSetKeys();

        this device to join the coordinator again,but no join the other coordinator;

      I want the FactoryReset node to join all the coordinator，how to do?

[liuxiang]

Hello, I have encountered the same problem, how do you solve it?
Thank you.

[kevinsung]

Hi, same issue as repeat Find and Join with Factory Reset, the test result not join any more,

I found the BDB return fail to join, the test information were stack apply event "ZPS_EVENT_NWK_FAILED_TO_JOIN" on Node and status code is " ZPS_APL_APS_E_SECURITY_FAIL", so it is security check failed.

NOTES: I also check InFrameCounter and OutFrameCounter both match documents , no any report "Bad Frame Counter" from STACK.

[limcb]

Hi, please refer to JN-UG-3113, Appendix B.3 Clearing Stack Context Data Before a Rejoin. 

Before factory resetting the Node, please do a Device Leave / ZPS_eAplZdoLeaveNetwork before factory reset to notify Coordinator of changes. 

[liuxiang]

I have two devices, a coordinator, an end node, can be successful, but when I re-programmed the node again (the EEPROM erase), the node can not join the coordinator, the coordinator must also erase Once the EEPROM, the terminal node can join the coordinator again.
Know why? Help me think about it
If a MAC address of 01 equipment to join a coordinator,
And then erase the EEPROM with the MAC address 01 device
MAC address of 01 this device to join the coordinator again, the network can not be successful. The The Why is this the case?