A way to see all Thread IPv6 addresses in a list rather than click each one?

Configuration Matter/Thread
, ,
1

I frequently diagnose issues with my Matter-over-Thread devices via the logs, and usually the only clear indicator is the IP. For instance, if I see
fd4f:9a0d:b4e5:1:68da:1db5:632c:f63a
in my log, I can then find the device in the Details of each device by matching it to

image
image932×948 51.7 KB

If I see that a new device is trying to connect to that node and failing, I then know how to physically troubleshoot instead of sitting around wondering why it doesn’t connect.

The trouble with this is that it’s a huge pain to get each IP address individually. Is there a way I can just have a list or table, similar to the default Device list, with each IP next to each device name? The data obviously exists, but I don’t know how to grab it and display it beyond opening each damn device page.

It would be great if I could just CTRL+F.

2

Settings > System > Network > zeroconf browser > _matter._tcp.local.

Mesh-Local have prefixes of fd00::/8 .

2 Likes
3

Helpful, thanks! What I really want is a single view that shows me the name of the device next to it’s IP. Zeroconf shows me this:

image
image2916×624 25.5 KB

In this example, the zeroconf browser suggests 2 devices have the same IP. Is there a view or dashboard I can set up that merges the data? Then I could figure out why.

4

You can use, notepad, excel or AI to do this. Hubitat also has a good view to show this.

5

I mean, the data is all in Home Assistant. I just don’t know how to connect it. Surely there is a way to pull the data from two places into a single view using Dashboards or something?

6

like using AI? If you are right, it should give you the needed YAML for your own dashboard.

7

Google was my first stop, and it recommends a lot of things that don’t make sense. I tried making Dashboard views with Gemini for a while but none of them worked and after a while it started recommending I add the custom repository “github.com” for HACS, at which point I gave up.

8

What you’re looking for isn’t possible at the moment.

9

Wow, I’m surprised. What’s the obstacle? Genuinely curious. If the UI can pull the data for a device from one place and another, I would assume a script could unify them.

10

there is no obstacle, it’s just not in the software

11

What? But it is in the software. If I can see this on one page:

image
image932×948 51.7 KB

and this in another page:

image
image1380×294 19.7 KB

then I know that’s the same device. What’s to stop a script from putting the name of the device (“ALPSTUGA air quality monitor (12289)”) next to the IP in a list?

I mean, it literally exists on each device page, I just don’t want to have to open 100 devices one by one to find the IP my log is yelling about.

Hell, I’d open a config or storage file and CTRL+F there if I knew where to look.

12

It’s not in the software in a list. There is no reason why it’s that way, it just hasn’t been done.

13

It can. if you are comfortable-ish with python you can tell AI to create a python script to pull it from the python-matter-server over the servers WS connection.
You’ll get something like this
{
“node_id”: 18,
“name”: “Eve Energy 20EBU4101”,
“ipv6”: [
“fe80::38ef:aaaa:f2fa:bbbb”,
“fdb8:855e:aaaa:0:549f:51fd:f37e:bbbb”,
“fdee:4244:aaaa:1:306:e069:a1a4:bbbb”
]
},

I used claude. if its important to you, i would recommend the same, so you understand all it entails.