[HOW-TO][Pro][Cloud] - Zigbee Route map (Homey Pro / Homey SHS / Homey Bridge)

I’ll have to check the external viewers, but I don’t want to add anything to different applications. Home Assistant would als work for this, as it has some sort of mesh viewer (which I saw online).

I think it is clear already, but there is no way possible to get the mesh data from a 2023 Homey. As the data is not actually there?

Let’s just say that other platforms using the same chip are able to generate network maps :man_shrugging:t3:

@Doekse Perhaps Athom could develop their own visual network maps and integrate that into Dashboards? I’m sure Emile has considered it, but other features have taken priority.

What an amazing way for Homey to stand out from HA

They are not, at least they are not being processed or stored by Homey anywhere (not even on low level).

So …

Zigbee

  • Adds endpoint for viewing source route table.

So now it works also on Homey 2023&6 … :+1:

Yes! Just updated the top post to support the new platform too

Hi Martijn, I tried your Zigbee mesh map script on my Homey Pro 2026 (now that it also shows the Zigbee routes in v13.2.1), but it does not seem to work. The script completes and I do get a (very long, more than 100 lines) URL as a result. But it seems the URL is capped. I would assume it to end with a double quote, but instead I see the following strange character at the end of the URL:

Any idea what could be the cause and how to tackle it?

@SunBeech can you check in the developer tools of your browser to see if it logs it there?

I got it to work by running the script on my laptop (in Chrome) instead of on my tablet (also in Chrome). Really cool result! :blush: :+1:

One question: I have 2 (battery powered) Zigbee devices for which no route info is available (currently). In Homey Developer Tools their route is displayed as a question mark:

Your script connects those two devices directly to Homey/the coordinator. Is that the actual route, or does your script connect every device that does not have route info to the coordinator as a fall back?

@SunBeech yes it’s a fallback. Otherwise the script can’t map it

Okay clear. One final thing I noted when opening the console in Chrome. It shows the following error, though the URL and map is generated:

@SunBeech yes that;s a error coming from Homey WebAPI. FYI @Doekse