Logger: homeassistant.config_entries
Source: /usr/src/homeassistant/homeassistant/config_entries.py:861
First occurred: 18 February 2026 at 22:50:19 (2 occurrences)
Last logged: 18 February 2026 at 22:50:39
Error setting up entry 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 146 bytes for tag 185, got 6
---
Logger: homeassistant.helpers.frame
Source: /usr/src/homeassistant/homeassistant/helpers/frame.py:307
First occurred: 18 February 2026 at 22:50:39 (1 occurrence)
Last logged: 18 February 2026 at 22:50:39
Detected that integration 'otbr' creates a config entry when another entry with the same unique ID exists. This will stop working in Home Assistant 2026.3, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+otbr%22
I’m using a SLZB-MR1 and have the OTBR app / addon running.
“No border routers found” coupled with the OTBR integration error strongly suggests your OTBR app (add-on) is not running — or at least not with the network name and credentials it used to have.
A separate, non-preferred OTBR network is appearing in your list, suggesting either you fired up a third border router, or somehow your add-on’s config changed. Removing and re-adding the OTBR integration to point to this new instance should (should!) give you the option to add it to the old preferred network (via the three-dot menu).
I removed / deleted the OTBR and Thread integrations from my HA instance.
I restarted the HA app and the OTBR addon.
I then tried to re-add Thread integration (discovered automatically) and then manually added the OTBR integration once again. But I still get the same errors.
I see no HA preferred Thread network and the other 2nd Thread Network is also showing. Along with the Thread router / network for Tado.
Is there something else I need to do to get this to work or clear out that rouge, additional Thread network?
Would removing the OTBR app completely help?
Logger: homeassistant.config_entries
Source: /usr/src/homeassistant/homeassistant/config_entries.py:861
First occurred: 18:30:55 (1 occurrence)
Last logged: 18:30:55
Error setting up entry Open Thread 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 146 bytes for tag 185, got 6
I was able to fix this issue, by removing the OTBR App and forcing the deletion of the App data.
Then removing both the Thread and OTBR integration.
Once I re-added the OTBR App, and reinstalled the Thread and OTBR integration. Everything started to work as expected again.
I’ve then added the HomeAssistant Thread network into the Tado one (the tado one was in place first). So now there are now two border routers and one Thread network. Best of both worlds.
I’ve then added the HomeAssistant Thread network into the Tado one (the tado one was in place first). So now there are now two border routers and one Thread network. Best of both worlds.
Can you ellaborate on the above? How did you add HA thread into the tado thread? Did you combine the thread networks? I didn’t know this can be done. I have my MR3U as my HA thread network and 2 tado routers (wireless router x - wired to my viessmann boiler and a bridge x).
Can you explain how you manage to only have 1 thread network?
Unfortunately, there’s nothing really about merging them. I don’t think that is possible, that is why, if you have done it with tado, please do share. I was curious and thought that could not be done. They use different credentials, so they cannot mesh, at least that’s what I thought. What you linked does not show how these can be combined.
My tado thread has
• 2 border routers (TR1 + IB1)
• No info button
• No credential export
So HA does not have the dataset for the tado network. Without the dataset, it cannot join or merge it. Or?
