I don’t know exactly how the diagramm is created in zigbee2mqtt. In this issue they recomand to update as less frequently as possible. If the Update now button does not work this is most likely related to the webhook. Open the developer tools in your browser and see if there are any error messages
I tried to show the network map according to the first post here but unfotunately it did not work.
First I copied the “custom_components” folder including the subfolders “custom_components/zigbee2mqtt_networkmap” and “custom_components/zigbee2mqtt_networkmap/www” to my “config” folder. I had no custom_components folder up to now.
Ok than once again. I am using HassOS 3.7 on a pi 3b.
Currently I have some Xiaomi sensors and Osram smart plug and a Conbee II Stick as gateway.
Everything is working fine with this configuration.yaml:
# Configure a default setup of Home Assistant (frontend, api, etc)
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# base_url: example.duckdns.org:8123
# Text to speech
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
I want to see the networkmap and therefore I followed the Instructions in the first post.
I had no “custom_components” folder in my “config” folder, therefore I copied it in (including subfolder “www”).
Afterwards I could not connect anymore to home-assistant via http://hassio.local:8123/hassio/system
When I used the old configuration.yaml is works again.
Question: What should I cange? Are the files correctly placed and can I just add this at the end of my configuration.yaml?
maybe some more background:
I have 4 servers, running: #1: RPI-82: hass.io (HassOS appliance) + zigbee2mqtt addon #2: RPI-83: hass on bare metal RPI3 (buster) #3: RPI-86: hass.io in docker on bare metal RPI4 (buster) #4: DEB-17: hass.io in docker on bare metal linux box (buster)
I can trigger zigbee2mqtt.update from #4
On #1: map is updated
On #2: map is updated
On #3: old map is displayed.
On #4: old map is displayed.
So I think it has something to do with the frontend, not the service itself.
Maybe some problem with security on files?
Is the result of triggering the service somewhere cached?
Is it not compatible with hass.io in docker?
Has it something to do with my docker config? I just followed the instructions on hass.io.
yep: “Maybe you need to delete the files and reinstall the component. I’ve had to do that in the past.”
solved my problem. no clue what the issue was, but just deleted the folder \usr\share\hassio\homeassistant\custom_components\zigbee2mqtt_networkmap
and created again from https://github.com/rgruebel/ha_zigbee2mqtt_networkmap
problem solved now.
No idea what caused/solved this issue…