🎉 Node-RED 1.2.1 released

Update: Node-RED 1.2.1 published with a fix for a race condition in the .config file migration.

Node-RED 1.2.0 is now generally available.

Full release notes on the blog: https://nodered.org/blog/2020/10/15/version-1-2-released

Thanks to everyone who tested the beta and provided feedback.

14 Likes

After upgrading to 1.2 some of my flows are missing and the Project history tab is empty!

@ghayne ok... All the usual questions for you: have you checked the log for any errors? Have you checked the browser developer console for any errors?

Lot's of errors in the install log:

Started : Thu 15 Oct 14:12:43 BST 2020
Running for user pi at /home/pi
Found global nodes:   :

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Package 'nodered' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 105 not upgraded.
Already have nodejs v8.16.0
Now install nodejs
Versions: node:v8.16.0 npm:6.13.4
Now install Node-RED
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
/usr/bin/node-red -> /usr/lib/node_modules/node-red/red.js
/usr/bin/node-red-pi -> /usr/lib/node_modules/node-red/bin/node-red-pi

> bcrypt@3.0.6 install /usr/lib/node_modules/node-red/node_modules/bcrypt
> node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download 
node-pre-gyp WARN Tried to download(404): https://github.com/kelektiv/node.bcrypt.js/releases/download/v3.0.6/bcrypt_lib-v3.0.6-node-v57-linux-arm-glibc.tar.gz 
node-pre-gyp WARN Pre-built binaries not found for bcrypt@3.0.6 and node@8.16.0 (node-v57 ABI, glibc) (falling back to source compile with node-gyp) 
make: Entering directory '/usr/lib/node_modules/node-red/node_modules/bcrypt/build'
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
  SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
  COPY Release/bcrypt_lib.node
  COPY /usr/lib/node_modules/node-red/node_modules/bcrypt/lib/binding/bcrypt_lib.node
  TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/usr/lib/node_modules/node-red/node_modules/bcrypt/build'

> bcrypt@3.0.8 install /usr/lib/node_modules/node-red/node_modules/node-red-admin/node_modules/bcrypt
> node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download 
node-pre-gyp WARN Tried to download(404): https://github.com/kelektiv/node.bcrypt.js/releases/download/v3.0.8/bcrypt_lib-v3.0.8-node-v57-linux-arm-glibc.tar.gz 
node-pre-gyp WARN Pre-built binaries not found for bcrypt@3.0.8 and node@8.16.0 (node-v57 ABI, glibc) (falling back to source compile with node-gyp) 
make: Entering directory '/usr/lib/node_modules/node-red/node_modules/node-red-admin/node_modules/bcrypt/build'
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
  SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
  COPY Release/bcrypt_lib.node
  COPY /usr/lib/node_modules/node-red/node_modules/node-red-admin/node_modules/bcrypt/lib/binding/bcrypt_lib.node
  TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/usr/lib/node_modules/node-red/node_modules/node-red-admin/node_modules/bcrypt/build'
