Buttons (Map Devices Options About Console) seem to have stopped working for me on the 2025.10.0 core release. Tried both Firefox and Chrome.
3 Likes
You are right, same for me. Iâll see what I can do.
2 Likes
Released version 1.1.1 with the following small fix:
Fixed
- Fix tabs rendering on
2025.10.0- @tom_l
Fix is not backwards compatible with older HA core versions, so donât update if it ainât broke 
Have fun!
3 Likes
Zigbee maps help a lot.
Thank you.
1 Like
Just discovered this add-on from a search and I look forward to trying it out. I have it installed and it seems to be correct, but it fails when starting:
[ FAIL ] Injecting extension into Zigbee2MQTT # timeout: 10000ms â trace: 9aef7c0b-7bab-46a0-ae2d-a17e361a57e4
I read you said a requirement is HAOS, which means not in a container. I am running it supervised on a Debian host, so I think my instance qualifies as HAOS in a virtual machine, but maybe I am incorrect in my assumption? Is my instance doomed to fail or is there something else I can try?
Thanks for your efforts and any assistance you may be able to offer.
1 Like
Can you see the devices list in the Devices tab? Otherwise I am afraid that the app cannot properly communicate with Z2M.
The app talks to Z2M through the same websocket that the Z2M frontend is using. When installed as an addon, HAOS exposes this websocket on the same âdomainâ and also takes care of the websocket authentication part.
I donât know much about this setup, and unfortunately I cannot test it. Sorry I cannot be of much help.
Add-ons are always in Docker containers.
While you have a supervisor container you do not have Home Assistant OS. You have Debian OS. So whatever dependencies this add-on uses from HA OS are likely missing in your Debian OS.
Supervised is a depreciated installation type and will be unsupported next month.
As a user of this advanced install type you are expected to be able to resolve dependency issues yourself. If this seems like a daunting task then it might be time to consider moving to either a Container or HAOS installation.
HA OS in a VM is also supported installation type. This is another option. See Alternative - Home Assistant
1 Like
I cannot. I tested whether it might be that my supervised HA installation on Debian might be the problem by installing a fresh HAOS VM following the official instructions, but the same problem occurs. Iâll keep investigating.
Thanks
1 Like
donât work:
- [ DONE ] Becoming mindful # trapped inside HA/2025.10.4
- [ DONE ] Probing system Supervisor # scan complete: 11 addons detected
- [ DONE ] Analyzing Zigbee2MQTT # binding slug confirmed: 45df7312_zigbee2mqtt/2.6.3-1
- [ DONE ] Tracing ingress tunnel # route stabilized: DPEbAJe-CNroâŠBNsF774NLUz4
- [ DONE ] Acquiring ingress session # handshake accepted: e75d3ef415b3âŠ1fd13d0c4ff9
- [ FAIL ] Tethering to Zigbee2MQTT # websocket disconnected after initial connection
I have z2m installed in the zigbee2mqttsoff folder instead of zigbee2mqtt, because at one time I had two instances of z2m.
Could that be the reason?
1 Like
That was exactly it.
1 Like
This is a great tool - Thanks for putting in all the work and making it available!
Whatâs the best way to submit some suggestions, like:
- It would help me a lot, if there was an additional column in the âDevicesâ tab (maybe only for EndDevices) that shows the signal quality (LQI) for that device.
- Is it possible to make it remember the setting for the âShow link particlesâ rather than defaulting to âOnâ?
- When I drag (or double-click) an EndDevice show the LQI value for that deviceâs connection?
- OK, I know Iâm stretching it now:
When I click on an EndDevice, show the highest LQI path back to the coordinator?
2 Likes
All good ideas, but especially #2.
1 Like
I think this thread is the best place for suggestions. You added some really good ones , hope I get a bit of time to include them.
#4 comes from a good place, but I believe it does more bad than good, simply because thatâs not how zigbee routing works: consecutive messages between the same source and destination might take different paths; also request and reply messages between 2 devices most likely use different paths too. Zigbee routing is an unpredictable mess that somehow just works.
1 Like
Mess, and/or mesh? Often both!
2 Likes
Released version 1.2.0 with the following changes:
Added
- Show the LQI value when end-devices are dragged - @chairstacker
- Add âLQIâ information in the âDevicesâ list - @chairstacker
- Persist options in browser local storage - @chairstacker
Have fun!
Sounds great - do you have a direct download link for the new version?
I tried the link in your original post as well as downloading the js-file from here - restarted HA both times after that, but I still see v1.1.1.
Sorry for being a little dense here 
1 Like
The original link should go to the latest version. Try to get past the browser cache with Ctrl+F5 or Ctrl+Shift+R after loading the link.
Do the same trick when loading the HA UI, or clear the browser cache. No need to restart HA.
Tried that before, tried it again - seems to be a browser cache issue in both Chrome and Edge, because it sticks to the old version when hitting Ctrgl+F5 and Ctrl+Shift+R.
I can get it to use v1.2.0 when I switch to an InPrivate/Incognito window, though 
1 Like
@chairstacker in Chrome (at least using Windows OS), hit f12 to bring up the developer sub window, then right click the reload icon on the browser, that should make a tiny drop down window appear. Click âEmpty cache and hard reloadâ. Hopefully, that does the trick for you
1 Like
Clearing the cache did the trick - just baffled that neither Ctrl+F5 nor Ctrl+Shift+R worked.
1 Like