node-red-contrib-arcus-orchestration
v1.0.4
Published
Node-RED nodes for Arcus Orchestration
Maintainers
Readme
node-red-contrib-arcus-orchestration
Arcus Orchestration is a collection of Node-RED nodes for asset management workflows. It fetches market data, checks signals, simulates OpenADR events, and decides when to shut down or bypass assets based on configurable criteria.
This Node-Red library packages the functionality needed for asset orchestration withing the Arcus hub environment.
All rights Reserved to ArcusPower.
Copyright Arcus Power 2025. All rights reserved
Maintainers: -Javier Vite -Patrick Bye
Licensed as AGPL-3.0-only
Install
npm install node-red-contrib-arcus-orchestrationThen restart Node-RED and you will see the Arcus nodes in the palette.
Nodes
- Datahub: Fetch data from the Arcus/NRGStream API with token handling, CSV/JSON parsing, and date range options.
- Asset-availability: Retrieve availability data and flag accepted offers to bypass event checks.
- Signal-buffer: Delay shutdown decisions to prevent rapid cycling.
- openadr-listener / openadr-simulator: Receive or simulate OpenADR events.
- shutdown-config / asset-config: Configuration nodes for shutdown and asset parameters.
- oadr-check, demand-check, realtime-price-check, forecast-price-check: Condition evaluators.
- warmup-cooldown: Manage warmup/cooldown timing.
- shutdown-decision-combiner: Merge multiple shutdown decisions.
- event-signal: Central decision node that applies configured rules and respects accepted-offer bypass flags.
Basic use
- Use Datahub to pull market data (CSV or JSON).
- Feed results into Asset-availability to detect accepted offers (sets
bypassEventSignal). - Pass through event-signal to decide shutdowns; optionally add individual check nodes before it.
- Buffer shutdown decisions with Signal-buffer and forward to your control system.
Publish checklist
namestarts withnode-red-contrib-andkeywordsincludenode-red.node-redsection maps each node to its.jsfile.- README present (this file) so the Node-RED library listing renders correctly.
- Only the whitelisted files are published (see
filesinpackage.json); confirm withnpm pack --dry-runbefore publishing. - Build step runs before publish and ships obfuscated JS from
dist:npm install npm run build # creates dist with minified JS and copied html/payload npm pack --dry-run # verify contents npm publish --access public
