# 🎉 Node-RED 4.0 released

**URL:** https://discourse.nodered.org/t/node-red-4-0-released/88815
**Category:** News
**Created:** [20 June 2024 13:53 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815 "2024-06-20T13:53:51Z")
**Posts on this page:** 17
**Page:** 5

<div class="post-metadata">

### Author: ![jundo](https://avatars.discourse-cdn.com/v4/letter/j/3da27b/32.png) [@jundo](https://discourse.nodered.org/u/jundo)
#### Post date: [26 June 2024 21:10 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/82 "2024-06-26T21:10:50Z")

</div>

> [@Colin](#):
>
> Computers do what you tell them to do, not what you meant them to do. It is necessary to use the correct commands.

Frankly at end I started node red as a service

```auto
sudo systemctl enable nodered.service

```

It seems working although i had to reimport flows

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [26 June 2024 21:19 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/83 "2024-06-26T21:19:21Z")

</div>

> [@jundo](#):
>
> `sudo systemctl enable nodered.service`

That does not start node-red as a service, it just tells systemd to start it on boot (as a service).  
`node-red-start` _does_ start it as a service immediately but also shows you the startup log. It is effectively the same as `sudo systemctl start nodered` followed by `sudo journalctl -f -n 0 -u nodered -o cat`.

---

<div class="post-metadata">

### Author: ![jundo](https://avatars.discourse-cdn.com/v4/letter/j/3da27b/32.png) [@jundo](https://discourse.nodered.org/u/jundo)
#### Post date: [27 June 2024 06:25 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/84 "2024-06-27T06:25:06Z")

</div>

Yes.  
The thing that worries me about using the upgrade command in the future is that I didn't understand what happened and why I lost my flows while keeping the palette.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [27 June 2024 07:01 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/85 "2024-06-27T07:01:42Z")

</div>

> [@jundo](#):
>
> The thing that worries me about using the upgrade command in the future is that I didn't understand what happened and why I lost my flows

Had you asked about how to fix that we could probably have helped. It may still be possible to work out what the problem was.  
What does this command show?  
`ls -al /home/roberto/.node-red`

---

<div class="post-metadata">

### Author: ![patrickL](https://avatars.discourse-cdn.com/v4/letter/p/65b543/32.png) [@patrickL](https://discourse.nodered.org/u/patrickL)
#### Post date: [4 August 2024 21:11 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/86 "2024-08-04T21:11:21Z")

</div>

i have a problem to have function of flowfuse.dashbard 2.0 (addon of home assistant).

```auto
[{"id":"0c44ce7ae7f9dcb0","type":"tab","label":"porte","disabled":false,"info":"","env":[]},{"id":"9d82c9d86212a10a","type":"ui-button","z":"0c44ce7ae7f9dcb0","group":"1cf97d7dc0a099ff","name":"texte","label":"button","order":1,"width":0,"height":0,"emulateClick":false,"tooltip":"","color":"","bgcolor":"","className":"","icon":"","iconPosition":"left","payload":"essai","payloadType":"str","topic":"topic","topicType":"msg","buttonColor":"","textColor":"","iconColor":"","x":250,"y":1080,"wires":[["dbf414e857f99ae2"]]},{"id":"dbf414e857f99ae2","type":"debug","z":"0c44ce7ae7f9dcb0","name":"debug 1","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":420,"y":1080,"wires":[]},{"id":"1cf97d7dc0a099ff","type":"ui-group","name":"My Group","page":"3e5a7def77e29cf0","width":"6","height":"1","order":1,"showTitle":true,"className":"","visible":"true","disabled":"false"},{"id":"3e5a7def77e29cf0","type":"ui-page","name":"texte","ui":"9d35493ff7cdb9d8","path":"/texte","icon":"home","layout":"grid","theme":"723f3a378be587ae","order":1,"className":"","visible":"true","disabled":"false"},{"id":"9d35493ff7cdb9d8","type":"ui-base","name":"My Dashboard","path":"/dashboard","includeClientData":true,"acceptsClientConfig":["ui-text"],"showPathInSidebar":false,"showPageTitle":true,"navigationStyle":"default","titleBarStyle":"default"},{"id":"723f3a378be587ae","type":"ui-theme","name":"Default Theme","colors":{"surface":"#ffffff","primary":"#0094ce","bgPage":"#eeeeee","groupBg":"#ffffff","groupOutline":"#cccccc"},"sizes":{"pagePadding":"12px","groupGap":"12px","groupBorderRadius":"4px","widgetGap":"12px"}}]

```

home assistant addon configuration

```auto
theme: default
http_node:
  username: patrick
  password: xxxxxx
http_static:
  username: patrick
  password: cxxxx
ssl: true
certfile: fullchain.pem
keyfile: privkey.pem
system_packages: []
npm_packages: []
init_commands: []
log_level: error

```

start-up log

```auto
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 18.0.4
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.4 (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.7.4
 Home Assistant Supervisor: 2024.06.2
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to ERROR
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started

up to date, audited 163 packages in 4s

16 packages are looking for funding
  run `npm fund` for details

```

est ce que quelq'un a la derniere version de nodered v4.0.2

```auto
found 0 vulnerabilities
npm notice
npm notice New minor version of npm available! 10.7.0 -> 10.8.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.2
npm notice To update run: npm install -g npm@10.8.2
npm notice
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

```

url dashboard

`https://xxxxx.duckdns.org/a0d7b954_nodered/ingress`

---

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [5 August 2024 16:16 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/87 "2024-08-05T16:16:56Z")

</div>

@patrickL I am afraid the right people are not going to see this post burried at the bottom of this old Node-RED v4.0.0 release post.

Please start a new post in the #Dashboard category and add the tag #dashboard-2

Also add a description of the problem (currently you only have a bunch of logs). Perhaps a screenshot would help too.

---

<div class="post-metadata">

### Author: ![patrickL](https://avatars.discourse-cdn.com/v4/letter/p/65b543/32.png) [@patrickL](https://discourse.nodered.org/u/patrickL)
#### Post date: [8 August 2024 17:54 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/88 "2024-08-08T17:54:09Z")

</div>

thank you your response

so y do it now

---

<div class="post-metadata">

### Author: ![rromele](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rromele/32/18431_2.png) [@rromele](https://discourse.nodered.org/u/rromele)
#### Post date: [25 September 2024 22:01 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/89 "2024-09-25T22:01:19Z")

</div>

I upgraded to v4.0.3  
Some nodes are not compatible (PCCC, Telegram, etc.)  
Are there any solutions?

How to get back to Vers. 3?

25 Sep 23:11:44 - [info] Node-RED version: v4.0.3  
25 Sep 23:11:44 - [info] Node.js version: v20.17.0  
25 Sep 23:11:44 - [info] Windows\_NT 10.0.19045 x64 LE  
25 Sep 23:11:45 - [info] Loading palette nodes  
[…..]  
**25 Sep 23:03:27 - [info] Waiting for missing types to be registered:**  
25 Sep 23:03:27 - [info] - node-red-contrib-whatsapp-cmb-account  
25 Sep 23:03:27 - [info] - telegrambot-config  
25 Sep 23:03:27 - [info] - pccc endpoint  
25 Sep 23:03:27 - [info] - pccc out  
25 Sep 23:03:27 - [info] - pccc in

 ![nred](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/8/c885729db74cc29414810e7c5a0f76d376a2c6e8.jpeg)

2024-09-25T21:12:48.057Z Install : node-red-contrib-pccc 1.0.2  
2024-09-25T21:12:52.144Z [err] npm error notsup Required: {"node":"8.x || 10.x"}  
2024-09-25T21:12:52.144Z [err] npm error notsup Actual: {"npm":"10.8.3","node":"v20.17.0"}

---

<div class="post-metadata">

### Author: ![softy2k](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/softy2k/32/23707_2.png) [@softy2k](https://discourse.nodered.org/u/softy2k)
#### Post date: [26 September 2024 07:58 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/90 "2024-09-26T07:58:07Z")

</div>

**Telegram** is compatible with **NodeRed 4.0.3** and **NodeJs 20.17.0** , Windows and Linux

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [26 September 2024 08:59 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/91 "2024-09-26T08:59:49Z")

</div>

> [@rromele](#):
>
> 2024-09-25T21:12:48.057Z Install : node-red-contrib-pccc 1.0.2  
> 2024-09-25T21:12:52.144Z [err] npm error notsup Required: {"node":"8.x || 10.x"}  
> 2024-09-25T21:12:52.144Z [err] npm error notsup Actual: {"npm":"10.8.3","node":"v20.17.0"}

It isn't the fact that you have upgraded node red that is causing the problem, but the fact that you have upgraded nodejs, but have not updated the nodes to their latest versions.

In your .node-red folder remove the node\_modules folder and the file package.json.lock. Then in a command window go into that folder and run  
`npm install`  
which will install the latest versions of all the nodes. Then you will know whether you have a real problem.  
If there are no errors then restart node-red.

---

<div class="post-metadata">

### Author: ![softy2k](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/softy2k/32/23707_2.png) [@softy2k](https://discourse.nodered.org/u/softy2k)
#### Post date: [26 September 2024 10:34 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/92 "2024-09-26T10:34:04Z")

</div>

Also, go to **.node-red** folder an run command `npm rebuild`

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [26 September 2024 20:13 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/93 "2024-09-26T20:13:48Z")

</div>

> [@softy2k](#):
>
> npm rebuild

Since the node\_modules folder has been removed and all packages have been re-installed, there is no need to rebuild. Normally, after a nodejs upgrade, it is only necessary to rebuild, but in this case some packages had not been updated to the latest versions before upgrading nodejs, so the easiest way is to get rid of them and re-install.

---

<div class="post-metadata">

### Author: ![rromele](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rromele/32/18431_2.png) [@rromele](https://discourse.nodered.org/u/rromele)
#### Post date: [26 September 2024 22:05 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/94 "2024-09-26T22:05:26Z")

</div>

Thank you for your help.  
To solve it I had to delete the entire .node-red folder.  
Reinstall node-red and install all the nodes needed by my application updated.  
Now everything is working  
Thank you very much

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [27 September 2024 09:27 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/95 "2024-09-27T09:27:49Z")

</div>

> [@rromele](#):
>
> To solve it I had to delete the entire .node-red folder.  
> Reinstall node-red and install all the nodes needed by my application updated.

You did not _need_ to do all that. Did the procedure I suggested not work?

---

<div class="post-metadata">

### Author: ![rromele](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rromele/32/18431_2.png) [@rromele](https://discourse.nodered.org/u/rromele)
#### Post date: [27 September 2024 20:23 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/96 "2024-09-27T20:23:30Z")

</div>

Unfortunately the procedure did not work correctly.  
Surely I did something wrong.  
Soon I will have to update other machines, and I will try again.  
Thanks again  
R.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [27 September 2024 21:03 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/97 "2024-09-27T21:03:32Z")

</div>

> [@rromele](#):
>
> Unfortunately the procedure did not work correctly.

On the next system, if you get problems, then come back and tell us what happened.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [26 November 2024 21:04 UTC](https://discourse.nodered.org/t/node-red-4-0-released/88815/98 "2024-11-26T21:04:21Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/node-red-4-0-released/88815.md?page=4)
