Listener is not active after restart of the server.
I am using ewelink listener a lot. I am receiving all changes from my smart switches in my house.
Today I was doing several restarts of node-red and I realized, that after each restart listener is not sending any msg messages. Even if simply connect it to debug node is not sending anything. Although it is showin "connected" icon. I have to recreate ewelink listener again, select credentials created before and it is working. I don't like this behavious, because that means I will have to do manually after every restart.
Any idea what could be the reason for that?
I am pasting also log after start of node-red.
demokedes@NodeRed:~$ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://10.0.0.4:1880
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to http://flows.nodered.org
Starting as a systemd service.
14 Feb 19:25:03 - [info]
Welcome to Node-RED
===================
14 Feb 19:25:03 - [info] Node-RED version: v2.2.0
14 Feb 19:25:03 - [info] Node.js version: v16.14.0
14 Feb 19:25:03 - [info] Linux 5.4.0-1069-azure x64 LE
14 Feb 19:25:03 - [info] Loading palette nodes
Mon, 14 Feb 2022 19:25:04 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/modules/cjs/loader:1103:14
14 Feb 19:25:05 - [info] RedBot version: 0.19.11 (node-red-contrib-chatbot)
14 Feb 19:25:07 - [info] Dashboard version 3.1.5 started at /ui
14 Feb 19:25:07 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
14 Feb 19:25:07 - [info] Settings file : /home/demokedes/.node-red/settings.js
14 Feb 19:25:07 - [info] Context store : 'default' [module=memory]
14 Feb 19:25:07 - [info] User directory : /home/demokedes/.node-red
14 Feb 19:25:07 - [warn] Flows file name not set. Generating name using hostname.
14 Feb 19:25:07 - [info] Flows file : /home/demokedes/.node-red/flows_NodeRed.json
14 Feb 19:25:07 - [info] Server now running at http://127.0.0.1:1880/
14 Feb 19:25:07 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
14 Feb 19:25:07 - [info] Starting flows
14 Feb 19:25:07 - [info] Started flows
![Screenshot 2022-02-14 203144|634x190](upload://mQHo7f919W3IC7mcAYI4A0ER0vU.jpeg)