SamIAm

> Having the capability of placing the ZigBee nodes in a floorplan is a wonderful idea :) It will help in placing adequately the routers to build a good mesh....

This is a edited copy of the configurable items from ZZv1 that will likely be the basis for ZZv2. ``` { "iconColorCoordinator":"blue", "iconColorEndDevice":"red", "iconColorRouter":"orange", "iconColorUnknown":"grey", "iconNameCoordinator":"mdi:radio-tower", "iconNameEndDevice":"mdi:zigbee", "iconNameRouter":"mdi:router", "iconNameUnknown":"mdi:crosshairs-question", "colorLQIGood":"lightgreen",...

Great idea! Also to allow a user to filter/select/focus on Zigs based on a name/area (Adds to the ever growing roadmap lol)

I **REALLY** need to add the icon/colour legend to the documentation!  Zigbee endpoint info is both obscure (at times) and HUGE! (https://www.eetimes.com/zigbee-applications-part-5-addressing-within-the-node/) At present...

By the way @DrCoolzic ... thank you for your feedback ... it is detailed, valuable and much appreciated in helping sort out some of the annoying ZZ issues! :)

> Not sure what "available" means here? Like an end device sleeping? The response I received on Discord (_From the oracle of Zigbee stuff_) is as follows:  So perhaps...

1) You're very welcome. Zigzag v2 is in the final stages (It'll have zoom/pan and is faster). 2) Yes. 3) :(. As it happens, there have been a whole bunch...

Thanks @MattWestb, but that is from v1. If you put an svg file in your local folder (the www folder) like this (_home assistant www folder_)/**zigzag/background.svg** It should appear :)

All fantastic ideas. At present my time is being totally absorbed by rebasing Zigzag as an addon, both to allow easier installation via Supervisor and to allow for a number...

It is an undocumented thing I'd played with. If one has a background.svg in that location, it will be used as a backdrop in zigzag, like this.