andreypopov/node-red-contrib-zigbee2mqtt

Zigbee2mqtt connectivity nodes for node-red

node-red-contrib-zigbee2mqtt's Issues

Switch and send value on start

Today I try to update from deconz to zigbee2mqtt and I have the first questions .....
Now I have:
. palette zigbee2mqtt 0.6.13
. version [email protected]
. ubuntu 20.04
. Node-RED version: v2.0.6
. Node.js version: v14.16.0

The pairing with switch Vimar is ok and the switch works fine, I have the flag "Send value on start" but at deploy I haven't the status of the switch.

You can see the payload empty.
I'm starting to get the correct status when I press the switch for the first time.

EDIT: I noticed that the status is sent after 5 min and later every 5 min, but I need it immediately not after 5 min.
I don't understand .....

Xbee network

Hi, can we use this project with Xbee modules?

Get node empty payload after deploy

Hey

This is a new issue i have just noticed, must be since last version? but when i use the get node it pushes through a empty payload at first, eventually it does work, but deploying NR again breaks it for a long while again.

as you can see here the payload output hasn't populated,

but give it a while and it returns until next deploy

NR: v2.1.3
Z2M Nodes : 0.6.11
Z2M : 1.22.0
EDIT: just noticed the input node is doing the same

Install failed

Hi Andrey,

Hi I'm trirying to install your zigbee2mqtt addon to node-red but raise a error and fail to install.

Post the node-red log about the failed install launch:

2020-03-28T19:28:00.622Z Install : node-red-contrib-zigbee2mqtt 0.0.8

2020-03-28T19:28:00.686Z npm install --no-audit --no-update-notifier --save --save-prefix="~" --production [email protected]
2020-03-28T19:28:13.904Z [err] npm
2020-03-28T19:28:13.905Z [err] WARN deprecated [email protected]: request has been deprecated, see request/request#3142
2020-03-28T19:28:30.830Z [err] npm
2020-03-28T19:28:30.831Z [err] WARN [email protected] requires a peer of [email protected] - 3 but none is installed. You must install peer dependencies yourself.
2020-03-28T19:28:30.831Z [err] npm
2020-03-28T19:28:30.831Z [err] WARN [email protected] No repository field.
2020-03-28T19:28:30.832Z [err] npm
2020-03-28T19:28:30.832Z [err] WARN [email protected] No license field.
2020-03-28T19:28:30.834Z [err]
2020-03-28T19:28:30.858Z [err] npm
2020-03-28T19:28:30.858Z [err] ERR! code EROFS
2020-03-28T19:28:30.859Z [err] npm ERR!
2020-03-28T19:28:30.859Z [err] syscall rmdir
2020-03-28T19:28:30.859Z [err] npm ERR!
2020-03-28T19:28:30.859Z [err] path /root/.node-red/node_modules/.staging/@babel
2020-03-28T19:28:30.861Z [err] npm
2020-03-28T19:28:30.861Z [err] ERR! errno -30
2020-03-28T19:28:30.862Z [err] npm
2020-03-28T19:28:30.862Z [err] ERR! rofs
2020-03-28T19:28:30.863Z [err] EROFS: read-only file system, rmdir '/root/.node-red/node_modules/.staging/@babel'
2020-03-28T19:28:30.863Z [err] npm
2020-03-28T19:28:30.864Z [err] ERR! rofs
2020-03-28T19:28:30.864Z [err] Often virtualized file systems, or other file systems
2020-03-28T19:28:30.864Z [err] npm
2020-03-28T19:28:30.864Z [err] ERR! rofs that don't support symlinks, give this error.
2020-03-28T19:28:30.953Z rc=226

---

2020-03-28T19:29:20.467Z Install : node-red-contrib-zigbee2mqtt 0.0.8

