OpenThread
Commissioner Joiner Failed #7893
-
|
Hello OpenThread community! I am performing some operations to provision the Endnode device into openthread network using the commissioner. In that I am enabling the commissioner and adding the joiner node on the Gateway node using the below command. commissioner start And then starting the joiner on the Endnode using the below command. ifconfig up With this commands I am able to provision the Endnode with the Gateway successfully. Now If I factory reset the Endnode and again do the same process for the reprovision of the device then sometimes I am getting some failure or delay to provision the device. // This is for the successful case[2022-07-08 19:33:47] Commissioner: disabled // This is for the failure case[2022-07-08 19:34:32] ~ Discovery Request from b4e3f9fffe88526d: version=3,joiner=1 Few questions related to this.
Note: I am using the openthread version 1.2 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
I'm not sure. I was not able to reproduce this issue when following the Commissioning Quick Start Guide.
OpenThread's Joiner implementation does not implement retries, so I'm not sure where the 5 seconds or 2 minutes are coming from. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much jwhui for the response. I have done some changes for the extended mac address in the open thread stack as below to get the unique eui64 in the child table of gateway every time when the end node-connect. otExtAddress extAddress; when I remove these changes commissioner is working file every time. But I need the same eui64 of the endnode every time on the connection with the gateway. Do I have any other way for this? |
Beta Was this translation helpful? Give feedback.
-
|
Note: please respond directly to prior messages rather than suggesting a new answer. The Thread Specification requires a device to generate an Extended Address at random each time a device joins a new Thread network to preserve privacy. If you want a way to uniquely identify a device, I suggest communicating the unique identifier using something other than the Extended Address. |
Beta Was this translation helpful? Give feedback.
-
|
Can you please suggest what other unique identifier can be other than the eui64? |
Beta Was this translation helpful? Give feedback.
-
|
Many end products have a serial number that is not related to the EUI-64. |
Beta Was this translation helpful? Give feedback.
Thank you so much jwhui for the response.
I have done some changes for the extended mac address in the open thread stack as below to get the unique eui64 in the child table of gateway every time when the end node-connect.
otExtAddress extAddress;
otLinkGetFactoryAssignedIeeeEui64(instance, &extAddress);
otLinkSetExtendedAddress(instance, &extAddress);
when I remove these changes commissioner is working file every time. But I need the same eui64 of the endnode every time on the connection with the gateway. Do I have any other way for this?