ben423423n32j14e / zigbee2mqttadminpanel Goto Github PK

View Code? Open in Web Editor NEW

111.0 111.0 71.0 273 KB

Node-Red-Dashboard web interface for controlling Zigbee2MQTT

License: GNU General Public License v3.0

zigbee2mqttadminpanel's People

Contributors

Stargazers

Watchers

Forkers

rcarmo luismsandrade piranik andigs94 nborget f1jsh prasertsakd vayain jandik73 jrg89 online-junkie kdanthony vexter0944 robertfolkers cerw ospectreo ijs1550 bobzer joseba midnights-straychild guitar9 tkwant tenspot ahpigsy heijnens mrrioes monxhy oldbobak jakob-w sendter vooz2 goto100 adrienaa zanza71 cephos freifunkrothenburg badreddine-dlaila wtfso eatl104 jwkgit julesrulez96 gebauer saarsinai leondragon luongos hotabka bse4792 rktaiwala marinac013 chc189 zergofswarm kriogman kmiar czdeee liuleidp eugenesok flutho brotherwrong giflopa reikoxa gherbort intigration hugh0jie prinzkaiser divebeer tonvanuum mnrgrrt mhill312 zerico daudxu ylilike

zigbee2mqttadminpanel's Issues

"TypeError: Cannot read property 'length' of undefined"

I got following message.

"TypeError: Cannot read property 'length' of undefined"

It seems to be the subnode „status“

Question from a newbie

Hi,

I have just installed zigbee2mqtt and I want to use your dashboard.

I am stuck at this:

Import flow into "Zigbee2MQTT Admin Panel" flow

Which flow should I import? I have a Philips Hue light...

Could you help me?

Thanks!

How do I update the admin panel

First I wan't to thank you for putting work into making this admin panel. I really like it :-) How do I update it when you release new features. Do I simply re-import it into Node-RED?

Feature Request: Sort devices by friendly_name

As I am using a naming scheme, a sorted device list may come handy. I implemented this in my flow (lack of configuration keeps me using a "fork"). Anyway: this may help you/others:

Put a function node using the following code right behind the JSON node in Devices subflow.

BTW. the JSON node may be ommited, when configuring the mqtt-in node to do the JSON conversion by itself.

// coordinator does not have a friendly name
msg.payload.message[0].friendly_name="";
// sort
msg.payload.message.sort((a, b) => a.friendly_name.localeCompare(b.friendly_name));
return msg;

I had the zigbee2mqttadminpanel working several months. Wanted to start using it again as I'm going to add a new zigbee2mqtt stick. Whenever I go to https://192.168.1.38:1880/ui I get:
Cannot GET /ui
https://192.168.138:1880 brings up node red without a problem.

I updated the node-red-dashboard. That didn't help
I deleted the zigbee2mqttadminpanel flow and all the subflows.
Imported the zigbee2mqttadminpanel flow back in and corrected the mqtt settings for my setup.
I still get Cannot GET /ui

I'm not sure how I borked the config up, but asking for help or ideas. Below is my node red log and also screenshots. I've been getting that length of undefined error for as long as I can remember if I'm not mistaken. I haven't been able to track its origin.

`Welcome to Node-RED

3 Jul 21:13:12 - [info] Node-RED version: v0.20.6
3 Jul 21:13:12 - [info] Node.js version: v10.16.0
3 Jul 21:13:12 - [info] Linux 4.14.98-v8 arm64 LE
3 Jul 21:13:13 - [info] Loading palette nodes
3 Jul 21:13:21 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
3 Jul 21:13:22 - [info] Dashboard version 2.15.5 started at /endpoint/ui
3 Jul 21:13:24 - [info] Settings file : /etc/node-red/config.js
3 Jul 21:13:24 - [info] Context store : 'default' [module=memory]
3 Jul 21:13:24 - [info] User directory : /config/node-red/
3 Jul 21:13:24 - [warn] Projects disabled : editorTheme.projects.enabled=false
3 Jul 21:13:24 - [info] Flows file : /config/node-red/flows.json
3 Jul 21:13:24 - [info] Server now running at http://127.0.0.1:46836/
[21:13:24] INFO: Starting NGinx...
3 Jul 21:13:25 - [info] Starting flows
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
3 Jul 21:13:26 - [info] Started flows
3 Jul 21:13:26 - [error] [function:Format Data] TypeError: Cannot read property 'length' of undefined
3 Jul 21:13:26 - [info] [mqtt-broker:MQTT] Connected to broker: mqtt://192.168.1.38:1883
3 Jul 21:13:29 - [error] [function:Format Data] TypeError: Cannot read property 'length' of undefined
3 Jul 21:13:30 - [info] [server:Home Assistant] WebSocket Connected to http://hassio/homeassistant
[03/Jul/2019:21:21:04 -0400] 404 -(192.168.1.5) GET /ui HTTP/2.0 (Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36)
[03/Jul/2019:21:21:04 -0400] 101 -(192.168.1.5) GET /comms HTTP/1.1 (Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36)`

