Ignition integrates with Node-RED

Ignition and Node-RED complement each other in industrial automation architectures. Ignition provides the robust SCADA foundation with enterprise features while Node-RED offers rapid prototyping and specialized protocol connectivity.

Integration architecture

Common integration patterns include:

• MQTT: Node-RED publishes sensor data to Mosquitto; Ignition's MQTT Engine subscribes
• REST API: Node-RED's HTTP nodes call Ignition's Web Development module endpoints
• Database: Both platforms read/write to shared SQL database for state synchronization
• OPC UA: Node-RED's OPC UA nodes connect to Ignition's built-in OPC UA server

Use cases

• Protocol bridging: Node-RED handles niche protocols (Modbus RTU over serial, proprietary APIs) and normalizes to MQTT for Ignition
• Rapid prototyping: Test automation logic in Node-RED before implementing in Ignition's more robust environment
• Edge preprocessing: Node-RED on edge gateways filters and aggregates data before forwarding to central Ignition
• Custom integrations: Node-RED connects to cloud services, social media, or business APIs not natively supported by Ignition

Configuration overview

1. Choose integration method based on latency and reliability requirements
2. For MQTT: Configure Node-RED MQTT out node → Mosquitto broker → Ignition MQTT Engine
3. For REST: Enable Ignition Web Development module; configure Node-RED HTTP request nodes with authentication
4. For database: Create shared tables; use Ignition's SQL Bridge and Node-RED's database nodes

Tradeoffs and considerations

• Reliability: Node-RED's single-threaded nature may struggle with high-throughput scenarios where Ignition excels
• Security: Node-RED's open ecosystem requires careful vetting of third-party nodes in production
• Maintenance: Two platforms to update, backup, and secure
• Skill requirements: Teams need proficiency in both Ignition (Java/Python scripting) and Node-RED (JavaScript)