# NodeRed Palette is months behind the NPM package - node-red-contrib-smartlifeair - HELP

**URL:** <https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124>\
**Category:** General\
**Created:** [28 August 2020 00:24 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124 "2020-08-28T00:24:06Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![razorRun](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/razorrun/32/27847_2.png) [@razorRun](https://discourse.nodered.org/u/razorRun)\
**Post date:** [28 August 2020 00:24 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/1 "2020-08-28T00:24:06Z")

</div>

Hey Guys  
I just noticed one of my Nodes still has a very old version(5months old) in NodeRed (NPM is updated several times after that- 12 version updates to be exact with in last 4 months). I am not sure how to update it. Any help is appreciated.

NPM package (0.0.34) - [https://www.npmjs.com/package/node-red-contrib-smartlifeair](https://www.npmjs.com/package/node-red-contrib-smartlifeair)

Node red package (0.0.15) - [https://flows.nodered.org/node/node-red-contrib-smartlifeair](https://flows.nodered.org/node/node-red-contrib-smartlifeair)

In the local node-red palette I see the same version (0.0.15)

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [28 August 2020 01:31 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/2 "2020-08-28T01:31:17Z")

</div>

You have to update _non standard_ nodes yourself.

---

<div class="post-metadata">

**Author:** ![razorRun](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/razorrun/32/27847_2.png) [@razorRun](https://discourse.nodered.org/u/razorRun)\
**Post date:** [28 August 2020 02:02 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/3 "2020-08-28T02:02:26Z")

</div>

What do you mean? Do you mean updating in a node-red instance in the palate or update somewhere else?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [28 August 2020 02:03 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/4 "2020-08-28T02:03:46Z")

</div>

No, you go into the palette manager, scroll to the node, and click update.

You can't expect the people at node red to build in support to update foreign nodes.

---

<div class="post-metadata">

**Author:** ![razorRun](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/razorrun/32/27847_2.png) [@razorRun](https://discourse.nodered.org/u/razorRun)\
**Post date:** [28 August 2020 02:05 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/5 "2020-08-28T02:05:57Z")

</div>

Found the solution.

For future reference.  
Had to log in to [https://flows.nodered.org/node/node-red-contrib-smartlifeair](https://flows.nodered.org/node/node-red-contrib-smartlifeair) and press "Request Refresh" under actions. Looks like that forced to update the cache

---

<div class="post-metadata">

**Author:** ![razorRun](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/razorrun/32/27847_2.png) [@razorRun](https://discourse.nodered.org/u/razorRun)\
**Post date:** [28 August 2020 02:12 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/6 "2020-08-28T02:12:06Z")

</div>

> [@razorRun](#):
>
> Had to log in to [node-red-contrib-smartlifeair (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-smartlifeair) and press "Request Refresh" under actions. Looks like that forced to update the cache

I think we are talking about two things here. 😅 My issue was, I was seeing a very old version of my plugin till I request an update on the [https://flows.nodered.org/node/](https://flows.nodered.org/node/). basically, in the palette manager, it won't show the update option even though NPM package has been updated several times

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [28 August 2020 07:02 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/7 "2020-08-28T07:02:23Z")

</div>

@razorRun we no longer scan for updates to the flow library automatically. This post gives the background: [⚠️Flow Library not detecting updated modules](https://discourse.nodered.org/t/flow-library-not-detecting-updated-modules/25254)

---

<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:** [28 August 2020 07:27 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/8 "2020-08-28T07:27:24Z")

</div>

Could you just clarify for me, does the node-red palette manager get its data on available node versions from the flow library or direct from npmjs?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [28 August 2020 07:48 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/9 "2020-08-28T07:48:54Z")

</div>

The editor loads a JSON catalog of available nodes that is generated by the flow library - this includes the version number.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [28 August 2020 08:38 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/10 "2020-08-28T08:38:36Z")

</div>

> [@Trying\_to\_learn](#):
>
> You can't expect the people at node red to build in support to update foreign nodes.

Just to be clear, node-RED **users** don't have to go through their palette, updating the palette node versions. It should be updated by the contrib node **developer** after they have updated their own contrib node version on npm.

If however, a developer forgets to do so, any user logged into git can also request a refresh of any node.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [28 August 2020 08:48 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/11 "2020-08-28T08:48:54Z")

</div>

Ok, I'm now even more confused than @razorRun.

I have a _swag_ of nodes.

I have NR 1.0.3 or later.

Every now and then I go in and update any often used nodes that are **WAY** behind on updates.

Yet, what you (@Paul-Reed) they are supposed to update themselves?

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [28 August 2020 09:03 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/12 "2020-08-28T09:03:17Z")

</div>

> [@Trying\_to\_learn](#):
>
> they are supposed to update themselves?

We are not talking about actually updating the node in your installation, we are talking about updating the available node version in the node library.  
Then you can update your local installation to the latest version via the palette.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [28 August 2020 09:05 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/13 "2020-08-28T09:05:41Z")

</div>

> [@Paul-Reed](#):
>
> we are talking about updating the available node version in the node library.

I'll put my hand up.

I am not understanding what you mean by that?  
As in: When I look at the nodes, their (the nodes installed) show their latest update and the one installed?

Ok, I saw you just added a bit.

The last line:

> [@Paul-Reed](#):
>
> Then you can update your local installation to the latest version via the palette.

Is what I was meaning to convey.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [28 August 2020 09:21 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/14 "2020-08-28T09:21:13Z")

</div>

Let me give you an example;

As a node developer (I use that term loosely 😝) and I update my Simpletime node on npm from v1 to v2.  
If I forget to update the node library, it will always show up as v1 in your palette, and you will not be able to get v2. Despite npm showing that it has been updated to v2.

Now, if I (or someone else) requests that the node is refreshed in the node library, the library will be then updated, and your palette will then show v2, and allow you to update to that version.

Hope that's clear (I'm replying on my phone, whilst sheltering from rain under a tree!)

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [28 August 2020 09:29 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/15 "2020-08-28T09:29:02Z")

</div>

Thanks. I don't fret too much on it and I just popped in to this thread in an attempt to help with how to update the node.

If it was thunderstorms, I would suggest you don't shelter under a tree.  
If hit by lightning, they tend to explode.

---

<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:** [11 September 2020 09:29 UTC](https://discourse.nodered.org/t/nodered-palette-is-months-behind-the-npm-package-node-red-contrib-smartlifeair-help/32124/16 "2020-09-11T09:29:11Z")

</div>

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