Node-RED: Node Version in Palette Manager is Older Compared to the NPM One

This documentation is part of the Getting Started guide. You can view the complete guide here: How to Get Started with Node-RED.

👋 Welcome to the Stackhero documentation!

Stackhero offers a ready-to-use Node-RED cloud solution that provides a host of benefits, including:

• MQTT server included (Mosquitto).
• Full access to Node-RED admin UI.
• Node-RED Dashboard included.
• Unlimited and dedicated SMTP email server included.
• Effortless updates with just a click.
• Customisable domain name secured with HTTPS (for example, https://node-red.your-company.com).
• Optimal performance and robust security powered by a private and dedicated VM.

Save time and simplify your life: it only takes 5 minutes to try Stackhero's Node-RED cloud hosting solution!

If you try to install a node using the Palette Manager but notice that the version is older than the one on NPM, it likely means that the node's creator has not updated the version on the Node-RED website.

Previously, node versions were automatically updated to reflect the version published on NPM. This is no longer the case.

The good news is that you can prompt the Node-RED website to refresh the version. Simply go to https://flows.nodered.org/add/node, enter the NPM module name (for example, node-red-contrib-xxx), and click the "Add" button. Once completed, return to your Node-RED dashboard and open the Palette Manager. The updated version should now be visible and ready for installation.