Blatantly wrong results
The app detected my Homebridge instance (running on a Linux server with only Ethernet connectivity) as a Thread border router. I have no idea how badly you have to mess up to get this kind of result, so I didn’t think it was even worth my time to look at the rest of the “mapping”.
Response from developer
You're right, and thank you for saying so plainly. Up to version 1.8, ThreadMapper counted any accessory Apple Home lists as a bridge as a Thread border router, and Homebridge presents itself to Apple Home as a bridge. That was wrong. In 1.9 a border router is shown only when it announces itself as one on your network, a bridge is shown as a bridge, and the map draws only links your devices actually report. If you try 1.9 and anything still looks wrong, please tell us through the Support link on this page.