2020-03-28T19:29:20.506Z npm install --no-audit --no-update-notifier --save --save-prefix="~" --production [email protected]
2020-03-28T19:29:29.206Z [err] npm
2020-03-28T19:29:29.207Z [err] WARN registry
2020-03-28T19:29:29.207Z [err] Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EROFS: EROFS: read-only file system, open '/root/.npm/_cacache/tmp/e4cad901'
2020-03-28T19:29:29.209Z [err] npm
2020-03-28T19:29:29.209Z [err] WARN
2020-03-28T19:29:29.209Z [err] registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
2020-03-28T19:29:29.367Z [err] npm
2020-03-28T19:29:29.367Z [err] WARN deprecated [email protected]: request has been deprecated, see request/request#3142
2020-03-28T19:29:37.459Z [err] npm
2020-03-28T19:29:37.460Z [err] ERR! code EROFS
2020-03-28T19:29:37.460Z [err] npm ERR!
2020-03-28T19:29:37.461Z [err] syscall open
2020-03-28T19:29:37.461Z [err] npm ERR!
2020-03-28T19:29:37.461Z [err] path /root/.npm/_cacache/tmp/1a249f55
2020-03-28T19:29:37.462Z [err] npm
2020-03-28T19:29:37.463Z [err] ERR! errno
2020-03-28T19:29:37.463Z [err] -30
2020-03-28T19:29:37.470Z [err] npm
2020-03-28T19:29:37.471Z [err] ERR! rofs EROFS: read-only file system, open '/root/.npm/_cacache/tmp/1a249f55'
2020-03-28T19:29:37.471Z [err] npm
2020-03-28T19:29:37.472Z [err] ERR! rofs
2020-03-28T19:29:37.472Z [err] Often virtualized file systems, or other file systems
2020-03-28T19:29:37.472Z [err] npm
2020-03-28T19:29:37.472Z [err] ERR! rofs that don't support symlinks, give this error.
2020-03-28T19:29:41.170Z [err] npm
2020-03-28T19:29:41.171Z [err] WARN checkPermissions Missing write access to /root/.node-red/node_modules
2020-03-28T19:29:42.075Z [err] npm
2020-03-28T19:29:42.076Z [err] WARN [email protected] requires a peer of [email protected] - 3 but none is installed. You must install peer dependencies yourself.
2020-03-28T19:29:42.076Z [err] npm
2020-03-28T19:29:42.076Z [err] WARN [email protected] No repository field.
2020-03-28T19:29:42.076Z [err] npm
2020-03-28T19:29:42.077Z [err] WARN [email protected] No license field.
2020-03-28T19:29:42.079Z [err]
2020-03-28T19:29:42.090Z [err] npm
2020-03-28T19:29:42.090Z [err] ERR! code EROFS
2020-03-28T19:29:42.090Z [err] npm ERR!
2020-03-28T19:29:42.091Z [err] syscall access
2020-03-28T19:29:42.091Z [err] npm ERR!
2020-03-28T19:29:42.091Z [err] path /root/.node-red/node_modules
2020-03-28T19:29:42.092Z [err] npm
2020-03-28T19:29:42.092Z [err] ERR! errno
2020-03-28T19:29:42.092Z [err] -30
2020-03-28T19:29:42.093Z [err] npm
2020-03-28T19:29:42.093Z [err] ERR!
2020-03-28T19:29:42.093Z [err] rofs EROFS: read-only file system, access '/root/.node-red/node_modules'
2020-03-28T19:29:42.093Z [err] npm ERR!
2020-03-28T19:29:42.094Z [err] rofs Often virtualized file systems, or other file systems
2020-03-28T19:29:42.094Z [err] npm ERR!
2020-03-28T19:29:42.094Z [err] rofs that don't support symlinks, give this error.

Has zigbee2mqtt library to be installed?

Hi, can this package be used right away or do I have to install the zigbee2mqtt software beforehand?

Dynamic device support for 'out' and 'get' nodes

In order to support DRY subflows it would be great if the device of 'out' and 'get' nodes could be optionally set by a message property. If changing a device isn't possible this could be at least accepted if no device was configured and persisted to the node's context.

Devices are not stored in IN-Node & device Names cannot be set

Hi,

thx for the dev work. I am using Z2M for a couple of sensors and buttons in my home automation setup.

I can connect to the bridge successfully. I get a list of devices but....

• trying to set a new friendly name on a device does not work --> pop-up error message "no such device"
• using the IN-Node I can select a device and deploy. No events from the device are coming through though. Re-editing the node it looks like the device was not stored --> Device field ist empty

Any idea?

Regards,

Stephan

Does the Zigbee2MQTT server and MQTT Broker need to be on the same host?

