I found a very light weight Thread network visualizer, try it

Configuration Matter/Thread
1

I (or rather Google) found a very lightweight Thread network visualizer. It is a web app. Actually, just a static eab page. Host it on any computer, even on your Open Thread Border Router. The app will use OTBR’s rest API to query the routing table and “crawl” the Thread network. It then creates a graphic of the topology.

There is a backup method to be used if your border router lacks the web GUI, where you manually capture output from OTBR’s CLI. I could only get this backup method to work even though I have a functional web GUI enabled.

I suspect the author of this code never tested it with Expressif’s FreeRTOS port of OTBR, as most people run OTBR on Linux.

It is very easy to set up and use.

My plan is to add this to a border router so I can see the network topology by clicking http://router-ip4-address/NetTopology.html

1 Like
2

I am using the OTBR addon and there is a toplogy button in the web gui that shows the network, but its very flakey and doesnt show all devices.

If I use the visualiser code you’ve posted, I just get an error:-

app.js:164 Error: Could not find RLOC16 in API response. Check console.
    at HTMLButtonElement.startDiscovery (app.js:150:23)
startDiscovery	@	app.js:164

Seems this is a known issue:-

3

Thanks for the info … I had played with the REST API shortly after the HA OTBR Beta App/Addon came out and could only get one node’s worth of data (the OTBR node itself). Figured I was missing something, so gave this visualizer a try, and it too can only get one node’s worth. OTBR Log is saying Failed to get diagnostic data: ResponseTimeout. I’m kinda guessing here, but I suspect that the HA OTBR Beta has not yet pulled in an upstream release that contains more of the finished API code (but again just a guess).

On the other hand, the “CLI Import” seems to work pretty well!! :slight_smile:
Was also able to use the device_names.json to start renaming some of the nodes too… NICE!