OpenThread
-
|
I seem to be super confused and need help. sometime later....
What i would like to do:
My questions:
Can anyone provide guidance or direct me to a how to? |
Beta Was this translation helpful? Give feedback.
Replies: 20 comments 132 replies
-
|
It's working! - though i am still confused about persisting state across container refreshes.... which i think is required for the mesh network to be reformed when the container is recreated? any answers i think i have found have been updated in the OP
|
Beta Was this translation helpful? Give feedback.
-
|
notes:
|
Beta Was this translation helpful? Give feedback.
-
|
this is my docker compose if anyone wants to critique (i created an external macvlan for the network) |
Beta Was this translation helpful? Give feedback.
-
Exactly. Matter comes with it's own commissioning flow, which essentially transfers the complete Thread operational dataset to the device. That same flow is used for WiFi. So in a way, Matter standardized commissining for it's purpose.
Currently importing Thread credentials to the HA iOS App is not completely working, but it should be ready with the next release Core release (2024.7.x) 🤞 |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, i was forced to delete the OTBR container + replug the SkyConnect as it was non functional
it either used data on the RCP or home assistant store the previous network in thread AND persisted that even when i deleted the OTBR integration! i am trending to the latter..... |
Beta Was this translation helpful? Give feedback.
-
I answered the previous question - the network data is stored with the thread integration, however it + otbr integration do not gracefully handle the OTBR container disappearing, i found this was what i had to do if i update the container:
After that the network would be reformed. Unclear if this is a bug or a feature. |
Beta Was this translation helpful? Give feedback.
-
Currently, the OTBR integration in Home Assistant is single instance. But it does assume that single instance has a persistent storage. The OTBR (or more specifically, the ot-br-posix) implementation stores by default it's information under
So no, the current behavior is really how it is intended to work. What you essentially cause by not making I'd recommend to make FWIW, this is the script/line which makes sure that the location is presistent for the HA OpenThread Border Router add-on. |
Beta Was this translation helpful? Give feedback.
-
|
I have one remaining confusion - why store container state at all when the hass OTBR integration seems to have enough data to reform the network with a fresh container (as i have seen it do when i readd it after tearing down the official OTBR container [not addon]) it seems hass is already storing some sort of state (TLV + other stuff?) irrespective of what the container stores in its bind mount? As i understand more what configures what, i can then think more about how to fork and refactor the official container or fork a standalone version of the addon-otbr container that removes the supervisor stuff... my gut says do the latter.... |
Beta Was this translation helpful? Give feedback.
-
|
based on the suggestion in this thread home-assistant/addons#3532 (comment) i am now trying another approach:
ser2net compose file (runs on the remote pi) set2net.yaml file otbr-addon yaml config
|
Beta Was this translation helpful? Give feedback.
-
|
this approach has the advantage of ensuring the mesh formation happens if everything is rebooted |
Beta Was this translation helpful? Give feedback.
-
|
Honestly, I am not a huge fan of the ser2net solution. Thread is already IP level, so why first forward to another IP participant. The RCP protocol is somewhat timing sensitive, so you might run into surprises. |
Beta Was this translation helpful? Give feedback.
-
me neither - its why my pi runs zwavejs2mqtt and zigbee2mqtt using docker on it... the reason is a)it puts the radios in the center of the house and not next to an RF noisy rack and b)when i started i had no easy way to have USB ports on my hass VM as at the time i used hyper-v the only reason i went down this path is when running the OTBR official container if i tear down the container and put it back up the network doesn't reform unless i remove and readd the OTBR integration - without knowing the code, to the architecture philosophy the team has, my initial thought is it would seem like the OTBR integration should poll the OTBR rest API periodically and reform the network if needed? when i do it with ser2net the containers on HA are super reliable at reforming the network (no surprise there) |
Beta Was this translation helpful? Give feedback.
-
|
update, this has been running reliably since i impelemented, way easier than trying to bend the official OTBR container to my will |
Beta Was this translation helpful? Give feedback.
-
|
random question: why do the home assistant folks disable mdns in their OTBR add-on when it is required by the thread specification for all border routers.... |
Beta Was this translation helpful? Give feedback.
-
Can you be more specific? The OTBR add-on should announce itself using the How do you determine that mDNS is disabled in the add-on? FWIW, the OTBR add-on uses the mDNSResponder (so no AVAHI). |
Beta Was this translation helpful? Give feedback.
-
hmm, well i don't see it advertising itself and i think i confused the no AVAHI with no mDNS... hold on... |
Beta Was this translation helpful? Give feedback.
-
Just want to put that out here, especially for other folks comming here: We work hard to build exactly that, as an out-of-the-box working solution: Home Assistant OS + OpenThread Border Router add-on provides a well tested and known working platform. It is built ontop of Linux + Docker, and comes with the Supervisor (roughly HA specific "container" manager). And we seek always for contributors, as our system certainly isn't perfect 😉 That said, I do understand, there is fun and value in building something like that from scratch. Not judging, just sayin 😄 I'll answer to things/question in here in more details per answer/topic. |
Beta Was this translation helpful? Give feedback.
-
|
thanks! yes this was first about asking for help, then as i went on the fun adventure capturing what i learn, as it might help others, but it lets me get my thoughts straight too. no value judgement here on the add-on OTBR container vs this one - just want to get to something that is reliable and does what it needs to, and this thread is just a stream of conciousness, lol also happy to contribute - i already did a minor PR on docs, lol, as for code unlikely unless it is day 1 python stuff, on docker stuff - there i can help, i have containers i have created with a few pulls... and thanks for answering, i really appreciate it! |
Beta Was this translation helpful? Give feedback.
-
|
In general, from what I can tell, the container offered by this upstream project is really more meant for development/testing. The fact that by default Thread network settings are not stored shows that. That said, ideally I would like to offer a "pure" container to run a OTBR for the Home Assistant community, for those using Core container and Matter container installations. Ideally, I'd like to use that container then as base for the add-on. We have a similar setup for Matter: The python-matter-server project offers a pure container, and this pure container is then also turned into an add-on. Maybe we could even go a step further and adjust/synchronize with the upstream |
Beta Was this translation helpful? Give feedback.
-
|
I agree, that was my assessment too - designed to work with their guide on fake RCPs and devices they include on the site, no more i have some skills with docker containers, minimal to no programing skills (i can fix others basic python stuff sometimes, but not create from scratch) i will give some thought to how I can contribute. |
Beta Was this translation helpful? Give feedback.
-
Yes, development/testing was the original use case. But as adoption increases, more people are now trying to use it in real deployments.
This would be great. It would be great if we could maintain a container that targets the deployment use case. |
Beta Was this translation helpful? Give feedback.
-
|
Hoping that both of you continue development of the OTBR as a Home Assistant container. I've a similar set up as scyto in that I run HA in docker using Docker Compose via Portainer. My Zigbee2MQTT and Mosquito are all containers. The OS is Ubuntu running as a VM on baremetal ESXi. My Zigbee radios are PoE SMlights. One blocker is this OTBR in a docker. @scyto , you mentioned writing a doc. Any chance that happened? |
Beta Was this translation helpful? Give feedback.
-
|
A doc, at some point, i's basically what i documented above somewhere in a post above radio > rPi running docker > container running set2net > network > OTBR integration on home assistant configure for network mode |
Beta Was this translation helpful? Give feedback.
-
|
Which docker image did you use? The official image that's designed for testing or did you somehow get the HAOS one to run in a docker? Any chance you'd commit your docker to Github? |
Beta Was this translation helpful? Give feedback.
-
|
@scyto @agners Interesting discussion here, do you know if anyone has done any progress to create a docker image that is independent from HassOS and can be used ? I run all my things in docker containers using docker compose and would love to have OTBR in a docker container. The only solution i have now is to move HassOS but i like the control i have using docker on my own. |
Beta Was this translation helpful? Give feedback.
-
sorry no, i found the solution using the OTBR add-on in hass to be good enough - i run home assistant in a VM |
Beta Was this translation helpful? Give feedback.
-
|
Yesterday my Nabu Casa Connect ZBT-1 arrived and I naively thought that it's easy to integrate the stick with Thread into homeassistant which is also running as a docker container with docker-compose over portainer. I wouldn't by another Thread Boarder Router like Amazon Echo or a Homepod. Just use the stick in my Raspberry Pi5. I am also very interested in a docker-compose.yaml for the current OTBR to easily add the Open Thread Boarder Router Integration with a url in Home Assistant to install my e.g. Eve energy plugs and move forward to replace older devices with newer Matter over Thread devices. Is there still anybody working on a docker image that is independent from HassOS? Best regards |
Beta Was this translation helpful? Give feedback.
-
|
@randm-ch thank you for the effort and progress. I'm far as you. My stick has the same behavior, and we seem to have the exact same setup. I'm also using |
Beta Was this translation helpful? Give feedback.
-
|
@randm-ch , I think we need to get more visibility into your issue. From what I can see in the logs, things are working as expected, except for the fact that there is no Matter-related traffic flowing through the border router. One thing we can try is adding additional logs to OT mDNS to see the border router is even seeing mDNS queries for the Matter service. I just chatted with @abtink and he agreed to help add some additional logging. |
Beta Was this translation helpful? Give feedback.
-
|
Amazing, thanks for the heads up. I'm happy to test this out & provide the logging as soon as it's ready (and I have 5 minutes to spare). |
Beta Was this translation helpful? Give feedback.
-
|
Here is the PR adding verbose logging |
Beta Was this translation helpful? Give feedback.
-
|
I've tested with the new version. The outcome is the same, as expected. Here are the logs: In the meantime, I made some changes to the compose file and I now see the OTBR in my HA Thread settings. I achieved this by using The Matter/Thread containers are the same as in my previous post.
|
Beta Was this translation helpful? Give feedback.
-
|
I have this Nabu Casa Stick (ZBT-1 / SkyConnect) for a while now and just gave up because the Thread setup seemed so complicated. Now I tried it again with Docker, and somehow I guess I managed to get it nearly working. 
Any idea what could be wrong?
Can you please explain a few things to me? So this is the official guide of how to install OpenThread for Docker, right: https://openthread.io/guides/border-router/build-docker Is the topic and also the manual so new and active that environment variables are missing? I mean And what is the difference between |
Beta Was this translation helpful? Give feedback.
-
|
https://openthread.io/guides/border-router/build-docker is the latest setup guide.
|
Beta Was this translation helpful? Give feedback.
-
|
@saschabrockel could you share how you got it working? when i have my sky connected plugged into the home assistant VM using USB passtrhough the OTBR addon just says it cant connect to the RCP. When i have my skyconnect plugged into my pi this open thread container has the same issue. however if i plug the sky connect into the pi and run ser2net (to pipe serial connections over the network) the otbr addon in my hassos vm on another machine connects just fine i am at loss where to look next |
Beta Was this translation helpful? Give feedback.
-
|
@scyto I run the Docker container as following on my unRAID server: You can use https://composerize.com if you want it as docker compose. This just works for me that OpenThread runs in the container without any issues, and I can connect through Home Assistant's OpenThread integration with my host IP and the custom port |
Beta Was this translation helpful? Give feedback.
-
|
I don't know what Home Assistant requires to recognize it as a border router. If someone knows, please do tell! |
Beta Was this translation helpful? Give feedback.
-
|
@jwhui are you taling about the auto discovery of the OTBR exists by the integration? if so a quick look at the code for the integration would seem to indicate its just looking to see of the current hass OTBR add-on is added - of course what we realy need is hass to detect based on the multicast discovery packets of the OTBR - not sure if those are bonjour? if it is then it would be possible to add code to this flow |
Beta Was this translation helpful? Give feedback.
-
|
oh i already have a compose, i was looking to see if i had missed anything (i have tried with and without the &usart-init-deassert) but it results in this, its as if it cant see the skyconnect at all not this is what happens when i use the compose on pi OR if i use the add-on builtin to haso now when i expose my RCP from the same pi using a ser2net container, it works just fine!? ser2net.yaml so i know the RCP works, i know i am mapping it correctly with compose, what i don't know is why it wont locally on the pi or locally on the hasos machine, but it will work when piped over the network, makes no sense to me, not sure what i am missing and here is rhe sample output when i go hasos obty add-on > network > ser2net running on pi > skyconnect plugged into pi, works pefectly.... i am a total loss..... and here is the otbr-add having the same issue, but you can see the flasher detects the device just fine, its just otbr that can't...... |
Beta Was this translation helpful? Give feedback.
-
|
Ah, sorry, yes, it is the ZBT-1. But I still bought it as SkyConnect, which is why it still confuses me with those names. Do you have the SkyConnect attached to the same device that is running the OTBR container? I'm still confused that Home Assistant always recognizes the SkyConnect even though I don't pass through it in the Docker container. But I can't do anything with it anyway. Anyway, I think if the stick is attached to the same system that runs Home Assistant, it works. I'm not using My startup logs: |
Beta Was this translation helpful? Give feedback.
-
thanks for the detail you are not going to believe this, it is now working (of course after i emailed nabucasa support). It is one of these that fixed it:
thanks again for the help, now i can move to the next step at the weekend and help test :-) |
Beta Was this translation helpful? Give feedback.
-
|
@jwhui hi, finally got my RCP working with the container. Here is what i did so far (havent managed to commission a device)
my suspicion is this is some form of network connectivity issue (the app on the phone can't connect to the device via the border router - note a run a dual stack IPv4 env across my entire estate, i will go back and make sure that home assistant has one of my GUA i remeber from doing this in May last year that the last step was an end-2-end IPv6 connecitivty check in someway, can't recall. Here is where you can see the otbr integration and. thread inetgration see the border router just fine (do we need to keep these keys hidden?) 
Could you add ifconfig to the container image so i can query the nics etc (of if a if you prefer) |
Beta Was this translation helpful? Give feedback.
-
|
@jwhui no, i was doing the dataset command as in the formation instrucitons that had shown me what was entered, i will the dataset active command instead - off to spin up the container what does dataset active do? |
Beta Was this translation helpful? Give feedback.
-
|
In case you're curious, you can learn more about all of the dataset commands here. |
Beta Was this translation helpful? Give feedback.
-
|
@jwhui very curious, i like to try and understand things from first principles and why i am doing things - not wrote recipies, so will look I think my coinfusion was a combo of this:
so yes it reaload the dataset fine 
now i need to get my devices reliably communicating with the RCP after that i can reverify that when i configure the gateway and home assistant to be IPv4 only nothing works.... |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good. You mentioned earlier about wanting to set things like Network Name. The |
Beta Was this translation helpful? Give feedback.
-
|
thanks, was just reading up on them like https://github.com/openthread/openthread/blob/main/src/cli/README_DATASET.md#meshlocalprefix any reason not to use one of my GUA /64 prefixes and then disable NAT64? also are these things better done via the CLI rather than being exposed as container env vars or simillar? |
Beta Was this translation helpful? Give feedback.
-
|
@saschabrockel starting new answer to contain your issues look at my answer above where i went from not working and effing cofused to working (and i still may be super conused and have done the wrong things)
let me know if i can help by looking at my now working system (i am terrified of restarting the container, rofl) |
Beta Was this translation helpful? Give feedback.
-
|
@randm-ch no need to guess - HA and OTBR absolutely needs to be talking native IPv4 IPv6 (link local should be ok if the HA instance and OTBRinstances are on the same subnet) as they need to rely on boradcast and multicats packets. If one can't use host networking ojne should use macvlan for the containers. Serioulsy i know its a PITA but home assistant really only gives you all the features when it is HAOS..... I migrated from docker to HAOS because i constantly hit issues caused by this (i have a lot of integrations.....) for all sorts of home assistant functionality. It can be in a VM, doesn't have to be on a dedicated pi. I am convinced there is a bug (@jwhui ?) where mDNS is not correctlyworking on IPv4 or rather the container advertises an mDNS address with IPv4 and IPv6 but during provisioning using the iphone with only IPv4 it doesn't work - i proved this to my satisfaction by togglng IPv6 off and on on the pi and the home assistant (of course it could equally be a home assistant issue where it is notusing IPv4correctly, or i guess the iphone.... or the matter container.....way too many movin gpieces...) |
Beta Was this translation helpful? Give feedback.
-
|
@scyto , for "provisioning" I assume you mean a Matter device? Matter requires IPv6 and IPv4-only generally won't work with Matter devices. |
Beta Was this translation helpful? Give feedback.
-
|
@jwhui yes, and TIL its a requirement for matter - thanks for confirming, that eplains a lot, i suspect thats a cause of lot of issues in home labbers networks. they generally don't think about IPv6 and using things like traefik, reverse proxies, etc. its super east to break IPv6 if folks are doing things like RA suppression... i will add a note to me answer, thanks for being so helpful and responsive! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @scyto - yeah probably. I made some strides as described on this other thread, but I'm still not there. However, it's not magic after all, it must be possible configure a Linux to work like HAOS. But yeah, at this point I'm not sure it's worth the hassle. |
Beta Was this translation helpful? Give feedback.
-
|
@randm-ch you gotta make sure none of the containers, iphone, etc are going through trafeik or nginx yes it should be possible on normal linux and docker
only use nginx/traefik for things coming from out side of your firewall (e.g. internet) as to worth trrying? if it were me and i am on a hypervisor that supports hardware pass through i would backup my home assistant config, shut down the home assitant container, startup a home assitant VM and import my config - takes 10 minutes, and never look back :-) practicl overrides 'elegant' or they 'way the cool kids do it' - also why i long ago abandoned traefik and handcrafted ngix for NPM its not like the VM needs to be large 
this. runs all these addons too
|
Beta Was this translation helpful? Give feedback.
-
|
@jwhui interesting, i set up a new network name, and it is being broadcast (fyi home assistant has an mDNS browser built into it :-) 
but home assistant doesn't pick up the change (even after removing and re-adding all integrations - will try reboot) FYI only as you don't have anything to do witn home assistant (afaik?) |
Beta Was this translation helpful? Give feedback.
-
|
ahh i see what is going on, that dataset above is one created by home assistant (starts ha) and as such it expects to manage the name and so assumes the name, so it must be maintaining state even when the integration is deleted (tsk tsk) so i created a new dataset with my name, then committed that and then i could add the one with the name i want to home assistant 
would be nice if there was a vendor name string :-) |
Beta Was this translation helpful? Give feedback.
-
|
Ok 2025.09.11 Answer Key Requirements
My setup is:
The docker compose on the pi: Sequence of fresh install (assumes home assistant OS is installed - not docker or supervised)
Note: Troubleshooting commissioning:
|
Beta Was this translation helpful? Give feedback.
-
|
For the record, I got HA, otbr and matter-server working in docker with the folowing docker-compose : This way thread is discovered by HA throuh mDNS, OTBR integration need to be configured with |
Beta Was this translation helpful? Give feedback.
-
|
@saschabrockel for your reference I managed to make it work with the docker-compose I'm attaching. Make sure you follow the instructions at https://openthread.io/guides/border-router/ including sections prepare, setup and form thread network. My problem was that I was using enp1s0 as a network interface and that was incorrect, since I had Cockipt installed I had to use bridge0, both in sysctl configurations and in the OT_INFRA_IF variable. services:
home-assistant:
container_name: home-assistant
image: ghcr.io/home-assistant/home-assistant:stable
restart: unless-stopped
network_mode: host
privileged: true
devices:
- /dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_8ada55c87bd9ee11b980b24c37b89984-if00-port0:/dev/ttyUSB0
volumes:
- /srv/docker/home-assistant:/config
- /etc/localtime:/etc/localtime:ro
- /run/dbus:/run/dbus:ro
matter-server:
container_name: matter-server
image: ghcr.io/home-assistant-libs/python-matter-server:stable
restart: unless-stopped
network_mode: host
security_opt:
- apparmor:unconfined
volumes:
- /srv/docker/matter-server:/data
- /run/dbus:/run/dbus:ro
border-router:
container_name: border-router
image: openthread/border-router:latest
restart: unless-stopped
network_mode: host
cap_add:
- NET_ADMIN
environment:
OT_RCP_DEVICE: "spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800&uart-flow-control"
OT_INFRA_IF: bridge0
OT_THREAD_IF: wpan0
OT_REST_LISTEN_ADDR: "0.0.0.0"
OT_REST_LISTEN_PORT: "8081"
OT_LOG_LEVEL: 7
devices:
- /dev/net/tun
- /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_1cec7151a89ced11abfa7dfaa7669f5d-if00-port0:/dev/ttyUSB0
volumes:
- /srv/docker/border-router/:/data |
Beta Was this translation helpful? Give feedback.
-
|
@mnllrnz, that was never a problem. The problem starts with the Thread integration in Home Assistant for me. It looks like this: |
Beta Was this translation helpful? Give feedback.
-
|
Hey I saw you are using a SMlight SLZB-06M, do you connect it with USB or ethernet and PoE? |
Beta Was this translation helpful? Give feedback.
-
|
You need to connect both : https://smlight.tech/manual/slzb-06/guide/thread-matter/ |
Beta Was this translation helpful? Give feedback.
-
I see, so Ethernet only won't work with OTBR, kinda sad when we have a PoE device that is flexible on location. |
Beta Was this translation helpful? Give feedback.
-
|
That's the same problem I was facing, and it was caused by the otbr not advertising correctly to the network, so that's why I suggested these potential solutions.
What netdata and meshcop show? Is everything working there?
…On Thu, Oct 2, 2025, at 22:39, Sascha Brockel wrote:
@mnllrnz <https://github.com/mnllrnz>, that was never a problem. The problem starts with the Thread integration in Home Assistant for me. It looks like this:
image.png (view on web) <https://github.com/user-attachments/assets/78a975ff-eff2-4d87-bc48-4e45beca67b1>
—
Reply to this email directly, view it on GitHub <#10311 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCLYHV7MGMOMI4MKDOXIBED3VWEQ5AVCNFSM6AAAAABIQEDXA2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINJXG44DSNQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Can you tell me how to check this? I heard several times here about these tools, but don't know where to get them or how to use them. |
Beta Was this translation helpful? Give feedback.
-
|
I have a similar setup running docker on an ubuntu host with a Sonoff Zigbee 3.0 USB Dongle Plus–ZBDongle-E plugged in. I am trying to add a XIAO MG24 as Matter / Thread device as described here. I took these steps:
settings
set these in /etc/sysctl.conf: Then run I'm unsure if this is correct, as this script from this guide says
docker-compose.yaml
services:
homeassistant:
container_name: homeassistant
image: "ghcr.io/home-assistant/home-assistant:stable"
volumes:
- /home/daniel/homeassistant/config:/config
- /etc/localtime:/etc/localtime:ro
- /run/dbus:/run/dbus:ro
restart: unless-stopped
privileged: true
network_mode: host
otbr:
container_name: otbr
image: openthread/border-router:latest
restart: unless-stopped
network_mode: host
cap_add:
- NET_ADMIN
environment:
OT_RCP_DEVICE: "spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800"
AUTOFLASH_FIRMWARE: 0
OT_INFRA_IF: enp1s0
OT_THREAD_IF: wpan0
OT_LOG_LEVEL: 7
OT_REST_LISTEN_ADDR: "0.0.0.0"
OT_REST_LISTEN_PORT: 8081
devices:
- /dev/ttyUSB0:/dev/ttyUSB0
- /dev/net/tun:/dev/net/tun
volumes:
- /etc/localtime:/etc/localtime:ro
- /home/daniel/otbr/thread:/data
# see https://github.com/matter-js/python-matter-server/blob/main/docs/docker.md
matter-server:
image: ghcr.io/home-assistant-libs/python-matter-server:stable
container_name: matter-server
restart: unless-stopped
# Required for mDNS to work correctly
network_mode: host
security_opt:
# Needed for Bluetooth via dbus
- apparmor:unconfined
volumes:
- /home/daniel/matter-server/data:/data/
- /etc/localtime:/etc/localtime:ro
# Required for Bluetooth via D-Bus
- /run/dbus:/run/dbus:ro
command: --storage-path /data --paa-root-cert-dir /data/credentials --bluetooth-adapter 0 --log-level verbose
I cannot see any obvious errors in the logs of the otbr or the matter-server containers. IPv6 and mDNS generally seem to work in my local network, I think otherwise I would have failed earlier in the process of setting up the integrations. My phone is connected to the same network. So I guess it's either a IPv6 problem or a problem with the device I am trying to connect (unfortunately I don't have another device). Does anyone have tips? |
Beta Was this translation helpful? Give feedback.
-
|
Got this sh*t working now! Holy crab. I don't know why or how, but I also set What I learned:
Pretty sure @mnllrnz gave me the last hint. I had set the sysctl setting to br0 even before, but I used OT_INFRA_IF with |
Beta Was this translation helpful? Give feedback.
-
|
@saschabrockel I am happy that worked. @daniel17903 everything you listed looks good. I have heard that sometimes devices fail to connect but after a reboot they work. I imagine you already tried that. I suggest you follow the checks on the OTBR instructions: ifconfig wpan0
docker exec -it otbr ot-ctl
netdata show
ping 8.8.8.8To see if everything is up and you have connectivity. |
Beta Was this translation helpful? Give feedback.
-
I think everything looks good: > netdata show
Prefixes:
fd1e:ae78:952f:1::/64 paros low ec00
Routes:
::/0 s med ec00
fd1e:ae78:952f:2:0:0::/96 sn low ec00
Services:
44970 01 7c000500000e10 s ec00 0
44970 5d fdad64595a8dca640ab3fef20308f3d6d122 s ec00 1
Contexts:
fd1e:ae78:952f:1::/64 1 sc
Commissioning:
25772 - - -
Done
> ping 8.8.8.8
Pinging synthesized IPv6 address: fd1e:ae78:952f:2:0:0:808:808
16 bytes from fd1e:ae78:952f:2:0:0:808:808: icmp_seq=1 hlim=118 time=17ms
1 packets transmitted, 1 packets received. Packet loss = 0.0%. Round-trip min/avg/max = 17/17.000/17 ms.
Done
ip addr show wpan0
23: wpan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UNKNOWN group default qlen 500
link/none
inet6 fdad:6459:5a8d:ca64:0:ff:fe00:fc11/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fd1e:ae78:952f:1:f982:6e6d:cbc6:fdac/64 scope global nodad
valid_lft forever preferred_lft forever
inet6 fdad:6459:5a8d:ca64:0:ff:fe00:fc38/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fdad:6459:5a8d:ca64:0:ff:fe00:fc10/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fdad:6459:5a8d:ca64:0:ff:fe00:fc00/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fdad:6459:5a8d:ca64:0:ff:fe00:ec00/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fdad:6459:5a8d:ca64:ab3:fef2:308:f3d6/64 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fe80::d05a:db4b:66d3:394b/64 scope link nodad deprecated
valid_lft forever preferred_lft 0secI suspect the problem might be the device I try to connect. Edit: It's not the device, when using an Aqara Hub M100 as Thread Border Router instead it works. |
Beta Was this translation helpful? Give feedback.
-
|
Everything looks good there. If you share your otbr container logs we can try to see what is happening there. |
Beta Was this translation helpful? Give feedback.
-
|
Hi all. With your help I managed to get my OTBR on Unraid to run and I can´t strech enough how thankfull I am. Do you have an idea what I can do to fix this? |
Beta Was this translation helpful? Give feedback.
-
|
Looks like something in HA looses track of external OTBR as it's mentioned in several issues (see home-assistant/core#138084 and home-assistant/core#131669 for exemple but there are more on their issue tracker). I ran into this same issue myself and I also found out this doesn't seems to be a problem unless I'm trying to commission a new device, then I can get my OTBR to show up for sometime by restarting my OTBR container and then it disapears again after 10min or so. |
Beta Was this translation helpful? Give feedback.
-
|
one point of note, i notice that comissioning on matter by default has a 10 minute time out, i saw the same thing on a matter over wifi issue with the tommy integration i was about to see if i had the same issue you note above but just found my rPi has failed.... awesome! |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone, this is my Docker stack, but I can't connect devices via the HA Companion app. (After a while the pairing on my companion responds with "unable to reach the device") IPv6 is enabled correctly. I tried installing HAOS on another PC and was able to add the devices successfully. I'm probably doing something wrong in the configuration or there are network issues. Can you help me? Thanks! services:
matter-server:
|
Beta Was this translation helpful? Give feedback.
Ok 2025.09.11 Answer
Key Requirements