Repository navigation
Openthread-BR #1652
Description
Name of the Script
Openthread-BR
Script Type
CT (LXC Container)
📋 Script Details
Application
Name: Open Thread Border Router
Website: https://openthread.io/guides/border-router
Description
Will be abble to manage the thread part separatly from home assistant
Activity
[-]Openthread Border Router[/-][+] Openthread-BR[/+][-] Openthread-BR[/-][+]Openthread-BR[/+]github-actions commentedon Mar 30, 2026
The openthread-br script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/openthread-br.sh)"Requires a Thread Radio Co-Processor (RCP) USB device passed through to the LXC container (e.g. /dev/ttyACM0). Edit /etc/default/otbr-agent to configure the RCP device path.
This container runs in privileged mode for network administration (iptables, ipset, tun device access).
Services are not started automatically on first boot. Connect your RCP device, configure /etc/default/otbr-agent, then run: systemctl start otbr-agent && systemctl start otbr-web
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
hiSweid commentedon Mar 31, 2026
Thank you for the great script! I'm trying to set up a network-based Thread adapter (SMLIGHT SLZB-MR3 via TCP).
Simply changing the config to OTBR_AGENT_OPTS="-I wpan0 -B eth0 spinel+socket://192.168.111.4:6638" doesn't work and causes the otbr-agent to exit silently. Are there any plans to natively support network adapters like the SMLIGHT in this script, or is there a recommended workaround?
r4h1mfr commentedon Mar 31, 2026
Hello, i have just tried it also, and having the same problem. I'm using a SMLIGHT SLZB-MR1U via tcp also. I don't use a usb device. The same happened with a SMLIGHT SLZB-06M
MickLesk commentedon Mar 31, 2026
Can you try privileged?
Is there any issue in the systemctl Services? journalctl -u ?
22 remaining items
r4h1mfr commentedon Apr 5, 2026
Hi Again,
It's working fine now !
PsychoRS commentedon Apr 5, 2026
Perfect!
github-actions commentedon Apr 5, 2026
A PR has been created for openthread-br: community-scripts/ProxmoxVE#13536
tomfrenzel commentedon Apr 16, 2026
Hi @hiSweid! Since i know you're also using a SMLight Network Thread Dongle i wanted to know if you're also experiencing those two issues i'm having with the LXC:
otbr-agentstarted (for me it takes about 30min to 2h) the agent service gets in a loop causing one core to max out at 100%. At that point i can only restart the service to get it down again.As i didn't have that issue with the HA Addon and nobody in the ot-br-posix repo reported such error, i thought it might have something to do with how the community script build / configures the agent.
As opposed to what the script default is, i created the LXC unprivileged since i don't need to pass through any USB Device. Maybe that could also play a role.
MickLesk commentedon Apr 16, 2026
Then find out? 😄 If you're already in touch with the community or the devs, our source code isn't a secret. As I've said from the start, these are tools we can't test because we don't have a use case or the hardware for that. If you know more, create a task in ProxmoxVE with the optimizations. It's already done here because it's been migrated
PS: "Docker-only" is no excuse
tomfrenzel commentedon Apr 16, 2026
I already spend a couple hours trying to narrow down the problem but haven't found the root cause yet. I found workarounds for both problems but both would need code changes in the ot-ber-posix repo. I'm not happy with that 😆 Since im not 100% sure if (at least the 2nd issue) originates from my setup as a whole (HA + other Border Routers) or this script, i wanted to check with @hiSweid before opening an issue in VE and trying to fix it in the script.
Of course, i just mentioned that since that made me think the issue comes from the way the script installed tha agent and not from my Thread/HA setup as a whole.
Should i create an issue in VE anyway to track those issues in case somebody else runs into them as well?
hiSweid commentedon Apr 16, 2026
hey, i can confirm your issue, i solved it with a restart, so every day it restarts like 10 times. thats not the solution :) but worked for me and my matter over thread devices. Please create a issue :)