I followed this guide to setup my sky connect as a thread board router Home Assistant Connect ZBT-1
I can see the device but the integration isn’t set up. It is asking for a URL but I’m not sure we’re to find it?
I have read in a few places that it is http://homeassistant.local:8081 but I already have something else running on that port.
Go to your OpenThread Border Router addon and select the configuration page and then click the Show disabled ports.
Now change the port to something else, save and restart the addon.
Excellent thank you
I’m curious too, I don’t get why it’s such a hidden thing. Like I flashed the stick with the Thread firmware manually on the website, now when I add the integration it asks for a url? Huh??
The URL is not a hidden thing. The URL is what your Thread dongle is set up to use.
Since that can be individually configured, then it is impossible to say what it is.
If you have connected USB dongle directly to HAOS/HA Supervised, then the serial port should be enough.
Using the OTBR AddOn (on HAOS) as the example, what generally happens, is the OTBR AddOn boots up and sends discovery information to the HA OTBR Integration.
From the OTBR AddOn Log:
[13:15:56] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
Through magical means through various HA Integrations, this is indeed hidden to the user, and the OTBR Integration is suppose to also auto-discover the URL without having to have user tell it.
This URL is what the OTBR Integration uses to talk to the OTBR AddOn’s REST API port. For the OTBR AddOn, this is normally:http://core-openthread-border-router:8081. If you goto the OTBR AddOn’s Info web page you’ll see there is a “hostname” core-openthread-border-router. It is this hostname that is used in the URL. BTW, if you are using multiprotocol (which is no longer recommended) it would be: core-silabs-multiprotocol:8081.
If your OTBR Integration is popping up a box asking you to supply a URL, it is probably because it didn’t auto-discover a URL, or whatever URL it has it tried to contact the OTBR but it failed. The main purpose of having to manually enter a URL is for cases where someone has rolled their own OTBR.
I can’t access the Web UI.
I checked the settings of the Open thread Web Port and it was empty. Changed it to 8055.
But still it is not possible to access it via home-assistant-ip:8055
Assuming home-assistant-ip is the Network name of your HA system (i.e. you have renamed it from home-assistant), then add .local to that name …
With home-assistant-ip I meant the IP address. But it also does not work with the DNS name homeassistant.local:8055. DNS works for home assistant of course.
Do i also need to set a Port for the REST API?
I would set the Web port to 8080.
Then, if you have the Advanced SSH & Web terminal, type in:
netstat -an | grep 8080. If it returns empty, then it means there is no socket (i.e. no server) opened to listen on 8080.
Probably not, but I set mine to 8081.
It works now after setting also a port for the rest API
Hello to all
I’m trying to configre the Thread on the HA using the smlight-slzb-mr1, but when I go to the integration thread open border router is asking to enter a URL
I already try several URLS like:
homeassistant.local
homeassistant-2.local
Without sucess for now I also try to use the solution present in this forum configuring the ports but I still facing the same issue…
Can some one please help me in order to solve this issue?
Thank in advance for nay help
Best regards
What type of installation for HA do you have (ex HAOS based)?
Is the OTBR AddOn actually running?
Hello Is is based on the HAOS and the OTBR AddOn is running
Tks
For an HAOS based installation, see my comment #7 above.
My only suggestion is to check the OTBR AddOn logs and make sure that it is actually running (i.e. has not stopped). If you think it is running, then I can only start guessing, and my only guess is that you have some other AddOn using the 8080/8081 ports, so would suggest you pick something else like 8090 and 8091 respectively and configure this into the OTBR AddOn and then use the 8091 in the URL settings.