Hi. I can't seem to get this to work. The Zigbee2MQTT bridge node always has a RED DOT at the bottom which probably means it can't connect. I have other nodes using the basic MQTT node-red and are able to connect to the Mosquitto broker. My Mosquitto broker is on a different machine (IP) from the Raspberry-Pi running the Zigbee2MQTT server. So for the Host IP configuration, which IP (Mosquitto or RaspPi) should I put there? Any way I tried both both none of them connected. Let me know what other info you need.

Thank you.

IN command did not return payload status

Hello,
I'm running a IN command to do action depending on the state of the light :

If I debug the payload I get this :

Perhaps, I'm not using the good way the IN command, but I want to get the state of the light ON/OFF and if ON the brightness and all others informations.

cannot disable "Empty devices list. Bug?" message from GET node

This is the flow for the moment (cannot get data unless i call for it) and the error message is correct, but when i update using the flow, it works as it should...
https://pastebin.com/0Ax30tvd

Is it possible to get the a feature to disable this message in GET node?

cannot get device list on zigbee2mqtt @1.20.0

I've updated zigbee2mqtt to v 1.20 via update.sh
now the nodered palette cannot get the device list anymore.

it keeps prompting disabled entries GROUP and DEVICE like this

Problem installing the node-red-contrib-zigbee2mqtt

I'm running the following setup:

11 Feb 18:48:12 - [info] Node-RED version: v1.2.7
11 Feb 18:48:12 - [info] Node.js version: v12.20.1
11 Feb 18:48:12 - [info] Linux 5.4.83-v7l+ arm LE

Installing the package from the command line gives:

root@raspberrypi:~# npm i node-red-contrib-zigbee2mqtt
npm WARN saveError ENOENT: no such file or directory, open '/root/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/root/package.json'
npm WARN [email protected] requires a peer of [email protected] - 3 but none is installed. You must install peer dependencies yourself.
npm WARN root No description
npm WARN root No repository field.
npm WARN root No README data
npm WARN root No license field.

Any suggestions of what is happening here?

zigbee2mqtt-out - missing example flow...

followed this https://www.zigbee2mqtt.io/devices/GS361A-H04.html
but cant get it to work... have i done something wrong?

the flow:

the data i pass:

result: not changed...

maybe this is wrong...?

can the "in" or "get" nodes report device offline?

hi there,
I am using your extension with a decent number of nodes (30+) and I really like it! THANKS.

I was just wondering however, if the nodes "in" or "get" can also report device "offline"?

Currently I am using a MQTT-in node to subscribe to e.g. "zigbee2mqtt/Bathroom motion/availability" which gives me online / offline results.

I noticed that e.g. a bulb that is turned off with a regular wall switch reports "offline" in zigbee2mqtt which is then passed on to my mqtt server (and node red). But the in- and get-nodes both, show "OK" for that device.

My MQTT-in now (as described above) catches that but it would be really cool, if the in- or get-nodes would do that for me!

Is that functionality already built-in or if not, is it planned for a future release?

THANKS

Effect support

Z2M now exposes the effect command.

https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttfriendly_nameset

Allows for interesting effects. Please add support.

// Trigger effect on a device (e.g. bulb blinks)
  // Supported: blink, breathe, okay, channel_change, finish_effect and stop_effect
  "effect": "blink",

[Question] zigbee2mqtt.in = "action" or "click" ?

Hi,
I am just wondering if, for switches or buttons, the information "action" is pulled or if this is the deprecated "click" ?

As described here : https://www.zigbee2mqtt.io/devices/WXKG11LM.html#xiaomi-wxkg11lm (paragraph "Deprecated click event")

Thanks for the confirmation,

Deploy makes Tradfri E1524 remote toggle

I have a Tradfri E1524 remote connected to a PEMENOL CC2531 on a raspberry 3.
Node Red and the zigbee2mqtt contrib are up to date.

When I deploy my flows it acts like the remote gets triggered.
When I subscribe to the MQTT Topic zigbee2mqtt/remotename it gets a triggered message twice:
"{"action":"arrow_left_click","battery":60,"linkquality":70}" (now its left click, before it was toggle)
I also have a zigbee2mqtt "In" node connected which "sends arrow_left_click" once.

Now I can´t deploy changes on my flows from my PC because it switches of my PC because of this :D

Grouping not working

Hi, I really like this plugin, thanks for your work!

It seems that the grouping feature is not working (properly).
I'm able to create a new group, but the search box below seems not to be working properly.
Sometimes it shows a single device or two, but most of the time, I don't get any results.

