# How-to update to latest beta? Node-RED 3.0.0-beta DietPi

**URL:** https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165
**Category:** General
**Created:** [20 June 2022 11:00 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165 "2022-06-20T11:00:22Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![homeplayer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/homeplayer/32/12388_2.png) [@homeplayer](https://discourse.nodered.org/u/homeplayer)
#### Post date: [20 June 2022 11:00 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/1 "2022-06-20T11:00:22Z")

</div>

How-to update to latest beta?

I tried;

```auto
cd /mnt/dietpi_userdata/node-red/
sudo systemctl stop node-red
sudo npm install -g --unsafe-perm node-red@next
sudo systemctl start node-red

```

seen this line "[https://registry.npmjs.org/@node-red/editor-client/-/editor-client-3.0.0-beta.3.tgz](https://registry.npmjs.org/@node-red/editor-client/-/editor-client-3.0.0-beta.3.tgz) 34711"  
on a http fetch status 200 ( got the latest release)

the output is;  
removed 6 packages, changed 294 packages, and audited 295 packages in 3m

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

found 0 vulnerabilities  
npm notice  
npm notice New minor version of npm available! 8.10.0 -\> 8.12.2  
npm notice Changelog: [Release v8.12.2 · npm/cli · GitHub](https://github.com/npm/cli/releases/tag/v8.12.2)  
npm notice Run npm install -g npm@8.12.2 to update!  
npm notice

after starting Node-Red still on Version 2.2.2

---

<div class="post-metadata">

### Author: ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [20 June 2022 11:16 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/2 "2022-06-20T11:16:20Z")

</div>

Its not very clear what command you run to install it.  
From what you have shared .. Stopping and starting the service will not update it.

In the top post of the [Node-RED 3.0.0-beta.3 released](https://discourse.nodered.org/t/node-red-3-0-0-beta-3-released/64027#installing-the-beta-4) thread it mentions how to install it.

```auto
sudo npm install -g --unsafe-perm node-red@next

```

Is this command what you tried ?

---

<div class="post-metadata">

### Author: ![homeplayer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/homeplayer/32/12388_2.png) [@homeplayer](https://discourse.nodered.org/u/homeplayer)
#### Post date: [20 June 2022 11:18 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/3 "2022-06-20T11:18:41Z")

</div>

oops yeah this what i did, made a copy past error in my post

```auto
` 278 cd /mnt/dietpi_userdata/node-red/
  279 systemctl stop node-red
  280 sudo systemctl stop node-red
  281 sudo npm install -g --unsafe-perm node-red@next
  282 sudo systemctl start node-red
`

```

---

<div class="post-metadata">

### Author: ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [20 June 2022 11:22 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/4 "2022-06-20T11:22:05Z")

</div>

what do you get when you run  
`npm list -g node-red`

---

<div class="post-metadata">

### Author: ![homeplayer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/homeplayer/32/12388_2.png) [@homeplayer](https://discourse.nodered.org/u/homeplayer)
#### Post date: [20 June 2022 11:23 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/5 "2022-06-20T11:23:22Z")

</div>

> [@UnborN](#):
>
> npm list -g node-red

```auto
dietpi@server01:~$ npm list -g node-red
/usr/local/lib
└── node-red@3.0.0-beta.3

npm notice
npm notice New minor version of npm available! 8.10.0 -> 8.12.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.12.2
npm notice Run npm install -g npm@8.12.2 to update!
npm notice

```

---

<div class="post-metadata">

### Author: ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [20 June 2022 11:25 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/6 "2022-06-20T11:25:27Z")

</div>

it seems to be installed .. have you tried clearing your browser's Cache files

---

<div class="post-metadata">

### Author: ![homeplayer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/homeplayer/32/12388_2.png) [@homeplayer](https://discourse.nodered.org/u/homeplayer)
#### Post date: [20 June 2022 11:31 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/7 "2022-06-20T11:31:20Z")

</div>

Yep, I did using Brave and Chrome both still show 2.2.2

installed Firefox, it to shows version 2.2.2

---

<div class="post-metadata">

### Author: ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [20 June 2022 11:48 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/8 "2022-06-20T11:48:23Z")

</div>

1. Are you running in Docker ?

2. If you stop the service `sudo systemctl stop node-red` and  
just run it from terminal with `node-red` what do you get ?

---

<div class="post-metadata">

### Author: ![homeplayer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/homeplayer/32/12388_2.png) [@homeplayer](https://discourse.nodered.org/u/homeplayer)
#### Post date: [20 June 2022 11:54 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/9 "2022-06-20T11:54:43Z")

</div>

> [@UnborN](#):
>
> sudo systemctl stop node-red

OMG, thats it, I guess i have node red installed twice now,  
20 Jun 13:49:18 - [info] Node-RED version: v3.0.0-beta.3  
beta 3 is up and running, no flows fresh install.

so i guess this is not the way to update on Dietpi  
this did a install in User directory : /home/dietpi/.node-red

and not in /mnt/dietpi\_userdata/node-red/

---

<div class="post-metadata">

### Author: ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [20 June 2022 14:33 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/10 "2022-06-20T14:33:39Z")

</div>

I might be wrong, and I don't immediately see a definitive answer in the documentation, but (not actually on a DietPi) to install a node-red version it's apparently

```auto
cd ~
sudo npm install -g --unsafe-perm node-red@next

```

whereas to install a specific version of a node it would be

```auto
cd ~/.node-red
npm i node-red-dashboard@2.24.1-beta

```

No idea why one needs cd ~/.node-red while the other needs sudo, nor about DietPi mount points.

---

<div class="post-metadata">

### Author: ![homeplayer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/homeplayer/32/12388_2.png) [@homeplayer](https://discourse.nodered.org/u/homeplayer)
#### Post date: [21 June 2022 15:15 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/11 "2022-06-21T15:15:08Z")

</div>

not using the -g tag, this will work

```auto
systemctl stop node-red
cd /mnt/dietpi_userdata/node-red
sudo -u nodered npm i --no-audit node-red@next
systemctl start node-red

```

---

<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: [5 July 2022 15:15 UTC](https://discourse.nodered.org/t/how-to-update-to-latest-beta-node-red-3-0-0-beta-dietpi/64165/12 "2022-07-05T15:15:39Z")

</div>

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