# Updating of installed nodes

**URL:** <https://discourse.nodered.org/t/updating-of-installed-nodes/58587>\
**Category:** Feature Requests\
**Created:** [18 February 2022 09:48 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587 "2022-02-18T09:48:01Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [18 February 2022 09:48 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587/1 "2022-02-18T09:48:01Z")

</div>

Add a feature to "update all" nodes that have a newer version available. If you have many nodes, the administration will be massive, especially if you think about having NR in commercial production/products

From other areas I know this as "fleet management". An example I have personal experience with is a portal where we manage thousands of routers and they do fw updates from time to time. Having to do this manually per router would be "almost impossible", at least very costly

Ideally a manually activated feature "update all nodes" and eventually a NR setting "automatic updating of nodes" that would happen as soon as a new version is available

---

<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:** [18 February 2022 09:57 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587/2 "2022-02-18T09:57:41Z")

</div>

Hi Walter, already on backlog: [Trello](https://trello.com/c/TY8mtcZ2)

---

<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:** [18 February 2022 10:00 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587/3 "2022-02-18T10:00:49Z")

</div>

> [@krambriw](#):
>
> a NR setting "automatic updating of nodes" that would happen as soon as a new version is available

Are you sure you want your thousands of systems to be automatically updated before you have a chance to check that your s/w works with the new versions of nodes? Remember sometimes new versions have bugs, or even breaking changes that need you to change your flows.

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [18 February 2022 10:08 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587/4 "2022-02-18T10:08:07Z")

</div>

Well, maybe not but the possibility to select all, I would like

---

<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:** [18 February 2022 10:09 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587/5 "2022-02-18T10:09:32Z")

</div>

If you want the feature immediately then you could use an Exec node and run the appropriate npm command in the exec node, then force a restart of node-red.

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [18 February 2022 10:14 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587/6 "2022-02-18T10:14:10Z")

</div>

OK, yes, that is an option of course, thanks!

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [18 February 2022 10:19 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587/7 "2022-02-18T10:19:39Z")

</div>

Hi Steve, I'm getting a bit confused about where all feedback should be given. For this forum part it is stated _A place to make suggestions for new features in Node-RED_

Then you have Trello as mentioned. As well as github for Node-RED with reported issues where I see many "good things" contributed in the issue list that is not listed in Trello

Very confusing

Where should we put feedback in order to get the highest impact and possible seen by those who need to see them??

---

<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:** [18 February 2022 10:46 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587/8 "2022-02-18T10:46:45Z")

</div>

> [@krambriw](#):
>
> Where should we put feedback in order to get the highest impact and possible seen by those who need to see them??

Trello is being wound down (i believe)  
FRs on github Issues is a new thing & only to be made by the team for now.  
You can make suggestions on SLACK but as it is a realtime messaging platform, I can go unnoticed.

Therefore, here is the best place (IMO).

---

<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:** [19 April 2022 10:47 UTC](https://discourse.nodered.org/t/updating-of-installed-nodes/58587/9 "2022-04-19T10:47:28Z")

</div>

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