Identify devices shown in Thread Tools

Thread Tools displays devices with RLOC16 values.

I’ve tried using Homey Developer Tools to determine/lookup RLOC16 values of the devices I have to no avail.

I need a helping hand in identifying the devices.

There are three dots at the right of the list shown by the matter option in the developer tools. The options give you RLOC16 values. The free phone-based Thread Network Diagnostics app also shows RLOC16 ids and MAC addresses.

Andy

Thanks, Andy.

I am using Thread Network Diagnostics. It shows me all the devices on my thread network but every device is identified by a RLOC16 #. I need to map this RLOC16 # to a device such as the Grillplats in my my living room, etc. I tried to look up RLOC # using Homey Developer Tool but I don’t know how to do so.

Nonetheless, I clicked on three dots to the right of a device on “Homey Developer Tools”, I see what’s in the screenshot below. I then selected “Thread Network Information” and was presented a bunch of information. Among the information are “Neighbor Table” and “Route Table”. I presume all the nodes in “Neighbor Table” are the other nodes this device has connection to. So where is the RLOC16 value of “this” device that I am looking at?

Pick another device and see which code appears/disappears from the neighbour table.

Andy

With 2 devices, the approach is sound. As the number of devices increases, so does the number of “paths” between the devices, not so sure if this approach is still possible, not to mention that it’s error-prone.

Is there no better way?

@Doekse since you have also been very involved with that other Matter issue thread and this tool has come up there quite often as well. I think it would be an improvement to show the same RLOC id in the developer tools as well. This is a real pain point when troubleshooting Thread issues for devices.

I’m using the Android version. Clicking a device and then the ‘Network’ tab shows an entry labelled ML-ED under IPv6 address list. For me, this maps to IP address in the nodes list shown by the developer tools.

Andy

I’m on Android as well. By the way, Thread Network Diagnostics has been superseded by Thread Tool which is what I’m currently using.

I observed on Thread Tool that

  1. Network tab of Sleepy End Device doesn’t display any ML-EID.
  2. Network tab of Extender as well as Border Router can have multiple ML-EID.

I have an idea from what you suggested earlier. I’ll remove each device, starting from a Sleepy End Device to a Border Router to see which device disappears from the topology to identify the device, a very laborious exercise indeed. I wonder if these RLOC16 values stay static following a restart of any device, be it Sleepy End Device, Extender, and/or Border Router.