#Thread UI

1 messages · Page 1 of 1 (latest)

potent walrus
#

I am running the Open Thread Border Router container (not the add-on) but the web ui doesn't really work when I try to look at details about my thread network. Integrations with HA work fine, and I can even use the CLI to get details about the network, but was wondering if there was some alternate UI for Thread networks out there (not impressed with what I have seen so far with what was incuded with the OTBR).

potent walrus
#

Seems the javascript is trying to access a wrong port in the OTBR UI

feral heath
#

otbr uses two ports, one for the ui and one for the api. some operations in the ui will make requests to the api port.

#

it's likely that a better otbr visualization/monitor will end up be built into home asistant itself at some point, interacting with otbr via its api.

potent walrus
#

Yah seems the rest api might be inaccessable or the port isn't set properly

potent walrus
#

Wow, finally got the topology page working it working and it's horrible. Really hope someone comes up with an alternative... the Z2m UI is so great compared to this

#

I wish I knew more about thread networks, I'm sure I could come up with something in a few days of work

feral heath
#

If you want to play around with the available data a bit, assuming you've enabled the rest api port, http://homeassistant.local:8081/diagnostics will dump a bunch of interesting information as json. (note that the api endpoint and data format is expected to change when the otbr addon is updated to thread 1.4)

#

it's also possible to run ot-ctl inside the container and it has some useful diagnostic commands. Start by running debug which will just dump out everything the otbr knows :)

potent walrus
#

Yah, I have been using ot-ctl and it meets my needs, but just discouraged by the discrepency of how polished Zigbee infrastructure is compared to Thread... although I did have to reboot just now because of failing Zigbee infra 🤷