Cannot GET /ui

Coudn't go from here. Is it probably because I run node-red under a HTTPS and not HTTP ????? If so, is there something I can change to work?

All configurations seems to be done correctly since I get this msg "online" and no errors.

zigbee2mqtt/bridge/state : msg : Object
{ topic: "zigbee2mqtt/bridge/state", payload: "online", qos: 0, retain: true, _msgid:

device list is empty after upgrading to the lastest version

Hello Ben,

Thanks for this admin panel.
I have been using it for about 6 months.
Yesterday I tried to upgrade to the lastest version.
The panel seems to work but the "device list" is empty (I have about 10 devices).
When I go back to my old version, all my devices are back.

Any suggestion?

Thanks,
Fred

PS: suggestion for future versions = indicate the version number on the user interface

manual refresh vs. automatic polling

What about an option and a button for manual refresh of the device-list? Currently I deactivate the dashboard because of the traffic generated by continious polling.

Don't see the maps

Is normal that i dont see the network map?

Suggestions

Thanks for the great flow!
Please add LINKS to HTTP API URLS =)
Please add statuses (permit_join and so on), it is hard to understand should I turn it on or not =)
In Devices subflow sending timestamp to zigbee2mqtt/bridge/config/devices is useless (and leads to errors in debug), we should send zigbee2mqtt/bridge/config/devices/get and after than real devices list will be shown here:

