node-red-contrib-escape-arc

Node-RED nodes for Automation Room Control (ARC). Use them to watch live game activity and trigger ARC actions from your flows.

Detailed release notes are in CHANGELOG.md.

What You Need

• Node-RED 2.0+
• ARC Core running and reachable on your network
• ARC connection node-red enabled in Settings -> Connections

Install

# Palette Manager (recommended)
node-red-contrib-escape-arc

# CLI
cd ~/.node-red
npm install node-red-contrib-escape-arc

Restart Node-RED after install.

Quick Start

1. Add an ARC Config node and set the ARC host (computer name or IP).
2. Add an input node (ARC Timer, ARC State, or ARC Objective) and pick your game.
3. Add an ARC Output node to send actions back to ARC.
4. Deploy and test.

Example action message:

msg.action = {
  type: "send_message",
  targets: ["display-main"],
  format: "text",
  text: "Welcome team!",
  durationMs: 12000
};
return msg;

Nodes

| Node | What it does | | --- | --- | | ARC-config | Shared ARC connection settings and game list lookup. | | ARC-input | Streams all ARC events, with optional filtering. | | ARC-state | Emits game state changes for one game. | | ARC-timer | Emits timer updates every N seconds or at thresholds. | | ARC-objective | Emits objective lifecycle events (activate, complete, reset, fail). | | ARC-output | Sends ARC actions, display commands, or custom events. | | ARC-boolean | Converts messages into a simple true/false match result. |

Output Modes

• ARC action: Send game.action messages (or use a preset action).
• Display command: Send display control commands.
• Custom event: Send your own custom event and payload.

Notes

• ARC host defaults are 127.0.0.1 and port 3000.
• The ARC path is fixed by this package.

Release Notes

See CHANGELOG.md.