#OTBR Cooked after upgrading to ZBT-2

1 messages · Page 1 of 1 (latest)

somber harbor
#

Upgrading to ZBT-2 form my ZBT-1 led to my OTBR to become nonfunctional.

Issue remains after multiple reboots and even reverting to previous backup.

Looking at the logs here are some of the main errors I receive.

[W] DuaManager----: Failed to perform next registration: NotFound
[N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:
[N] MeshForwarder-: Dropping IPv6 UDP msg, len:
[W] Mle-----------: Failed to process Child Update Response as child: NotFound[W] Mle-----------: Failed to process Link Accept: Security

Can't connect to any of my old/new thread devices.

Please Help!

LOGS


Add-on: OpenThread Border Router
OpenThread Border Router add-on

Add-on version: 2.16.0
You are running the latest version of this add-on.
System: Home Assistant OS 17.0 (aarch64 / green)
Home Assistant Core: 2026.1.3
Home Assistant Supervisor: 2026.01.1

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

atomic lava
#

Have you found any solutions yet?
I saw a beta just came out for the OTBR addon.
I'm thinking about wiping all matter and thread setup, clearing all devices, and starting over.

autumn basin
#

@distant eagle is this a failed thread migration that can be recovered?

distant eagle
#

Please give the beta a try!

When migrating Thread, think of it like adding a brand new border router to your Thread network and then disconnecting your old border router. It'll take a minute or two for devices to reroute (since a border router has been removed) but it should be automatic. A lot of runtime bugs have been fixed with OTBR in the beta. It looks like your Thread network settings were properly migrated but OTBR is having trouble starting up. This is probably a bug that has been fixed in the beta.

somber harbor
somber harbor
# atomic lava Have you found any solutions yet? I saw a beta just came out for the OTBR addon....

Just got back from a long work trip. Unfortunately even after updating to the latest firmware for both home assistant and the OTBR app all my thread devices are still unavailable.. Currently on OTBR 2.16.4. Even tried toggling on the beta but still nothing.. Would hate to do it but do you think If I delete the matter integration with all it's stored devices it will get the OTBR app working again?

somber harbor
#

Updated my ZBT-2 to beta firmware 2.7.2.0 and rebooted.. Thread devices still appear as unavailable : /

somber harbor
distant eagle
#

@somber harbor can you uninstall the OTBR addon (I think an option is provided to delete existing data) and reinstall it?

distant eagle
#

How are you running HA OS?

somber harbor
#

Using HA Green

#

Been making slight progress on reddit.

distant eagle
#

Oh. Do you not have IPv6 enabled in your router??

somber harbor
#

Just enabled it today

somber harbor
#

@distant eagle not sure if the Ipv6 functioning right..

somber harbor
#

output = 1

somber harbor
#

ZBT-2 acting as child

somber harbor
#

Killed power to the entire house and it somehow got the ZBT-2 to switch roles from a child to a router. OTBR is finally back up and running! @distant eagle

distant eagle
#

Nice! The mesh is kinda self organizing so the specific role your ZBT-2 takes is up to consensus with other devices on the mesh

silver quarry
#

This is kinda weird, the "thread border router" functionality (routing between thread and outside networks) should still be working is the TBR is a "child" device in the thread network.