search

andreypopov / node-red-contrib-zigbee2mqtt

Zigbee2mqtt connectivity nodes for node-red
GNU General Public License v3.0
95 stars 24 forks source link

"Error: getDevices timeout, close connection" spammed in log, and groups not updating #82

Open AlecTBM opened 2 years ago

AlecTBM commented 2 years ago

Hello Thank you for your good job with this package. However, it have become "unstable" after I updated to the latest version (2.1.6) from an quite old version. Sometimes it just start spamming "Error: getDevices timeout, close connection" hvem trying to select a device in a node, and the group list is emtpy, until I make a new group, then it gets updated. I am not sure if the "new" api is not correctly implemented somewhere. image

Zigbee2MQTT version 1.25.0 commit: 6f1460e4 Some settings from Zigbee2MQTT that may be different than "normal", just for information: image image image image

ambarusa commented 2 years ago

also this message: 

5/8/2022, 9:31:03 PM[node: MQTT Local Z2M](http://xxx:1880/#)
msg : string[33]
"Bridge status: {"state":"online"}"
andreypopov commented 2 years ago

I have no idea

Gulpman commented 2 years ago

Hi, I just updated to version 2.6.3 today and had the same issue (error message) as @ambarusa

After checking that everything else is set up correctly, I thought the plugin had forgotten the password for the connection to mosquitto. After I reentered the password in the connection I got a different error message:

"MQTT Error: Subscribe to "zigbee2mqtt/#"

Looking into the config node the base subsciption was "zigbee2mqtt" only - without the "/#". I cannot say, if that really was the base topic beforehand. If so - it worked flawlessly in the past. If not it may have vanished with the update.

I really don't know :) Just as information for @andreypopov who may know best about the code :)

After changing the base topic to "zigbee2mqtt/#" I did not get any further error messages.

Hope that helps.

Best Sascha