OpenThread
Failed to process Child Update Response as child: NotFound error as well as Bad UDP Checksum on Esp32-H2 #11248
Replies: 2 comments 4 replies
-
|
This typically occurs when the Active Operational Datasets are not matching. Can you output the Active Operational Dataset from your different Thread devices and compare their contents? Specifically, look at the mesh-local prefix configuration. |
Beta Was this translation helpful? Give feedback.
-
|
To get the mesh-local prefix i need to use OT-CLI, where do i run CLI from? does it need to be from a board that's currently running open thread? |
Beta Was this translation helpful? Give feedback.
-
|
How did you configure the Active Operational Dataset on the different devices? Is it possible to see the list of IPv6 addresses on the different devices from the logs? Otherwise, you might need to update the code running on the devices to output the information. |
Beta Was this translation helpful? Give feedback.
-
|
for the active operational dataset is that stuff like network name, panid, extpanid, and network_key. otherwise not sure what the Active Operational Dataset is or how to configure it. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, correct. See: https://github.com/openthread/openthread/blob/main/src/cli/README_DATASET.md#active-operational-dataset |
Beta Was this translation helpful? Give feedback.
-
|
I was able to get a list of IPv6 addresses, listed 4 of them only one was able to be pinged from the ESP32 board. Rn we are thinking possible an issue with the dataset not matching and causing a mismatch in the UDP, able to view and change the dataset for the ESP32 using "dataset active -x" but unsure of how to find the corresponding dataset for our border router, using a nrf52840 running the OT-RCP through HAOS |
Beta Was this translation helpful? Give feedback.
-
Describe the bug A clear and concise description of what the bug is.
When setting up a thread network to home assistant the endpoint devices (ESP32-H2-Devkit + DHT22) seem to connect to our border router (nrf52840) as it appears in topology, however when starting the code on the ESP32 we get an error of "Failed to process Child Update Response as child: NotFound" and "Failed to perform next registration: NotFound". Additionaly when opening the topology page in the web app, it gives "Bad UDP checksum" as well as "Failed to handle payload: Drop"
To Reproduce Information to reproduce the behavior, including:
Expected behavior A clear and concise description of what you expected to happen.
Home Assistant OTBR add-on will show some recognition of data being sent, not just mirroring the bad UDP checksum
Console/log output If applicable, add console/log output to help explain your problem.
Home Assistant Log:
Additional context Add any other context about the problem here.
N/A
Beta Was this translation helpful? Give feedback.
All reactions