#OTBR Won't Start

1 messages · Page 1 of 1 (latest)

obtuse light
#

I have two ZBT-2s, one for Thread and one for Zigbee. Both networks were originally on ZBT-1/Skyconnect but I migrated them.

I had a lot of challenges getting devices to pair via the google play services workflow before realising I had IPv6 turned off, I then managed to connect a single device, but then thread crapped itself.

I have since restarted HA, reconnected the devices, etc.

HA is running on a VM in Unraid.

OTBR won't start now. The addon logs are attached.

I also see the below in the HA logs:

Source: config_entries.py:762
First occurred: 20:16:18 (3 occurrences)
Last logged: 20:22:47
Error setting up entry Home Assistant Connect ZBT-2 (OpenThread Border Router) for otbr

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 762, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/otbr/__init__.py", line 73, in async_setup_entry
    await update_issues(hass, otbrdata, dataset_tlvs)
  File "/usr/src/homeassistant/homeassistant/components/otbr/util.py", line 268, in update_issues
    _warn_on_default_network_settings(hass, otbrdata, dataset_tlvs)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/otbr/util.py", line 224, in _warn_on_default_network_settings
    dataset = tlv_parser.parse_tlv(dataset_tlvs.hex())
  File "/usr/local/lib/python3.13/site-packages/python_otbr_api/tlv_parser.py", line 188, in parse_tlv
    raise TLVError(f"expected {_len} bytes for tag {tag!r}, got {length - pos}")
python_otbr_api.tlv_parser.TLVError: expected 71 bytes for tag 87, got 6```
📎 core_openthread_border_router_2026-02-11T20-29-06.289Z.log
#

Looks like there is a github issue suggesting this is a HA 2026.2 issue, suggesting to reinstall the addon, which I have now done, but need to get the integration working again

#

and it wants a rest api url

supple dawn
#

the integration is automatically configured based on discovery; sometimes that doesn't work, try restarting home assistant to get the discovery to run again.

#

do you have any other thread border routers, or only the HA OTBR?

obtuse light
#

i have managed to get OTBR started now

#

and lights seem to work

#

now to fix zigbee 😄

supple dawn
#

huh. I wonder how the corrupt TLV got into the network data then. If there's some thread device you have which is doing this network data change, it might happen again :/

obtuse light
#

removing the OTBR addon and adding it again fixed it apparently

obtuse light
obtuse light
#

I think I have managed to add some bulbs to thread that won't then connect to matter

#

not sure how i boot them off

#

sure i found a way to see known thread devices earlier

#

right, what breaks OTBR is turning on thread 1.4

#

Error commissioning node: Commission failed: No device discovered using identifier {"shortDiscriminator":2}! Please check that the relevant device is online.
sigh

#

i think I am going to return these bulbs, they are useless to me

obtuse light
#

ok, having tried 3 different samsung devices, i dug out a pixel 7 pro, fixed everything

orchid lark
#

I am Apple user. But which Samsung models did not work for you?

obtuse light
#

Fold 7, tablet 9 ultra, s24