Thanks
best regards

cuctom topic

hi!
for sending the commands to some devices (for example double switch)
we should do pass topic like a

// left
// right

msg.topic = "zigbee2mqtt/0x00158d0003a27716/left/set"
msg.payload = "on"
return msg;

but you hardcode topic
node.server.mqtt.publish(node.server.getBaseTopic()+'/'+node.config.friendly_name + '/set', JSON.stringify(toSend));

TLS support?

Will TLS be supported to connect to an mqtt broker secured by TLS?

Option for power and usage reading

Dear..
Thaks for the great work!!!
Is there perhaps a option possible to create power and voltage etc reading from all the devices?

Like to see that option into the nr devices.

Hope you can built this.

Please update package.json for 0.6.13

I had to compare the packages from npm to check that the only changes were for #54.

Transition option has no effect

The transition option in an out node seems to be not working. The field is missing in the resulting mqtt message.

Option for disabling retain true for new devices

There is already this feature request #25

Since it is closed, I open a new one.

I also stumbled upon this problem. I only use node-red-contrib-zigbee2mqtt for adding new devices

The rest of the nodes functionality I don't use. So it would be really great to have a checkbox that new devices don't have retained flag set.

Thanks a lot in advance.

Some 'Payload Output' settings are missing after deploy

Hi!
First, Thank you for this extension! Very helpfull ^^
Before:

After:

I have this issue on 'aqara' sensors (lumi.weather) & 'sonoff' buttons (wb01) sensors for now, but working great other models or brands...
Any idea ? Maybe i need to get the whole payload, then
Thanks for help =)

Is there a QoS setting?

Really loving your work! Makes Node-Red much easier with Zigbee2MQTT devices!

However, is there a way to change the QoS settings for a push somehow?

Best,
Jan

IN node: Same data in payload output WindowCovering

Hi!
I found that IN node in payload output WindowCovering TargetPosition & CurrentPosition Characteristic always have same value. I think this is wrong

Node crashes when starting on pi3

Hi Just getting started with zigbee2mqtt. My 'test' is to pair and use an IKEA remote.
My system is up to date and I'm using
node-red 1.1.3
node v12.9.0
on a pi3 using Linux 5.4.51-v7+ arm LE
node-red-contrib-aedes 0.3.6
node-red-contrib-zigbee2mqtt 0.6.2

I create a bridge node and configure the server and the bridge. connect a debug node to the output.
Deploys successfully but after a while I lose the connection with the pi. How long this takes varies a lot, but once it does, node-red sits in an endless restart loop as shown in the logging below.
I have got as far as pairing the IKEA remote with the coordinator but never managed to get further than a successful pairing.

The only way I have found to get out of this is to remove the node from the diagram, remove the node with npm and reboot. The palette is then inconsistent with the install nodes so it takes a bit of fiddling to get it right and then I am back at the start ready to install the node again.

Any suggestions on what I should try next, or what I have done wrong?
thanks
Gary

Node Red Log:

21 Oct 15:24:46 - [info] [aedes broker:e27008de.58f51] Binding aedes mqtt server on port: 1883
21 Oct 15:24:46 - [error] [openweathermap in:Service] No API key set
21 Oct 15:24:47 - [info] [zigbee2mqtt-server:z2m s] MQTT Connected
21 Oct 15:24:47 - [red] Uncaught Exception:
21 Oct 15:24:47 - TypeError: Cannot read property 'toString' of null
    at /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/flows/Flow.js:437:62
    at Array.forEach (<anonymous>)
    at Flow.handleStatus (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/flows/Flow.js:429:30)
    at Zigbee2mqttNodeBridge.Node.status (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:551:16)
    at Zigbee2mqttNodeBridge.setNodeStatus (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/bridge.js:197:22)
    at Zigbee2mqttNodeBridge.onMQTTConnect (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/bridge.js:169:18)
    at ServerNode.Zigbee2mqttNodeBridge.node.listener_onMQTTConnect (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/bridge.js:39:69)
    at ServerNode.emit (events.js:314:20)
    at ServerNode.Node.emit (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:185:20)
    at ServerNode.onMQTTConnect (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/server.js:477:18)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Service RestartSec=100ms expired, scheduling restart.
nodered.service: Scheduled restart job, restart counter is at 6.
Stopped Node-RED graphical event wiring tool.

