# Cannot GET /zigbee2mqtt/showMap

**URL:** <https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890>\
**Category:** General\
**Tags:** zigbee\
**Created:** [5 October 2021 19:43 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890 "2021-10-05T19:43:11Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![edje11](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/edje11/32/572_2.png) [@edje11](https://discourse.nodered.org/u/edje11)\
**Post date:** [5 October 2021 19:43 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/1 "2021-10-05T19:43:11Z")

</div>

I'm using [node-red-contrib-zigbee2mqtt](https://flows.nodered.org/node/node-red-contrib-zigbee2mqtt) for my Zigbee devices, works all great.  
In the Zigbee bridge node there's a tab with the option to generate a map of my Zigbee network, this works also great.  
However on this tab there's also a button "Open in full screen", if this is pressed we get an empty web page with the error **Cannot GET /zigbee2mqtt/showMap** , in the url of my browser is [http://192.168.1.127:1880/zigbee2mqtt/showMap?controllerID=fcbfb445.44989](http://192.168.1.127:1880/zigbee2mqtt/showMap?controllerID=fcbfb445.44989) , this all looks fine to me.  
I'm sure it was working a couple of months ago.  
What can be the problem or where to look to tackle the problem?

Nr V2.0.3, Dashboard 2.30.0

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [5 October 2021 21:46 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/2 "2021-10-05T21:46:14Z")

</div>

It is working for me, which doesn't help much except to prove that it not a node problem.

A few things to try (which to probably already have)  
Refresh the page and try repeating the map selection.  
Have a look at the empty web page with Dev Tools to see if there are any clues there. I get  
`<!-- Generated by graphviz version 2.40.1 (20161225.0304) -->`  
at the top of the guff, followed by an svg element

Have pop-ups been disabled in your browser?

My status;  
NR v2.0.6, Dashboard 3.0.4, node-red-contrib-zigbee2mqtt 0.6.9

So not sure if that makes any difference

url is [192.168.1.21:1880/zigbee2mqtt/showMap?controllerID=83162ab9.755208](http://192.168.1.21:1880/zigbee2mqtt/showMap?controllerID=83162ab9.755208) which is pretty much the same. I am using Edge, again not sure if that makes any difference

---

<div class="post-metadata">

**Author:** ![edje11](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/edje11/32/572_2.png) [@edje11](https://discourse.nodered.org/u/edje11)\
**Post date:** [5 October 2021 22:18 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/3 "2021-10-05T22:18:58Z")

</div>

Thanks for the help.

> [@edje11](#):
>
> I'm sure it was working a couple of months ago.

Mmmh, I remember now that I have changed something in the settings.js (httpAdminRoot: '/admin',) to get some icons installed.  
Opening the NR editor must be done now with [http://192.168.1.127:1880/admin/](http://192.168.1.127:1880/admin/).  
Tried opening the Zigbee map with the /admin in the url [http://192.168.1.127:1880/admin/zigbee2mqtt/showMap?controllerID=fcbfb445.44989](http://192.168.1.127:1880/admin/zigbee2mqtt/showMap?controllerID=fcbfb445.44989) and that's works, the map is shown full screen.

Now to find out how to get this url called by the button in the bridge node....

---

<div class="post-metadata">

**Author:** ![cflurin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cflurin/32/29_2.png) [@cflurin](https://discourse.nodered.org/u/cflurin)\
**Post date:** [5 October 2021 22:26 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/4 "2021-10-05T22:26:36Z")

</div>

As an option have a look at the build-in [frontend](https://www.zigbee2mqtt.io/information/frontend.html) which includes a map and more.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [6 October 2021 08:15 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/5 "2021-10-06T08:15:12Z")

</div>

I think that is a bug in the node? It has attached to the admin ExpressJS app instead of the user one.

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [6 October 2021 13:39 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/6 "2021-10-06T13:39:02Z")

</div>

There is also a flow called Z2M Admin which is a bit simpler than Frontend but is pure Node-RED

---

<div class="post-metadata">

**Author:** ![cflurin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cflurin/32/29_2.png) [@cflurin](https://discourse.nodered.org/u/cflurin)\
**Post date:** [6 October 2021 13:47 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/7 "2021-10-06T13:47:15Z")

</div>

I don't see the advantage of using `contrib-zigbee2mqtt`. For data exchange you can use the core `mqtt nodes` (less maintenance and trouble). For settings the `frontend` is really handy.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [6 October 2021 17:16 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/8 "2021-10-06T17:16:06Z")

</div>

The only value of the map is showing the inter-connectivity. Not sure if that data is available via MQTT and even if it were, you might still want to build a map (strictly speaking, the display is a "Graph").

Personally, I find browser bookmarks or web pages with links more than good enough to take me to the right page without messing with iframes and other complexities.

---

<div class="post-metadata">

**Author:** ![cflurin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cflurin/32/29_2.png) [@cflurin](https://discourse.nodered.org/u/cflurin)\
**Post date:** [7 October 2021 06:33 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/9 "2021-10-07T06:33:58Z")

</div>

> [@TotallyInformation](#):
>
> The only value of the map is showing the inter-connectivity. Not sure if that data is available via MQTT and even if it were, you might still want to build a map (strictly speaking, the display is a "Graph").

No need of MQTT for the build-in frontend. It's very easy to configure, open a browser with the zigbee2mqtt ip address and click the Map tab. Try yourself and you'll never want to miss it. 😀

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [7 October 2021 09:34 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/10 "2021-10-07T09:34:10Z")

</div>

> [@cflurin](#):
>
> open a browser with the zigbee2mqtt ip address and click the Map tab

I believe that it is necessary to include this in the zigbee2mqtt configuration file to enable the web frontend feature.

```auto
frontend:
  port: 8080

```

---

<div class="post-metadata">

**Author:** ![cflurin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cflurin/32/29_2.png) [@cflurin](https://discourse.nodered.org/u/cflurin)\
**Post date:** [7 October 2021 09:39 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/11 "2021-10-07T09:39:32Z")

</div>

Just click the link I've already posted but especially for you 😀 here the details:

```auto
configuration.yaml:

frontend:
  # Optional, default 8080
  port: 8080
  # Optional, default 0.0.0.0
  host: 0.0.0.0
  # Optional, enables authentication, disabled by default
  auth_token: your-secret-token

```

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [7 October 2021 12:32 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/12 "2021-10-07T12:32:53Z")

</div>

I already use it, I was just pointing out to others that this may not work out of the box, it is necessary to specify the option in the config file, which I don't think was necessarily made clear.

---

<div class="post-metadata">

**Author:** ![cflurin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cflurin/32/29_2.png) [@cflurin](https://discourse.nodered.org/u/cflurin)\
**Post date:** [7 October 2021 12:52 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/13 "2021-10-07T12:52:51Z")

</div>

> [@Colin](#):
>
> which I don't think was necessarily made clear.

Again see my link above, that's enough clear 😉

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [7 October 2021 12:55 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/14 "2021-10-07T12:55:50Z")

</div>

Clarity is in the eye of the beholder 🙂

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [7 October 2021 13:40 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/15 "2021-10-07T13:40:56Z")

</div>

> [@cflurin](#):
>
> No need of MQTT for the build-in frontend. It's very easy to configure, open a browser with the zigbee2mqtt ip address and click the Map tab. Try yourself and you'll never want to miss it.

That's what I was saying, and that's what I do 🙂 Just put the link into the Dashboard instead of trying to integrate.

---

<div class="post-metadata">

**Author:** ![cflurin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cflurin/32/29_2.png) [@cflurin](https://discourse.nodered.org/u/cflurin)\
**Post date:** [7 October 2021 14:15 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/16 "2021-10-07T14:15:46Z")

</div>

> [@Colin](#):
>
> Clarity is in the eye of the beholder 🙂

Sure! but this forum is for adults, so we don't need a milk bottle. 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [6 December 2021 14:16 UTC](https://discourse.nodered.org/t/cannot-get-zigbee2mqtt-showmap/51890/17 "2021-12-06T14:16:05Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.