A collection of extra nodes for Node-RED, extending its capabilities with hardware I/O, social APIs, data parsing, and utility functions.
Node-RED Nodes is a collection of additional nodes for the Node-RED flow-based development tool. It extends Node-RED's core capabilities by providing pre-built components for interacting with hardware devices, social media APIs, databases, and various data processing utilities. This allows users to quickly build IoT, automation, and integration workflows without developing custom nodes from scratch.
Node-RED users, IoT developers, and automation engineers who need to integrate with specific hardware, services, or data sources beyond Node-RED's built-in nodes.
It saves development time by offering a wide range of tested, community-maintained nodes for common tasks, reducing the need to write custom JavaScript functions. The modular design allows users to pick only the nodes they need, keeping flows lightweight and maintainable.
Extra nodes for Node-RED
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes nodes for Arduino, Raspberry Pi, BeagleBone, and various sensors like temperature and LEDs, enabling direct IoT integration without custom firmware development.
Provides nodes for Twitter, email, IRC, XMPP, and push notifications (e.g., Pushbullet, Pushover), covering multiple communication platforms for alerts and messaging.
Follows Node-RED's philosophy of single-purpose nodes, allowing users to easily combine components for complex workflows without extensive coding.
Available as individual npm packages, enabling installation via Node-RED's palette manager or command line, making it flexible for different deployment scenarios.
The MySQL node explicitly warns about SQL injection risks in the README, which could compromise applications handling sensitive data without proper safeguards.
Several nodes like NMA are deprecated, and the Twitter node is noted to break soon due to API changes, indicating inconsistent maintenance and potential reliability issues.
Installation from the GitHub repository requires cloning and running npm install in subfolders, which is more cumbersome than standard npm methods and less user-friendly.