Thread fails to connect

[noranraskin]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

Commissioning Thread esp32 C6 with light_rgbcw_ws2812 works with home assistant with setup openthread border router.

Actual behavior (suspected bug)

I get an error message in home assistant saying it couldn't connect the device.

Here is the output from the code space console. The log was too long to add it into the dedicated field.
console.txt

Error logs or terminal output

This is the log from the openthread border router:


[15:41:04] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b067e5ac-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_e0492bbfc8c2ef11bcb855ac8048b910-if00-port0?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT---: Radio URL: trel://wlan0
[NOTE]-ILS-----: Infra link selected: wlan0
54d.17:29:22.140 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.045 [N] RoutingManager: BR ULA prefix: fd8e:5d97:31ed::/48 (loaded)
00:00:00.045 [N] RoutingManager: Local on-link prefix: fd33:f5b0:129c:f275::/64
00:00:00.064 [N] Mle-----------: Role disabled -> detached
00:00:00.073 [N] P-Netif-------: Changing interface state to up.
00:00:00.082 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.082 [W] P-Netif-------: Failed to process request#6: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-configure: starting
s6-rc: info: service otbr-web: starting
s6-rc: info: service otbr-web successfully started
[15:41:05] INFO: Starting otbr-web...
[INFO]-WEB-----: Running 0.3.0-b067e5ac-dirty
listenAddr not specified, using default ::
[INFO]-WEB-----: Border router web started on wpan0
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[15:41:05] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
00:00:27.299 [N] Mle-----------: RLOC16 b000 -> fffe
00:00:27.575 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:34.075 [N] RouterTable---: Allocate router id 44
00:00:34.075 [N] Mle-----------: RLOC16 fffe -> b000
00:00:34.077 [N] Mle-----------: Role detached -> leader
00:00:34.078 [N] Mle-----------: Partition ID 0x38ee4755
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:36.354 [W] DuaManager----: Failed to perform next registration: NotFound


The output from the Codespace console was too long. Attached as file see above

Steps to reproduce the behavior

1. Create a new code space
2. Set Product: light_rgbcw_ws2812, chip: ESP32-C6: Thread
3. Prepare device, upload configuration, upload code
4. Click on QR Code button and try to pair device with home assistant companion app
5. When warned about the device not being official dismiss warning and add anyway

Project release version

latest

System architecture

other (details in Additional context)

Operating system

Linux

Operating system version

Github Codespace

Shell

ZSH

Additional context

I already connected other thread devices to home assistant and also flashed esphome on the exact same dev module to rule out a hardware fault.
Nevertheless this could very easily be a user error. How could I further debug this and trace the issue better?

[ChinmayLonkar]

Hello @noranraskin ,

After checking the logs it feels that there is some issue related to thread network or hardware that you are using. I recommend you to please try again with the latest code, I have modified the data models for thread and wifi and have also tested on my side. Please let me me know if you still face issues.