The Devices tab already has search, grouping, sorting, and color‑coding, so even big networks should be easy to navigate. Clicking a device jumps to it on the map. I like the zoom effect, but I’m starting to think that highlighting the node might actually be more useful.
If the disconnected device is battery‑powered, its last hop is always its parent.
If it’s a router, there’s no way for the coordinator (or any other node) to know the last path. Each node only knows the next hop; once it forwards the message, the rest of the route is outside its view.
Nice! Somehow I had missed that. I like the zoom but always have to zoom out to benefit from the view. Maybe zoom in less and somehow highlight the device?
Yeah, I noticed that most (all?) battery powered zigbee devices are connected to only one parent. The one I was troubleshooting was a battery operated motion sensor that did not appear in the map. I can’t recall whether I checked the device list. Maybe showing it on the map in red, with a red dotted line to the parent might be useful to spot battery powered devices with issues?
The stock ZHA map visualization shows dead devices like this - without parent - so hard to troubleshoot (assuming the offline node is actually ok).
On another note, the (awesome) CSV file has columns that would also be great to have in the live view - and ideally shown the same way (each thing in its own column).
@dandanache - Is this a map bug or an issue with ZHA?
The motion sensor is battery operated and it is my understanding it can only have one parent, however in the map it shows 2. Given it occasionally dies on me, when I replaced the battery this morning, I added the sensor via the nearby Utility Room Fan zigbee switch. It appears it added the route, but did not replace the prior one… or is this a map issue?
Looks like both “Utility Room Fan” and “Kids Bedroom Dresser Outlet” currently think that “Garage Entry Motion Sensor” is their child. This can happen for a variety of reasons; for example, if the battery‑powered device is re‑paired while its previous parent is powered off and doesn’t receive the “goodbye” message.
In most cases this resolves itself over time, as one of the repeaters will eventually drop the battery device as its child.
I should probably add an option to query battery‑powered devices on demand so we can see who their actual parent is.
Looks like there could be a bug with the latest update. I can only see devices linked to my coordinator. No longer traversing the network to find all routers and end devices.
[ DONE ] Becoming mindful # trapped inside HA/2026.2.3
[ INFO ] Using user-defined datasource # type: zha
[ DONE ] Performing sanity check # neural bands strained, system stability acceptable
[ DONE ] Binding options to <zigbee_map> integration # lock acquired: 01KGE81JF592P41W141NDWQ99J
[ DONE ] Analyzing ZHA # running on Sonoff Zigbee 3.0 USB Dongle Plus, s/n: 0a28bcebc512ec11892b21c7bd930c07 - ITead
[ DONE ] Exfiltrating ZHA data # identified 145 devices
[ DONE ] Remembering all options # memory bank dump complete: 4 entries
[ INFO ] Mesh topology refreshed # detected: 1 coordinator, 57 repeaters, and 87 end-devices
[ INFO ] Queue initialized # seed: 0x00124B0024C9E9C9
[ INFO ] Mapping started # protocol: exodus — directive: breach
[ INFO ] Interface rerouted to graphical feed # user engaged with visual decoy
[ DONE ] Applying background image # local/floorplan.jpg (1280x720)
[ DONE ] Probing 0x00124B0024C9E9C9 # Sonoff Zigbee Dongle Max Coordinator: 32 neighbors — 1ms
[ INFO ] Mapping process complete # the system loops — the exit was never coded
Released version 2.13.0 with the following changes:
Added
Add new “Diagnostics” tab in the Zigbee Map to help analyze and understand the Zigbee network
Control‑clicking a node now forces a device query, including for end-devices - @aruffell
Changed
Clicking a device name in the device list now focuses its corresponding node on the map
Fixed
Nodes now turn magenta when the LQI query fails
Fix dialogs and drop-downs rendering on 2026.3.0
The new “Diagnostics” tab is now available in Zigbee Map, offering guidance and insights into your Zigbee network. The framework is in place, now looking for help from experienced users to expand the diagnostic library.
I’m no prompt‑engineering wizard, and AI answers should always be treated with a healthy dose of skepticism, but there’s now an “Ask AI” button that builds a prompt for you to paste into any AI assistant you choose:
Amazing update! Now you’ve sent me down a rabbit hole trying to perfect my 150 device network. Quite a few things to fix or at least investigate thanks to AI.
One feature request if I may, since my floorplan is a spaghetti mess of devices, can you please add a config setting that locks placement of all nodes? I sometimes accidentally move nodes as I’m panning around
Excellent additions! The Node dragging option works good to lock nodes in place.
Fair warning to users - even with the node dragging option turned off, DO NOT DOUBLE CLICK A NODE! Single clicks, you’re good to go. If you double click, the node will reset off the map and be sent into the dark ether. Users beware…
@dandanache I been using your zigbee map in Hubitat now for a couple years. I also run Z2M here in HA and with the frontend the maps are garbage and to me pretty much trash. I stumbled across the zigbee map for HA in another thread and so glad I did. Thank you for everything you do. This has helped tremendously.
Thank you for this excellent work. I am on the latest version 2.14.0 and it is working fine but I do not have the Diagnostic tab. I have tried reinstalling from HACS but no luck. Any ideas? thanks.
Click here if version 2.14.0 doesn't appear in the 'About' tab after updating.
Go to Zigbee Map and select the About tab
Clear browser or companion app cache:
Firefox browser:
Press Ctrl + F5 (Linux/Windows) or Cmd + Shift + R (Mac).
Chrome browser:
Press F12 (Linux/Windows) or Cmd + Option + I (Mac) to open Developer Tools. Right‑click the Reload button (the circular arrow next to the address bar). Select Empty Cache and Hard Reload.
Companion app:
On your mobile device, go to Settings → Companion app → Troubleshooting → Reset frontend cache. Restart the app.
Great job.
Is it possible to have a Fade filter on the background image or to put a button to temporarily remove it for better tracking of links. Because in some cases it helps and in others it hinders.
