RnD/EVOLV
3
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity
Page: Manual NodeRED Messages And Editor Structure
Pages
Archive Home
Clone
2
Manual NodeRED Messages And Editor Structure
znetsixe edited this page 2026-05-11 22:24:29 +02:00
Table of Contents

Node-RED Messages and Editor/Runtime Structure (EVOLV Summary)

code-ref type

Note

Reference page. Maintained for context; not regenerated by code. See Home for current top-level navigation.

Sources:

Message Shape

  • Standard message object is usually msg.
  • msg.payload is the default value channel.
  • msg.topic is used for routing/intent labeling.

EVOLV Topic Routing

  • EVOLV runtime wrappers route commands by msg.topic in src/nodeClass.js.
  • Keep topic names stable unless a migration is defined (flow compatibility).

Editor/Runtime Parity

  • In .html, RED.nodes.registerType(... defaults ...) defines persisted config fields.
  • Runtime parser in src/nodeClass.js must read and normalize the same fields.
  • If a field is added/renamed in editor defaults, update runtime mapping and tests in the same change.

Multi-Output Node Rule

  • Runtime node.send([out1, out2, out3]) must align with declared outputs in .html.
  • If output meaning is process, dbase, parent, maintain stable index mapping across all message paths.

EVOLV Wiki

Start here

Reference

Per-node wikis

Domain concepts

Operations findings

Node-RED / FlowFuse manuals

Archive