I have recently attempted to update to node red 1.0.0 on pi 3 and zero w. I used the bash script to upgrade. After complete I start node red and when I attempt to open through local ip and server addresses but the pages gui won't load.
I am new to node red and the pi and had the process working prior to the 1.0.0 update. Can anyone help me work through this.
Did you search the forum ?
Verify the versions of npm, nodejs, dashboard.
what does the /var/log/nodered-install.log file contain ?
14 Oct 19:15:54 - [info] Node-RED version: v1.0.1
14 Oct 19:15:54 - [info] Node.js version: v10.16.3
14 Oct 19:15:54 - [info] Linux 4.19.75-v7+ arm LE
14 Oct 19:15:56 - [info] Loading palette nodes
14 Oct 19:16:04 - [info] Dashboard version 2.17.1 started at /ui
14 Oct 19:16:05 - [info] Settings file : /home/pi/.node-red/settings.js
14 Oct 19:16:05 - [info] Context store : 'default' [module=memory]
14 Oct 19:16:05 - [info] User directory : /home/pi/.node-red
14 Oct 19:16:05 - [warn] Projects disabled : editorTheme.projects.enabled=false
14 Oct 19:16:05 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
14 Oct 19:16:05 - [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.
14 Oct 19:16:05 - [info] Starting flows
14 Oct 19:16:05 - [info] Started flows
14 Oct 19:16:05 - [info] [inject:Temp Check] repeat = 5000
14 Oct 19:16:06 - [info] Server now running at http://127.0.0.1:1880/
14 Oct 19:16:06 - [info] [rpi-gpio out:Heat Lamp 1] out: 0
Im sorry guys, I'm very to new to all this tech being pi and node red and I'm self teaching. I have a var/log/nodered-install.log but there is to much to post. I have attempted to start fresh from new noobs install and would appreciate best practice to move on from here.
Follow the docs. There is a page for the raspberry pi with instructions
I have followed the docs from raspberry pi to update node.js and node-red and nom through the bash script but everytime I do upgrade. I am then unable to log into the server or the local address. Nodered boots in the terminal window as a systemd. But when I point a browser to the ip address shown in terminal it will not load.
Just to be clear - do you mean these docs?
Yes, that's the process and doc I used to install and attempt to run. Can I just ask, I reread the section on freeing up extra memory. Is node-red-pi --max-old-space-size=256 a one off terminal entry have the free space changed or should it be used on every boot of nodered
are you pointing a browser on a different computer at 127.0.0.1:1880 ?
That means “this machine” you need to find out the ip address that the node-red machine has on your network and use that
Yes I am. I have tried using that server address and also using the local ip through chromium on the pi itself. I have even tried login into the pi through vnc.
I will try a full format and start again.
Found the issue with the upgrade. After running noobs I allow the system to update recommended software. For some reason this caused instability.
After a fresh install, updating raspian, node red and node.js through terminal evetything is aok.
Hey guys, need to start this over. After the full rebuilt of raspian, updated or and node red to latest versions the dashboard worked a couple of times. Now it will not load. Once came up saying add dashboard nodes to use, there nodes there. I have tried to loading it on different machines without luck. Also loading the node red editor using the local address is very very slow. Will not load using the server address 127.0.0.1
Restart node red in a terminal and post the log here. Assuming you installed using the bash <(curl script then you can do that using
node-red-stop
node-red-start
pi@raspberrypi:~ $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.0.25: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
14 Nov 13:24:07 - [info] Starting flows
14 Nov 13:24:07 - [info] Started flows
14 Nov 13:24:07 - [info] Server now running at http://127.0.0.1:1880/
14 Nov 13:24:15 - [info] [debug:Temp 1] 31.25
14 Nov 13:24:15 - [info] [debug:Temp 3] 26.312
14 Nov 13:24:15 - [info] [debug:Temp 2] 28.812
14 Nov 13:24:23 - [info] [debug:Temp 1] 31.312
14 Nov 13:24:23 - [info] [debug:Temp 3] 26.312
14 Nov 13:24:23 - [info] [debug:Temp 2] 28.875
14 Nov 13:24:31 - [info] [debug:Temp 1] 31.312
14 Nov 13:24:31 - [info] [debug:Temp 3] 26.375
14 Nov 13:24:31 - [info] [debug:Temp 2] 28.875
14 Nov 13:24:39 - [info] [debug:Temp 1] 31.375
14 Nov 13:24:39 - [info] [debug:Temp 3] 26.375
14 Nov 13:24:39 - [info] [debug:Temp 2] 28.875
This also shows in the Browser F12 elements. "[Deprecation] Application Cache is restricted to secure contexts. Please consider migrating your application to HTTPS, and eventually shifting over to Service Workers. See https://goo.gl/rStTGz for more details"
What is the exact symptom you are seeing now? Please try accessing via a browser not running on the Pi. Part of the problem may be that the browser is overloading the Pi (what model is it?).
My symptoms are that the editor takes very long to load and deploy. The dashboard has 3 guages in it and will not load at all. I'm logging in using another pc and browser on the network. I have a pi 3 b+ and also pi zero w.
Can anyone tell me what the difference is when I run sudo-node-red compared to node-red-start. When run sudo-node-red the editor is lightening fast.
My symptoms are that the editor takes very long to load and deploy.
How do you deploy ? If you only deploy the flows that have changed, it will speed up significantly.
In a terminal on the node red machine run topand I suspect you will find that something is hogging the processor. If so then if you are using mqtt then stop the mqtt server, if that fixes it then possibly you have an mqtt loop.
As to running sudo node-red (I presume you meant that, not sudo-node-red) does that run the same flows file? You can see that in the log after starting it.
If still no joy, post the log you get when starting node red.
[edit] Sorry, I was on the phone and didn't notice which thread this is in. The symptom you describe is not the original symptom where it was saying there were no dashboard nodes. You have already posted the log so no need to do that again.
Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
The OpenJS Foundation | Terms of Use | Privacy Policy | OpenJS Foundation Bylaws | Trademark Policy | Trademark List | Cookie Policy