Zigbee2mqtt node doesn't handle all MQTT messages

Hello,

I just testing your Z2M node-red component but it seems that not all MQTT commands are correctly handled.

This is my simple test case:

and this is the debug log:

The first three clicks are notified by MQTT handled as same as Z2M handler, but when I continue in clicking these events are handled only by the MQTT handler and not Z2M.

Do you have any idea why this can happen? I have the same behavior on multiple Ikea buttons (5-button as same as 2-button or Xiaomi cube).

[Feature request] Network map

Hi,

I love the work you have here, exactly what is needed for a great integration with node-red.

I am currently using deconz, but with your project I have started to migrate to zigbee2mqtt.

May I request a link or something on the bridge-node to see the network map of the routing ?

Best regards

Will these work with the Tasmota Sonoff Zigbee Bridge?

Hello,

Will these work with the version of Zigbee2Mqtt that is incorporated into the Tasmota Zigbee Bridge?

Old copy of jquery "multiple-select" add-in causing issues with monaco-editor

Hi, with node-red 2.0.0 now supporting monaco editor it has been discovered that when node-red-contrib-zigbee2mqtt is installed the editor stops working.

See here

I have also tested this and get the same error.

Steps to repeat this issue...

1. Install latest node-red 2.0.0-beta.1
2. enable monaco in settings.js

        codeEditor: {
         lib: "monaco",
         options: {
             theme: "vs",
         }
     }
   

3. Run node-red - editor works as expected
4. Install node-red-contrib-zigbee2mqtt
5. Stop and restart node-red & refresh browser
6. open a function node - editor now broke (cannot types) & console shows error Uncaught Error: e[Symbol.iterator] is not a function

Tracking down the cause was problematic and I am still not certain why it happens however I hound by disabling $.getScript('zigbee2mqtt/static/js/multiple-select.min.js'); in app.html and restarting node-red / refresh browser, the editor now works again.

Further more, I found by replacing node-red-contrib-zigbee2mqtt/static/js/multiple-select.min.js (which is v1.4.2) with the latest version v1.5.2 from here the editor no longer breaks.

I have provided a temporary workaround for users of your node here on the node-red forum

No entity choice with multi entities devices .

Context
Container Docker Nodered, deploy with docker-compose on a RPI4.
Nodered v2.0.6
node-red-contrib-zigbee2mqtt: v0.6.9

Process
Call or receive entities to or from a entity of a device like: MOES switch module 2 gang
This module/device manage 2 entities (l1 - switch 1 & l2 - switch 2)

Expected result
Can choose one of the multiple entities of the devices and not just the device.

Current result
Have a list of devices but not all the entities.

msg.device.lastSeen not updating without "refresh all data"

I'm attempting to keep track of all my devices in a table, but msg.device.lastSeen is not updating WITHOUT a refresh all data, then it does get updated. Is this expected behaviour?

You can see with the contact sensor data below that the timestamp has not moved as all since about 10 mins ago (when I last refreshed all data in the bridge node).

node red crashes on friendly name change of a device

hi,

I'm using the extension for a few IKEA Tradfri devices. I'm really happy with it because it works fine and it safed me a lot of work.
But now I have an issue when I try to change a friendly name of a device via mqtt.
The name is changed by zigbee2mqtt but when the "in" and "out" nodes are trying to change the name, node red chrashes with error:
18 Mar 21:26:32 - [red] Uncaught Exception:
18 Mar 21:26:32 - TypeError: Cannot use 'in' operator to search for 'brightness' in
at Function.payload2homekit (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/lib/Zigbee2mqttHelper.js:132:26)
at ServerNode.getDeviceById (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/server.js:174:63)
at Zigbee2mqttNodeIn.updateTextStatus (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/in.js:163:38)
at Zigbee2mqttNodeIn.onMQTTMessage (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/in.js:147:22)
at ServerNode.Zigbee2mqttNodeIn.node.listener_onMQTTMessage (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/in.js:31:69)
at ServerNode.emit (events.js:326:22)
at ServerNode.Node.emit (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:181:20)
at ServerNode.onMQTTMessage (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/server.js:600:26)
at MqttClient. (/home/pi/.node-red/node_modules/node-red-contrib-zigbee2mqtt/nodes/server.js:28:62)
at MqttClient.emit (events.js:314:20)

