Hi all,
I want to synchronize the cloud platform to know whether the
End Device is still connected to the OTBR network. The End Device is usually in a deep sleep, and OPENTHREAD_CONFIG_MLE_CHILD_TIMEOUT_DEFAULT is set to 60, so the gateway can know whether the Thread of the End Device is still alive.
I want to use extAddr as the identifier. The End Device will report EUI64 and SN to the cloud platform.I changed extaddr to be the same as EUI64. By looking at the extaddr field in OTBR's child table, I can corresponding to the fixed End Device. The OTBR can then report to the cloud platform whether the End Device is still connected.This is done by setting extAddr after the joiner completes. The code is shown below.
During my testing, I found that sometimes when I looked at the child table from the OTBR, the extAddr of the End Device was not the value I set, but a random value.I know extaddr is a random value,
but Rloc16 seems to be more inconvenient to use , so I can only use extaddr.
I want to know why the extaddr sometimes changed after I modified it.Or is there another way for the platform to be able to navigate to a End Device through the gateway?
--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/a1238198-d4df-4efd-9d80-1cf08959ca0an%40googlegroups.com.