In "Rename device" we can use dropdown list to avoid mistakes.
VizJS Networkmap shows in ~50% browser height (dunno why). Also can we get map in png or any other static format?
It is very hard to update flow to next version =( I manually edit all MQTT nodes in subflows, remove all existing subflows and MQTT settings and so on. Cannot provide any suggestion to make it easier =(

Thanks again, great work!

problem with dashboard

Hello, I did everything according to the instructions, but unfortunately my dashboard does not show me anything, how can I fix it?

Connection to MQTT Broker

Currently it is unclear how to connect to your MQTT broker. Also it has a reference to Domoticz.

Remove it

how do i remove this i dont want it anymore it keeps gving error messages every time i deploy

No devices shown

I can see messages popping up in the right-hand corner, but no devices displayed in the list:

I have been though all the subflows and made sure they point to my mqtt configuration node, Im a bit stumped now

How to remove?

Hi,
how do I remove the palette that were added when I've imported the flow?
Thanks!

GraphViz broken with ' in device description

var graphData = 'digraph G {node[shape=record];  "0x00124b0018e1e995" [style="bold, filled", fillcolor="#e04e5d", fontcolor="#ffffff", label="{0x00124b0018e1e995|0x0 |No model information available|online (2019-08-04T11:49:02+04:00)}"];  "0x00124b0018e1e995" -> "0x00124b001d3b0628" [penwidth=0.5, weight=0, color="#994444", label="42"]  "0x00124b0018e1e995" -> "0x00158d00031421a9" [penwidth=0.5, weight=0, color="#994444", label="105"]  "0x00124b0018e1e995" -> "0x00158d0002c00bd7" [penwidth=0.5, weight=0, color="#994444", label="50"]  "0x00124b0018e1e995" -> "0x00158d000257b860" [penwidth=0.5, weight=0, color="#994444", label="56"]  "0x00124b0018e1e995" -> "0x00158d0002e69749" [penwidth=0.5, weight=0, color="#994444", label="58"]  "0x00124b0018e1e995" -> "0x00158d0002ead0f9" [penwidth=0.5, weight=0, color="#994444", label="42"]  "0x00158d00031421a9" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{light_zal|0x2db7 |Xiaomi Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter (QBKG04LM)|online (00:04:02s ago)}"];  "0x00158d00031421a9" -> "0x00124b0018e1e995" [penwidth=1, weight=0, color="#994444", label="104"]  "0x00158d0002c00bd7" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{light_wc1|0xe776 |Xiaomi Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter (QBKG03LM)|online (00:04:42s ago)}"];  "0x00158d0002c00bd7" -> "0x00124b0018e1e995" [penwidth=1, weight=0, color="#994444", label="46"]  "0x00158d0002e69749" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{light_kitchen|0x8f1c |Xiaomi Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter (QBKG03LM)|online (00:01:21s ago)}"];  "0x00158d0002e69749" -> "0x00124b0018e1e995" [penwidth=1, weight=0, color="#994444", label="53"]  "0x00158d000257b860" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{light_guest1|0xfd88 |Xiaomi Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter (QBKG04LM)|online (00:04:55s ago)}"];  "0x00158d000257b860" -> "0x00124b0018e1e995" [penwidth=1, weight=0, color="#994444", label="53"]  "0x00158d00031de635" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{light_hall2|0x9806 |Xiaomi Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter (QBKG03LM)|online (00:00:06s ago)}"];  "0x00158d00031de635" -> "0x00124b001d3b0628" [penwidth=1, weight=0, color="#994444", label="90"]  "0x00124b001d3b0628" [style="rounded, filled", fillcolor="#4ea3e0", fontcolor="#ffffff", label="{0x00124b001d3b0628|0x8de2 |Custom devices (DiY) [CC2530 router](http://ptvo.info/cc2530-based-zigbee-coordinator-and-router-112/) (CC2530.ROUTER)|online (00:00:16s ago)}"];  "0x00124b001d3b0628" -> "0x00124b0018e1e995" [penwidth=0.5, weight=0, color="#994444", label="47"]  "0x00124b001d3b0628" -> "0x00158d00031de635" [penwidth=0.5, weight=0, color="#994444", label="94"]  "0x00124b001d3b0628" -> "0x00158d00031dd5a0" [penwidth=0.5, weight=0, color="#994444", label="66"]  "0x00124b001d3b0628" -> "0x00158d0002e69495" [penwidth=0.5, weight=0, color="#994444", label="74"]  "0x00158d00031dd5a0" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{light_bedroom|0x3459 |Xiaomi Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter (QBKG03LM)|online (00:02:51s ago)}"];  "0x00158d00031dd5a0" -> "0x00124b001d3b0628" [penwidth=1, weight=0, color="#994444", label="62"]  "0x00158d0002e69495" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{light_mama|0xf734 |Xiaomi Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter (QBKG03LM)|online (00:04:09s ago)}"];  "0x00158d0002e69495" -> "0x00124b001d3b0628" [penwidth=1, weight=0, color="#994444", label="70"]  "0x00158d0002ead0f9" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{light_hall1|0x9b16 |Xiaomi Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter (QBKG03LM)|online (00:02:30s ago)}"];  "0x00158d0002ead0f9" -> "0x00124b0018e1e995" [penwidth=1, weight=0, color="#994444", label="38"]}';

The problem with Xiaomi Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter (QBKG03LM)|online:

Domoticz log receives continuously messages when Z2M Admin Panel flow is running

Hi,

Both Domoticz, Node-Red and Zigbee2MQTT are running on an RPi3b (Stretch)
When "Zigbee2MQTT Admin Panel" flow is running, the Domoticz log receives continuously (each 4 seconds) messages from bridge....

When I stop Node-Red, the messagings stops

What is causing this?

 2019-12-17 18:40:10.114 (Zigbee) Received available devices list from bridge
2019-12-17 18:40:10.114 (Zigbee) Device LED1537R6 0x14b457fffe437ffb (0x14b457fffe437ffb)
2019-12-17 18:40:10.114 (Zigbee) Device CC2530.ROUTER 0x00124b001d44f5cf (Keuken_Router)
2019-12-17 18:40:10.114 (Zigbee) Device LED1537R6 0x14b457fffe4594ed (0x14b457fffe4594ed)
2019-12-17 18:40:10.115 (Zigbee) Device LED1537R6 0x14b457fffe266637 (0x14b457fffe266637)
2019-12-17 18:40:10.115 (Zigbee) Device E1524/E1810 0x000d6ffffe5e7ec7 (IKEA_Remote_E1524-E1810)
2019-12-17 18:40:14.126 (Zigbee) Received available devices list from bridge
2019-12-17 18:40:14.126 (Zigbee) Device LED1537R6 0x14b457fffe437ffb (0x14b457fffe437ffb)
2019-12-17 18:40:14.127 (Zigbee) Device CC2530.ROUTER 0x00124b001d44f5cf (Keuken_Router)
2019-12-17 18:40:14.127 (Zigbee) Device LED1537R6 0x14b457fffe4594ed (0x14b457fffe4594ed)
2019-12-17 18:40:14.127 (Zigbee) Device LED1537R6 0x14b457fffe266637 (0x14b457fffe266637)
2019-12-17 18:40:14.127 (Zigbee) Device E1524/E1810 0x000d6ffffe5e7ec7 (IKEA_Remote_E1524-E1810)
2019-12-17 18:40:18.141 (Zigbee) Received available devices list from bridge
2019-12-17 18:40:18.141 (Zigbee) Device LED1537R6 0x14b457fffe437ffb (0x14b457fffe437ffb)
2019-12-17 18:40:18.142 (Zigbee) Device CC2530.ROUTER 0x00124b001d44f5cf (Keuken_Router)
2019-12-17 18:40:18.142 (Zigbee) Device LED1537R6 0x14b457fffe4594ed (0x14b457fffe4594ed)
2019-12-17 18:40:18.142 (Zigbee) Device LED1537R6 0x14b457fffe266637 (0x14b457fffe266637)
2019-12-17 18:40:18.142 (Zigbee) Device E1524/E1810 0x000d6ffffe5e7ec7 (IKEA_Remote_E1524-E1810)
2019-12-17 18:40:22.103 (Zigbee) Received available devices list from bridge
2019-12-17 18:40:22.104 (Zigbee) Device LED1537R6 0x14b457fffe437ffb (0x14b457fffe437ffb)
2019-12-17 18:40:22.104 (Zigbee) Device CC2530.ROUTER 0x00124b001d44f5cf (Keuken_Router)
2019-12-17 18:40:22.104 (Zigbee) Device LED1537R6 0x14b457fffe4594ed (0x14b457fffe4594ed)
2019-12-17 18:40:22.104 (Zigbee) Device LED1537R6 0x14b457fffe266637 (0x14b457fffe266637)
2019-12-17 18:40:22.105 (Zigbee) Device E1524/E1810 0x000d6ffffe5e7ec7 (IKEA_Remote_E1524-E1810)
2019-12-17 18:40:26.116 (Zigbee) Received available devices list from bridge
2019-12-17 18:40:26.116 (Zigbee) Device LED1537R6 0x14b457fffe437ffb (0x14b457fffe437ffb)
2019-12-17 18:40:26.116 (Zigbee) Device CC2530.ROUTER 0x00124b001d44f5cf (Keuken_Router)
2019-12-17 18:40:26.116 (Zigbee) Device LED1537R6 0x14b457fffe4594ed (0x14b457fffe4594ed)
2019-12-17 18:40:26.117 (Zigbee) Device LED1537R6 0x14b457fffe266637 (0x14b457fffe266637)
2019-12-17 18:40:26.117 (Zigbee) Device E1524/E1810 0x000d6ffffe5e7ec7 (IKEA_Remote_E1524-E1810)
2019-12-17 18:40:30.129 (Zigbee) Received available devices list from bridge
2019-12-17 18:40:30.129 (Zigbee) Device LED1537R6 0x14b457fffe437ffb (0x14b457fffe437ffb)
2019-12-17 18:40:30.130 (Zigbee) Device CC2530.ROUTER 0x00124b001d44f5cf (Keuken_Router)
2019-12-17 18:40:30.130 (Zigbee) Device LED1537R6 0x14b457fffe4594ed (0x14b457fffe4594ed)
2019-12-17 18:40:30.130 (Zigbee) Device LED1537R6 0x14b457fffe266637 (0x14b457fffe266637)
2019-12-17 18:40:30.130 (Zigbee) Device E1524/E1810 0x000d6ffffe5e7ec7 (IKEA_Remote_E1524-E1810)
2019-12-17 18:40:34.140 (Zigbee) Received available devices list from bridge
2019-12-17 18:40:34.140 (Zigbee) Device LED1537R6 0x14b457fffe437ffb (0x14b457fffe437ffb)
2019-12-17 18:40:34.140 (Zigbee) Device CC2530.ROUTER 0x00124b001d44f5cf (Keuken_Router)
2019-12-17 18:40:34.140 (Zigbee) Device LED1537R6 0x14b457fffe4594ed (0x14b457fffe4594ed)
2019-12-17 18:40:34.141 (Zigbee) Device LED1537R6 0x14b457fffe266637 (0x14b457fffe266637)
2019-12-17 18:40:34.141 (Zigbee) Device E1524/E1810 0x000d6ffffe5e7ec7 (IKEA_Remote_E1524-E1810)
2019-12-17 18:40:38.155 (Zigbee) Received available devices list from bridge
2019-12-17 18:40:38.155 (Zigbee) Device LED1537R6 0x14b457fffe437ffb (0x14b457fffe437ffb)
2019-12-17 18:40:38.156 (Zigbee) Device CC2530.ROUTER 0x00124b001d44f5cf (Keuken_Router)
2019-12-17 18:40:38.156 (Zigbee) Device LED1537R6 0x14b457fffe4594ed (0x14b457fffe4594ed)
2019-12-17 18:40:38.156 (Zigbee) Device LED1537R6 0x14b457fffe266637 (0x14b457fffe266637)
2019-12-17 18:40:38.157 (Zigbee) Device E1524/E1810 0x000d6ffffe5e7ec7 (IKEA_Remote_E1524-E1810)

MQTT Broker Source

Nice work.
It would be cool if we got the option to select mqtt broker source themselve.
actually we use MQTT","broker":"127.0.0.1" -> Some Sort of Config-Menu would help =)