# Upgrade Node-RED from Node.js 16.20.2 to 18.x or 20.x

**URL:** <https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224>\
**Category:** Développement\
**Created:** [December 6, 2024, 4:44pm UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224 "2024-12-06T16:44:55Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\
**Post date:** [December 6, 2024, 4:44pm UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/1 "2024-12-06T16:44:55Z")

</div>

Hello,

A quick poll to see whether it would be a problem for you to upgrade Node-RED with Node.js to version 18.x or 20.x  
We are on Node.js version 16.20.x, which reached EOL in September 2023

> **[Supported Node versions : Node-RED](https://nodered.org/docs/faq/node-versions)**

> **[Release Plan : Node-RED](https://nodered.org/about/releases/)**

> **[Node.js](https://endoflife.date/nodejs)**
>
> Check end-of-life, release policy and support schedule for Node.js.

I would have needed at least Node.js 18 for this plugin and for retrieving the Tempo tariffs from a PDF: (Ultimately no longer needed 🙂 )

> [@\[TUTO\] Mise à jour du tarif TEMPO](https://community.gladysassistant.com/t/tuto-mise-a-jour-du-tarif-tempo/9218):
>
> Bonjour la Team, suite à la mise en place du [Tuto - Domotiser son lave linge avec une prise connectée](https://community.gladysassistant.com/t/tuto-domotiser-son-lave-linge-avec-une-prise-connectee/8824) et du [Tuto - Récupérer le prix de son abonnement d'électricité via le site data.gouv.fr](https://community.gladysassistant.com/t/tuto-recuperer-le-prix-de-son-abonnement-delectricite-via-le-site-data-gouv-fr/8838) de @prohand , j’ai eu besoin de modifier la récupération du coût de l’électricité pour mon abonnement TEMPO. Voici le résultat sur mon dashboard : Je n’ai rien trouvé en opendata qui aurait pu être intégrée via node-red donc je suis passé par des scènes et les tarifs sont «&nbsp;en…

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 14, 2025, 10:04am UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/2 "2025-02-14T10:04:44Z")

</div>

Hi @prohand,

I’m bringing this topic up again, because indeed it would be good to update.

The problem is that this update is, in my opinion, a breaking change.

If we force all instances to update Node-RED, it could break installations, right? And that, I think, we really don’t want 😬

Wouldn’t the solution be to add a Node-RED version selector in the interface of this integration?

---

<div class="post-metadata">

**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\
**Post date:** [February 14, 2025, 10:43am UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/3 "2025-02-14T10:43:12Z")

</div>

I hadn’t responded to the survey because I use quite a few flows in Node-RED, but I have no idea at all about the possible impact of the upgrade… The option might be a good idea. Would that allow testing the upgrade and rolling back if we find that our Node-RED flows are broken?

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 14, 2025, 10:45am UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/4 "2025-02-14T10:45:26Z")

</div>

I don’t know Node-RED well enough to answer you. I don’t think so — if you update and it breaks, you’ll have to fix your flows.

In my opinion, Node-RED doesn’t provide a migration assistant for downgrades…

On the Gladys side, for example, we have migrations in place for upgrades, never for downgrades.

---

<div class="post-metadata">

**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\
**Post date:** [July 16, 2025, 6:33pm UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/5 "2025-07-16T18:33:18Z")

</div>

To get back to the topic, I’ll try to upgrade Node

---

<div class="post-metadata">

**Author:** ![Terdious](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/terdious/32/6316_2.png) [@Terdious](https://community.gladysassistant.com/u/Terdious)\
**Post date:** [July 16, 2025, 8:11pm UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/6 "2025-07-16T20:11:15Z")

</div>

[quote=«&nbsp;prohand, post:5, topic:9224&nbsp;»]

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [July 17, 2025, 6:20am UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/7 "2025-07-17T06:20:10Z")

</div>

@prohand Thanks! In any case, I’m not sure a forced update is possible or desirable. I think we’ll need to add a version selector in the integration interface to switch to a newer version.

In the case of Node-RED, the user uses many third-party plugins that aren’t necessarily all compatible with every version, so it’s up to the user to perform the update, I think.

---

<div class="post-metadata">

**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\
**Post date:** [July 17, 2025, 7:15am UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/8 "2025-07-17T07:15:31Z")

</div>

Indeed, the user should be allowed to choose whether to update or not 🙂

---

<div class="post-metadata">

**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\
**Post date:** [December 20, 2025, 12:41pm UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/9 "2025-12-20T12:41:14Z")

</div>

Hello,

I’m following up on this topic because I realize I didn’t follow up regarding the update.

I just upgraded my Node-RED to version 4.1.2 (Docker)

I had to update some plugins:

![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/8/3/835207d75480436681e59fb33f042e0bbabd5b1c.png)

I had to restart Node-RED one last time to finish updating the plugins

For now everything seems to be working well.  
I’ll keep you posted if I have any problems.

I think the risk of breaking installations is, I believe, limited to the fact that some plugins may no longer be compatible, but we could indeed add a version selector for those who wish to migrate to a newer version.

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [January 5, 2026, 8:29am UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/10 "2026-01-05T08:29:52Z")

</div>

@prohand thanks for your feedback.

If you had done the update without doing anything, would your flows have continued to run?

Because that’s what’s going to happen if we force an update.

---

<div class="post-metadata">

**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\
**Post date:** [January 5, 2026, 8:42am UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/11 "2026-01-05T08:42:20Z")

</div>

Yes, it would have continued to work, I think, but I’m not 100% sure because I haven’t tested it over several days without updating the plugins.

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [January 5, 2026, 1:03pm UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/12 "2026-01-05T13:03:36Z")

</div>

If someone could take this issue and make a PR (and test it, of course), it would help me enormously 🙏

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [June 15, 2026, 3:56pm UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/13 "2026-06-15T15:56:57Z")

</div>

My answer on this topic: a version selector in the Node-RED integration, so we don’t break Node-RED for anyone and the user can, if they wish, update 🙂

> [@Gladys Assistant 4.79 : IA plus maline, assistant vocal amélioré et plus d'appareils Matter](https://community.gladysassistant.com/t/gladys-assistant-4-79-ia-plus-maline-assistant-vocal-ameliore-et-plus-dappareils-matter/10270):
>
> Bonjour à tous, La version v4.79 de Gladys est sortie slight_smilerobot Intelligence artificielle Cette version apporte plusieurs améliorations à l’agent IA : Création de scènes : Correction du schéma + augmentation du timeout pour corriger un bug de création de scène remonté par @GBoulvin et @Jluc. Meilleure gestion des erreurs : des retours plus clairs quand l’IA ne répond pas. Appels d’outils via Telegram : Via Telegram, on voit désormais les appels d’outils comme sur le web

I’m closing this topic!

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [June 15, 2026, 3:57pm UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/14 "2026-06-15T15:57:00Z")

</div>


