Node red - RevPi node server
Posted: 08 Mar 2022, 14:40
Hi,
Since I update node-red, I'm not able to connect to revpi node. Connexion lost always. . Need I come back to a previous version?
Sometimes it works but the response time is very long.
Is it possible to have several server running in the same time? Because when I open a node, I see 3 times Connecting to WS Server wss://localhost:8000 openning
Thanks
Here after what I see when I start node-red
pi@RevPixxxxx:~ $ sudo systemctl start noderedrevpinodes-server
pi@RevPixxxxx:~ $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://xx.xxx.xx.xxx: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.
Started Node-RED graphical event wiring tool.
8 Mar 11:38:20 - [info]
Welcome to Node-RED
===================
8 Mar 11:38:20 - [info] Node-RED version: v2.2.2
8 Mar 11:38:20 - [info] Node.js version: v10.19.0
8 Mar 11:38:20 - [info] Linux 4.19.95-rt38-v7 arm LE
8 Mar 11:38:25 - [info] Loading palette nodes
8 Mar 11:38:32 - [info] Dashboard version 3.0.4 started at /ui
8 Mar 11:38:33 - [info] Settings file : /home/pi/.node-red/settings.js
8 Mar 11:38:33 - [info] Context store : 'default' [module=memory]
8 Mar 11:38:33 - [info] User directory : /home/pi/.node-red
8 Mar 11:38:33 - [warn] Projects disabled : editorTheme.projects.enabled=false
8 Mar 11:38:33 - [warn] Flows file name not set. Generating name using hostname.
8 Mar 11:38:33 - [info] Flows file : /home/pi/.node-red/flows_RevPixxxxx.json
8 Mar 11:38:33 - [info] Server now running at http://127.0.0.1:1880/
8 Mar 11:38:33 - [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.
---------------------------------------------------------------------
8 Mar 11:38:34 - [info] Starting flows
8 Mar 11:38:35 - [info] Started flows
Connecting to WS Server wss://localhost:8000
Connection to WS Server established!
info Authorized by server!
8 Mar 11:39:46 - [info] Stopping flows
8 Mar 11:39:47 - [info] Stopped flows
8 Mar 11:39:47 - [info] Starting flows
Connecting to WS Server wss://localhost:8000
8 Mar 11:39:47 - [info] Started flows
Connection to WS Server established!
info Authorized by server!
Connecting to WS Server wss://localhost:8000
Connecting to WS Server wss://localhost:8000
Connecting to WS Server wss://localhost:8000
Connection to WS Server established!
Connection to WS Server established!
Connection to WS Server established!
info Authorized by server!
info Authorized by server!
Since I update node-red, I'm not able to connect to revpi node. Connexion lost always. . Need I come back to a previous version?
Sometimes it works but the response time is very long.
Is it possible to have several server running in the same time? Because when I open a node, I see 3 times Connecting to WS Server wss://localhost:8000 openning
Thanks
Here after what I see when I start node-red
pi@RevPixxxxx:~ $ sudo systemctl start noderedrevpinodes-server
pi@RevPixxxxx:~ $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://xx.xxx.xx.xxx: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.
Started Node-RED graphical event wiring tool.
8 Mar 11:38:20 - [info]
Welcome to Node-RED
===================
8 Mar 11:38:20 - [info] Node-RED version: v2.2.2
8 Mar 11:38:20 - [info] Node.js version: v10.19.0
8 Mar 11:38:20 - [info] Linux 4.19.95-rt38-v7 arm LE
8 Mar 11:38:25 - [info] Loading palette nodes
8 Mar 11:38:32 - [info] Dashboard version 3.0.4 started at /ui
8 Mar 11:38:33 - [info] Settings file : /home/pi/.node-red/settings.js
8 Mar 11:38:33 - [info] Context store : 'default' [module=memory]
8 Mar 11:38:33 - [info] User directory : /home/pi/.node-red
8 Mar 11:38:33 - [warn] Projects disabled : editorTheme.projects.enabled=false
8 Mar 11:38:33 - [warn] Flows file name not set. Generating name using hostname.
8 Mar 11:38:33 - [info] Flows file : /home/pi/.node-red/flows_RevPixxxxx.json
8 Mar 11:38:33 - [info] Server now running at http://127.0.0.1:1880/
8 Mar 11:38:33 - [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.
---------------------------------------------------------------------
8 Mar 11:38:34 - [info] Starting flows
8 Mar 11:38:35 - [info] Started flows
Connecting to WS Server wss://localhost:8000
Connection to WS Server established!
info Authorized by server!
8 Mar 11:39:46 - [info] Stopping flows
8 Mar 11:39:47 - [info] Stopped flows
8 Mar 11:39:47 - [info] Starting flows
Connecting to WS Server wss://localhost:8000
8 Mar 11:39:47 - [info] Started flows
Connection to WS Server established!
info Authorized by server!
Connecting to WS Server wss://localhost:8000
Connecting to WS Server wss://localhost:8000
Connecting to WS Server wss://localhost:8000
Connection to WS Server established!
Connection to WS Server established!
Connection to WS Server established!
info Authorized by server!
info Authorized by server!