Domoticz Community Forum - Support & Discussion

Hello everyone,

Version 9.1.008 of the stable9 branch has just been released. It brings together 58 pull requests. Here are the highlights.

🕸️ New: the Mesh graph
The WebUI has a new view at Network > Mesh graph. It shows the real mesh of your Zigbee network, built from the tables each router reports:

• Neighbours, routing and associated devices: each table has its own view, with several layouts and filters.
• Computed routes: pick a device and the WebUI draws its path to the coordinator. Each hop shows whether it was seen in the tables or estimated.
• With zigpy, a topology scan now queries every router, where most were skipped before. A scan therefore takes a few minutes instead of a few seconds, and that is
  expected.

Full documentation: WebUI – Mesh graph

📖 The English Wiki has been fully refreshed
Alongside this release, the English Wiki has been reviewed from end to end. About 90 pages were rewritten or updated for stable9 and zigpy coordinators:

• A new index organised by what you want to do: install, pair, operate, troubleshoot.
• Rewritten installation pages, including the Python virtual environment, Docker and Synology.
• New pages on coordinator backups, on replacing or migrating a coordinator, and on reporting a problem, including which logs to provide.
• The whole WebUI documented from the current screens, with new screenshots.
• A richer FAQ that now includes the recurring questions from the French forum.
• Pages that only apply to ZiGate are grouped under a "Legacy ZiGate" section.

Start here: Zigbee for Domoticz Wiki

Other changes

• The WebUI moves to Angular 21, which clears the 23 security advisories open against the previous version.
• A hardened WebUI server: no file access outside its own folders, faster answers, and the WebUI no longer stays on the old version after an upgrade.
• The "device not seen" delay (Health) is now configurable for the whole plugin or per device (Param HealthTimeOut).
• A new Button_4 selector (click / double / triple / long), first used by the Sonoff SNZB-01M.
• Groups: many fixes, especially for Legrand multi-gang remotes.
• A command sent to a device that has left the network is refused, with a clear message in the log.
• The plugin upgrade is more robust, especially on Docker / Synology.
• The daily coordinator backup is now always a full backup.

⚠️ Good to know: EZSP (Silabs) users
The default TX power (0) now means "keep the radio's own TX power" instead of forcing 0 dBm at every start. If an older version left your coordinator at 0 dBm, it is set once to 8
dBm, the bellows default. Range improves, and some battery devices may switch to another parent in the hours after the upgrade.

Upgrading
As usual, upgrade from the WebUI or with git pull on the stable9 branch, then restart the plugin.
Full changelog: ReleaseNotes.md

Feedback on the Mesh graph and on the new Wiki is very welcome, and screenshots of your own networks even more so 🙂

Happy Zigbee-ing!

Thanks for the update. The update was done thru the web iu, without problems.
Very nice that the wiki is up to date now. I the past i had to figure it out myself how to solve a problem when a update failed and had to combine some documents to make it work again.
The mesh graph is a nice, can see how the devices are connected to eachother, more detailed then the older versions.

Thank you very much, pipiche, for again an update of this great Zigbee plugin. I just updated via cli. No problems.
Thank you especially for the improved English Wiki. One cannot underestimate the importance of good documentation! Good software without proper documentation is useless. So therefore, thanks for the new Wiki!

Thanks a lot @Rik60 and @WouterO for your kind and warm feedback, it really means a lot!

Glad the update went smoothly, via the web UI or the CLI. The wiki was long overdue, so I'm happy it already helps.

I'm doing my best, but maintaining the code, the wiki and further improvements all at once is quite a challenge.

Any support is welcome: testing, reporting issues with logs, helping others on the forum, or contributing to the wiki or the code.

And for those who prefer, a small donation via Buy Me a Coffee or PayPal (links on the GitHub page) also helps keep the project going.

Thanks again!
Pipiche