I'm quite new to node red, so I'm not completely sure about my guess that the "in" and "out" nodes are causing the chrash, but when I remove them from the flow verything works fine.

Is there anything which I maybe configured wrong or which could help me to find the root cause of the error

Thanks in advance
Best Regards

Добавить поддержку Алисы

В принципе в заголовке и так все понятно:)

Use a variable for Device

What I want to do:

I have several switches that I control via Big Timer and whose state I subsequently read out. Works as desired. Now I want to set up a subflow, because large parts of the flow occur again and again. But "Device" is of course always a different one. How can I change the "Device" with each instance of the subflow? Via an environment variable? But there is nothing for this in the dropdown menu. Or is there another solution?

Translated with www.DeepL.com/Translator (free version)

Global Context

I can't seem to wrap my head around how to pass a global context variable through the out node...

Here's my setup... recently (today) got my controller and am switching from the Hue bridge to Z2M. All my automations are within node-red. How do I pass on a global context (color temp) in the out node? I was able to figure out the basics and it's working, just can't seem to figure out how to pass on a changing color temp.

{"state":"ON","brightness":254,"color_temp":233,"transition":2}

This works for the lights that need that setting, but how would I reference my variable in this instance?
Thanks for any help...

Error in setup documentation

During setup of a new bridge node, a host needs to be configured.
The documentation suggests that this is the address of your zigbee2mqtt server but it should say that it is the address of the MQTT server used....

Strange Off Behaviour by Homekit and IKEA RGB Lightbulb

First of all, thanks for your work.

I have come across a strange behavior, and I am not yet sure whether this is connected to the specific bulb or your nodes or me being stupid. Anyway:
Bulb Firmware, Node Red, zigbee2mqtt, homekit-bridged and your nodes being at latest stable, I have created a very simple flow (see also attachement "flow.txt").

When I switch ON the light for he first time, it goes to 100% Brightness, then I switch OFF and ON again, now the bulb is on at 1% brightness. in the screenshot of the debugging nodes you can see, that the response node outputs 0% twice then turns to 1% in Brightness on Zigbee level. The bulb is at the same time not connected to any group, direkt link or other flow, but when I simulate the same thing with Zigbee messages and dashboard, it perfectls keeps it's prior brightness.
Any Ideas?

flow.txt

No devices showing

I have not any devices in my list.
I did configure my MQTT server and it connect, but can't see any devices.
What I miss ?

Groups keep disappearing from device list

I'm having this strange issue with the Get node in particular. It almost all the time starts showing up as no device even though I set it up recently to use a group and the state of that group. While setting it up, and testing that my flow works, it appears to work just fine, but after some time of inactivity it start's saying no device, even though it's still showing the name of the group, and also what which payload output I had chosen.

When configurating the node again, you can see that the device dropdown is in fact empty, as the no device error would indicate. And when opening the device list, the groups area is then empty. But a quick refresh of devices and it's there again.

I don't think there is any issues with Zigbee2MQTT in general, because as you see on the underneath image here I have a simple MQTT OUT node that I control the same group with, by using a switch. And that works fine, even while the get node is saying no device

All newly added devices will have retain: true

Hi

All newly added device to zigbee2mqtt will have reatain: true option set. I found that server node of this addon adds this option on new device join. I don't want to have retained state messages for all my devices, and it is annoying to remove this each time I'm adding new device and then cleaing retain flag from mqtt network.

Please emove this feature or add some option in server node to control, if retain: true should be added or not.

Not able to connect to Mosquitto from NodeRED in non-host mode

