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 fully managed Node-RED cloud environment designed to help you build workflows quickly:

• Integrated MQTT server (Mosquitto) for seamless IoT integration.
• Full access to the Node-RED admin interface for managing your flows and settings.
• Node-RED Dashboard included for real-time visualisation.
• Dedicated SMTP email server included, with no sending limits.
• Effortless one-click updates to keep your instance up to date.
• Custom domain names with automatic HTTPS: for example, https://node-red.your-company.com.
• High performance and enhanced security thanks to private, dedicated infrastructure.

You can have a secure, production-ready Node-RED cloud hosting instance running in around 5 minutes. Stackhero takes care of installation, updates, and infrastructure, so you can focus on building your automations.

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.