Hi @tim-vk have you solved? I have the same issue: in thread integration the otbr disappare in 2 minutes.
I run otbr in docker
Hello. I have built an OTBR using the Expressif ESP32 development board. It seems to be working, at least it is advertising on mdns and Home Assistant picks it up, showing it as my preferred network. It appears to be responding to the rest api calls as expected. I also have two other thread networks, one from amazon and one from apple. When I attempt to add a thread/matter device with the companion app, Home Assistant adds it to the apple thread network, even though the Expressif network is preferred. I don’t think this is the expected behavior, correct? Also, it is the case that I have a number of thread/matter devices connected to the apple thread network that are working correctly.
Note that I have checked the log files for Home Assistant and I see no indication that it is trying to use the OTBR thread network, instead it just indicates it is connecting to the Amazon network. OTBR is clearly shown in the HA UI as the preferred network.
One other note, my OTBR is set to a different channel than my Apple network, FYI.
Finally, output from OTBR:
http://10.11.2.105/node/dataset/active
{
“ActiveTimestamp”: {
“Seconds”: 1,
“Ticks”: 0,
“Authoritative”: false
},
“NetworkKey”: “9985b215cafdcf448cf968e3815b7fe5”,
“NetworkName”: “ha-thread-d758”,
“ExtPanId”: “a588b9c2145b31e3”,
“MeshLocalPrefix”: “fdda:db61:38de:8c79::/64”,
“PanId”: 55128,
“Channel”: 15,
“PSKc”: “8a220936cd01c250d77449531c98b614”,
“SecurityPolicy”: {
“RotationTime”: 672,
“ObtainNetworkKey”: true,
“NativeCommissioning”: true,
“Routers”: true,
“ExternalCommissioning”: true,
“CommercialCommissioning”: false,
“AutonomousEnrollment”: false,
“NetworkKeyProvisioning”: false,
“TobleLink”: true,
“NonCcmRouters”: false
},
“ChannelMask”: 134215680
}
Hi Have you already solved this problem? My Home assistant has the same error