System:
I am running NodeRED via the docker-compose implementation IOTstack (https://sensorsiot.github.io/IOTstack/Containers/Node-RED) in addition to Zigbee2mqtt and Mosquitto. I also added Portainer for easy management.
This runs on a Raspberry Pi 4B, and the coordinator is an electrolama zig-a-zig-ah.

Problem:
I added the node-red-contrib-zigbee2mqtt nodes to my palette as I had very good results with them in previous installations.
The docker environment runs in 'non-host'-mode, so if I'm not mistaken, I need to define the zigbee2mqtt server as the name of the mosquitto container (mosquitto) and not the loopback address (127.0.0.1).

This is confirmed by adding an MQTT server, if I define the host as "mosquitto", I can communicate to the zigbee devices via standard MQTT nodes.

My issue is that I can not get the zigbee2mqtt-server configured properly. I can't use the nodes of this repository.

Question
In case I am running NodeRED in a non-host docker environment, how should I set up the server connection?
I can test and feedback here.
I tried so far:
host: mosquitto port: 1883
host: 127.0.0.1 port: 1883

Here is my network list on Portainer:

These are the settings for the server:

(this works for the MQTT nodes...)

This is the result (no devices)

Date display not working on "in node"

The in node displays a date of "! Dec 31 1969" and doesn't appear to change. I assume this date should show the Last Seen date and time?

Thanks!

Bridge Note with TLS enabled MQTT broker shows offline although working OK

Set Up:
Node Red and mosquitto running on same docker host, zigbee2mqtt on standalone Rpi4. Z2M connects fine to Mosquitto with TLS enabled, node-red-contrib-zigbee2mqtt bridge node connects to Mosquitto fine (Relays all mqtt messages from Z2M, devices and status are shown correctly in bridge node) but status of bridge node shows "offline":

Logs of mosquitto show:
`2020-10-03T11:55:25: New client connected from 192.168.99.20 as NodeRed-53fa5640.85b908 (p2, c1, k60, u'nodered-rpi4iot').

2020-10-03T11:55:25: New client connected from 192.168.99.20 as NodeRed-53fa5640.85b908-tmp (p2, c1, k60, u'nodered-rpi4iot').

2020-10-03T11:55:25: Socket error on client NodeRed-53fa5640.85b908-tmp, disconnecting.`

I would think that the error is the handling of the tmp node to check connectivity, either due not taking TLS or user/pass setup into account.
Configuration of bridge mqtt node:

No devices

I have a perfect working installation of this Zigbee2MQTT node set running overseas. I've just returned to the UK, upgraded my UK Node-Red on RPI4 to the latest Node-Red (everything up to date - Node 14, NR 2.....

I installed Node-Red-Contrib-Zigbee2MQTT (as normal, as user Pi) using the Node-Red palette Manager (just as I did on my original RPi4 a couple of months ago) - and in Node-Red added a couple of sensors (using an INJECT node straight into MQTT to allow adding) - then renamed devices to something useful again using an INJECT node into MQTT).

The N-R-C-Zigbee2MQTT bridge node seems fine as I have a debug output on it - and it is showing various logging messages in the debug... and if I manually trigger, for example, one of my Aqara temperature sensors, a package comes from the bridge node to show the temperature - and if I rename the device again as above, the bridge node gets the updated "friendly" name - BUT - couple of problems... in bridge node properties - the version number is showing a minus sign instead of a version number - and WAY more importantly - the bridge node - properties - devices tab shows NO devices -and using REFRESH ALL DATA has no effect on that. I have NO idea where to start looking for why this is happening... hence I can't use the other nodes - HELP

Wrong payload output

After selecting a device in out node, the zigbee2mqtt command option does not show the relevant list of commands for that device. It seems stuck on a general list of commands unrelated to the specific device.

[Feature Request] Support for Radiator Valves

Hi, I really like this plugin, thanks for your work!

Can you add support for radiator valve commands?
The "out" node actually not support commands for Siterwell GS361A-H04 control.

https://www.zigbee2mqtt.io/devices/GS361A-H04.html

Readings:
away_mode: "OFF" / "ON"
battery: 100
child_lock: "UNLOCKED"
current_heating_setpoint: "21.0"
linkquality: 107
local_temperature: "21.1"
preset: "manual"
system_mode: "manual"
valve_detection: "ON"
window_detection: "ON"

Supported commands are:

child_lock: "UNLOCKED" / "LOCK"
current_heating_setpoint: "21.0" (string) can change in 0.5 steps
preset: "manual" / "scheduled" / "away"
system_mode: "manual" / "auto" / "off" -> preset change synchronous on system_mode change
valve_detection: "ON" / "OFF"
window_detection: "ON" / "OFF"

i can give you more information or tests
Thank you in advance.
Toxo

[BUG] TypeError: Cannot use 'in' operator to search for 'lastPayload' in null

Out node fails to process with error:
TypeError: Cannot use 'in' operator to search for 'lastPayload' in null

Device used in out node is a Group of LED.
Payload going into out node is a valid HomeKit payload.

It worked correctly before I moved to Group.