node-red-contrib-jsonscada

Node-RED nodes for bidirectional integration with JSON-SCADA over its NODE-RED protocol driver. Drag nodes to move process data in and out of JSON-SCADA — no broker required.

Install

From the Node-RED palette manager, search for node-red-contrib-jsonscada, or:

cd ~/.node-red
npm install node-red-contrib-jsonscada

Requires a running JSON-SCADA NODE-RED driver instance (see src/node-red-driver).

Nodes

| Node | Purpose | |---|---| | jsonscada-server (config) | The shared, auto-reconnecting WebSocket connection to the driver. Set host, port, TLS, and the access token (the connection's password). | | jsonscada tag in | Subscribe to live tag updates (all / by tag / by group1). Emits msg.payload = value, msg.topic = tag, msg.point = full tag object. | | jsonscada tag out | Inject values (single via address + msg.payload, or bulk array). Optionally declares a commandable point. | | jsonscada cmd in | Receive operator commands for points this flow owns; reply with a result. | | jsonscada cmd out | Command any commandable JSON-SCADA tag; second output carries the ack. | | jsonscada read | Request a one-shot snapshot of tags/topics. |

Quick start

1. Add a jsonscada tag out node, create a jsonscada-server config pointing at your driver (default 127.0.0.1:51931), set an Address like PLANT1~LINE2~temperature, and wire an inject/function producing a numeric msg.payload. The tag auto-creates in JSON-SCADA (if autoCreateTags is on).
2. Add a jsonscada tag in node, subscribe by topic PLANT1, and wire a debug node to watch live updates flow back.

Examples

Import from the Node-RED menu → Import → Examples → node-red-contrib-jsonscada:

• 01 ingest — HTTP API → tag out (auto-created tags)
• 02 notify — tag in (alarms) → notification
• 03 actuate — commandable point + cmd in → actuate → result
• 04 command out — buttons commanding a field breaker tag
• 05 raw websocket — the same ingest using only built-in nodes (no palette)

Protocol

These nodes speak the versioned JSON WebSocket protocol documented in the driver's PROTOCOL.md. The config node checks the driver's protocolVersion and reports a mismatch.

License

GPL-3.0-or-later, as part of the JSON-SCADA distribution.