node-red-contrib-opcua-connector-manager 1.0.1
Node-RED sidebar panel to bulk-reassign any config node references across all flows — ideal when promoting from dev to prod.
node-red-contrib-opcua-connector-manager
A Node-RED sidebar panel that lists every config node reference across all flow tabs and lets you bulk-reassign them in one shot — useful when promoting flows from dev to prod.
Despite the name it works with any config node type: OPCUA connectors, MQTT brokers, HTTP request configs, database connections, whatever.
Features
- Sidebar panel — always accessible via the ⇄ icon, no node placement needed
- Config-type selector — pick any type that actually exists in the workspace
- Per-instance cards, each showing:
- Name and detail line (endpoint URL, broker address, host…)
- Flow-tab pills with per-flow node counts
- Replace with dropdown
- Bulk apply — one click to reassign all referencing nodes, then Deploy to save
- Stale-reference detection — highlights nodes pointing to deleted config nodes
Requirements
- Node-RED ≥ 3.0.0
- Node.js ≥ 18.0.0
Installation
npm
cd ~/.node-red
npm install node-red-contrib-opcua-connector-manager
Docker
COPY nodes/ /opt/nr-local-nodes/
RUN npm install /opt/nr-local-nodes/node-red-contrib-opcua-connector-manager
Usage
Open the ⇄ tab in the Node-RED right sidebar. That's it.
- Pick a config node type from the dropdown at the top.
- Each card is one config node instance. The flow pills show you exactly where it's used.
- Set Replace with on the cards you want to change.
- Click Apply Changes, then Deploy.
You can also drop the Config Node Mgr node from the Connector Manager palette onto any flow — double-clicking it opens the sidebar automatically.
Dev → Prod example
Say you have two OPCUA connectors:
| Config node | Endpoint |
|---|---|
| OPC Server – Dev | opc.tcp://dev-plc:4840 |
| OPC Server – Prod | opc.tcp://10.0.1.5:4840 |
Open the panel, select OPCUA-IIoT-Connector, set Replace with to OPC Server – Prod on the dev card, click Apply, Deploy. Done.
Example flow
Import examples/config-node-manager.json via ☰ → Import.