Does it work with just standard ISO8601 / RFC3339 / HTML5 (para 2.4.5) format? “2019-01-21T21:01:00.269” ? (the space in the original format swapped to a “T”, keep the “-”, no slashes)
See examples at https://tools.ietf.org/html/rfc3339#section-5.8
I hope that instead of inventing a new date/time format, a well known standard can be used.
@Robin already fixed this a year ago, so this shouldn’t be an issue any more. It works for me (in Safari).
I’m not concerned if it’s a standard format or not, it should just work. But maybe Robin want’s to look at it.
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
Yellow = Enddevice
Blue = repeater
I do not specify the colors, they are generated in zigbee2mqtt.
I create a instance of the javascript date object and then call the “toLocaleString” method of it.
I guess there shouldn’t be any problems.
is your mqtt server already ready when starting home assistant or will it be started afterwards?
Hi,
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.
Then I added:
webhook:
zigbee2mqtt_networkmap:
panel_iframe:
networkmap:
title: ‘Zigbee Map’
url: ‘/local/community/zigbee2mqtt_networkmap/map.html’
icon: ‘mdi:graphql’
to my configuration.yaml
it looked like that:
"# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
"# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
"# http:
"# base_url: example.duckdns.org:8123
"# Text to speech
tts:
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
webhook:
zigbee2mqtt_networkmap:
panel_iframe:
networkmap:
title: ‘Zigbee Map’
url: ‘/local/community/zigbee2mqtt_networkmap/map.html’
icon: ‘mdi:graphql’
"
After that I restated and I could not access hass.io anymore. Cold you please help me?
None of your config will possibly work as you have no indentation. Either that or you posted it incorrectly. See How to help us help you - or How to ask a good question
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)
default_config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
# Text to speech
tts:
- 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?
zigbee2mqtt_networkmap:
panel_iframe:
networkmap:
title: 'Zigbee Map'
url: '/local/community/zigbee2mqtt_networkmap/map.html'
icon: 'mdi:graphql'
The network map described in this thread is for zigbee2mqtt. You are not using zigbee2mqtt, therefore it doesn’t, and can’t work.
OK thanks.
Actually I came to this Topic following the link from this one:
I will try to get an answer there.
I have the same problem…
I called the service and also set up a automation to reload every 10 minutes but i get the same card as you… No map showing…
What could be the problem there?
Hi,
My map was working, but for some reason is not updated anymore now.
If I call the service“zigbee2mqtt_networkmap.update” manual, I can see results coming in on my mqtt, i.e.
however, the iframe still displays an old result and is NOT updated:
What’s wrong here?
Kind regards,
Bart
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.
regards,
B
I can’t get this to work…just get a blank screen
I’ve installed the Integration and my yaml entries are:
config file
webhook:
zigbee2mqtt_networkmap:
automation file
- id: update_networkmap
alias: 'Zigbee Map aktualisieren'
hide_entity: true
trigger:
platform: time_pattern
minutes: '/10'
seconds: 00
action:
service: zigbee2mqtt_networkmap.update
Try ctrl-F5 when you get the blank screen.
refreshing the screen is not doing anything no 
It works fine with Hass.io in docker. That’s what I’m using. Maybe you need to delete the files and reinstall the component. I’ve had to do that in the past.
@cjsimmons
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…
kind regards,
Bart
Hi,
Using your tool for a while now. Thanks for the effort!
Now I have following situation:
Seems that some end devices are connected to two routers (or coordinator)…
Is this technically possible?
Or is there something wrong with my zigbee network? But all devices seem to work properly…
kind regards,
B