npm WARN notsup Unsupported engine for tar@6.0.5: wanted: {"node":">= 10"} (current: {"node":"8.16.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: tar@6.0.5
npm WARN notsup Unsupported engine for mkdirp@1.0.4: wanted: {"node":">=10"} (current: {"node":"8.16.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: mkdirp@1.0.4
npm WARN notsup Unsupported engine for chownr@2.0.0: wanted: {"node":">=10"} (current: {"node":"8.16.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: chownr@2.0.0

+ node-red@1.2.0
added 359 packages from 320 contributors in 304.796s
1.2.0 
Now create basic package.json for the user and move any global nodes
Now add the shortcut and start/stop/log scripts to the menu
Now add systemd script and configure it for pi
Now add launcher to top bar, add cpu temp example, make sure ping works
The user `pi' is already a member of `gpio'.
Memory : 1.1G
Finished : Thu 15 Oct 14:12:43 BST 2020

ConsoleScreenshot-40

That's the install log - what about the log when Node-RED starts?

It says no active project although I am using projects.

Welcome to Node-RED
===================
15 Oct 15:19:25 - [info] Node-RED version: v1.2.0
15 Oct 15:19:25 - [info] Node.js  version: v8.16.0
15 Oct 15:19:25 - [info] Linux 4.19.58-v7+ arm LE
15 Oct 15:19:26 - [info] Loading palette nodes
15 Oct 15:19:30 - [info] Settings file  : /home/pi/.node-red/settings.js
15 Oct 15:19:30 - [info] Context store  : 'default' [module=localfilesystem]
15 Oct 15:19:30 - [info] User directory : /home/pi/.node-red
15 Oct 15:19:30 - [warn] No active project : using default flows file
15 Oct 15:19:30 - [info] Flows file     : /home/pi/.node-red/flows_salgar.json
15 Oct 15:19:30 - [info] Server now running at http://127.0.0.1:1880/
15 Oct 15:19:30 - [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.
---------------------------------------------------------------------
15 Oct 15:19:30 - [info] Starting flows
15 Oct 15:19:31 - [info] Started flows
15 Oct 15:19:31 - [info] [mqtt-broker:33b374f4.96a50c] Connected to broker: mqtt://192.168.1.2:1883
15 Oct 15:19:31 - [info] [alexa-remote-account:gh] intialising "gh" with the PROXY method and saved data...
15 Oct 15:19:31 - [info] [mqtt-broker:192.168.1.3] Connected to broker: mqtt://192.168.1.3:1883
15 Oct 15:19:31 - [info] [mqtt-broker:Glowmarkt] Connected to broker: mqtt://glowmqtt.energyhive.com

So it appears to have 'forgotten' what your active project was. You should be able to reopen the project from the Project's menu in the editor. If the 'open' option is disabled, select 'new' and then select the 'open existing project' option at the bottom of the new project dialog.

I get this after choosing the project
Screenshot-41

When I press "Setup credentials" I get:

How do I proceed?

Lets take this to a DM conversation so we don't flood the release post.

1 Like

Reload Flows isn't working on v1.2.1...

I tested it on two separate Node-RED installs.

Thanks - will have a 1.2.2 tomorrow.

1 Like

After upgrading to 1.2.1. node-red can't start.......

Side note... my flow to notify when a new version of NR is release, works like a charm. :slight_smile:

2 Likes

Now with the new nice feature/possibilty to organize the side bar tabs horizontally, I really wish for making it possible to organize flow tabs vertically. I have so many tabs, how nice would it not be to be able to drag and drop them to new positions?
Also like to add, I had no problems upgrading this RPi3, everything works!

Hi I tried to upgrade my old nodered/node-red-docker container with the new image nodered/node-red version 1.2.1
The container is not starting properly / restarting every minute. I mounted the old volume to /data.
The log is:

> node-red-docker@1.2.1 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
18 Oct 05:11:46 - [warn] Flushing file /data/.config.nodes.json.$$$ to disk failed : Error: EACCES: permission denied, open '/data/.config.nodes.json.$$$'
18 Oct 05:11:46 - [error] Failed to start server:
18 Oct 05:11:46 - [error] Error: EACCES: permission denied, open '/data/.config.nodes.json.$$$'
18 Oct 05:11:46 - [warn] Flushing file /data/.config.users.json.$$$ to disk failed : Error: EACCES: permission denied, open '/data/.config.users.json.$$$'
18 Oct 05:11:46 - [warn] Flushing file /data/.config.projects.json.$$$ to disk failed : Error: EACCES: permission denied, open '/data/.config.projects.json.$$$'
18 Oct 05:11:46 - [warn] Flushing file /data/.config.runtime.json.$$$ to disk failed : Error: EACCES: permission denied, open '/data/.config.runtime.json.$$$'

Update:
When i create a new volume every thing works fine.
I changed the old volume to public, now it works. The old flows seem to be lost. :cold_sweat:

Hello!
Reorderable sidebar tabs #2655.
There's a separate possible change to make to remember the last tab a user was on.
Is there such a possibility at the moment? info tab is not the most relevant in work.

Regards, Yuri