Nodes

Nodes page

Energy Flow › Nodes. Every node you added. PDUs and outlets are added automatically and are not listed.

• Add node: id, label, kind.
• Import device template: adds pre-wired nodes and the Modbus connection for a known device (EG4 FlexBoss 21). Check register addresses and scales against your device.
• Fed by sets the feeder from the table.
• Edit opens the node editor. Rename changes the id and keeps its links. Copy duplicates it.
• The bindings column shows a warning when a measured node has no energy (kWh) source.
• Save applies. Bindings apply without a restart.

Node editor

A load cannot feed anything.

Bindings

+ Add binding, pick the metric and the source type. The live value shows at the right of each binding.

Fields on every binding:

• Browse lists topics on the broker, feeds on EmonCMS, or entities in Home Assistant, with current values.
• Direction split: one signed value. Positive is out, negative is in. Grid: out = import, in = export. Battery: out = discharge, in = charge.
• Accumulation: check the topic across midnight. A daily counter drops at midnight; a lifetime counter does not.
• A live reading replaces the node's fixed Value. Negative readings count as 0.
• EmonCMS bindings need EmonCMS.Url and a read API key. EmonCMS.Enabled is not required.
• Home Assistant bindings use HomeAssistant.EnergyDashboard.Url and its token.
• unavailable or non-numeric values supply nothing.

Derived values

A measured reading replaces a derived one. Missing operands give no value.

YAML

EnergyFlow:
  Nodes:
    - Id: solar
      Label: Solar Array
      Kind: solar
      Max: 9600
      Sources:
        - { Type: mqtt, Metric: realpower, Topic: solar_assistant/inverter_1/pv_power/state }
        - { Type: mqtt, Metric: energy, Topic: solar_assistant/total/pv_energy/state }
    - Id: grid
      Label: Grid
      Kind: grid
      Sources:
        - { Type: mqtt, Metric: realpower, Topic: solar_assistant/inverter_1/grid_power/state, Direction: split }
        - { Type: mqtt, Metric: voltage, Topic: solar_assistant/inverter_1/grid_voltage/state }
        - { Type: derived, Metric: current, Direction: split }
    - Id: server_rack
      Label: Server rack
      Sources:
        - { Type: emoncms, Metric: realpower, Feed: 2_power }
  Links:
    - { From: solar, To: main_panel }
    - { From: grid, To: main_panel }

Groups

Energy Flow › Groups. Several nodes drawn as one collapsible node on the flow diagrams. Members keep their own links and exports. The group publishes the sum of members that have data.

• Add group: id, label, kind, then + add member.
• Or turn an existing node into a group: the node becomes the group's anchor (for example Solar PV over its MPPTs).
• Click a group on the Flow diagram to expand it.

EnergyFlow:
  Groups:
    - { Id: downstairs_loads, Label: Downstairs, Kind: load, Members: [kitchen, laundry, fridge] }

Tags

Energy Flow › Tags. Tags filter the diagram and decide what each destination exports. A tag never changes a value.

• Define tag: name and description. Declaring is optional.
• The table lists each tag, what carries it, and which destinations filter on it.
• Tags for PDUs and outlets: rules matched by node id with *, for example outlet:rack_pdu_1:*. Per-PDU and per-outlet tags are on Vertiv rPDU.
• Destination filters: EnergyFlow.MqttExportTags, HomeAssistant.EnergyDashboard.NodeTags, Prometheus.NodeTags, EmonCMS.NodeTags. Exclude wins over Include.

EnergyFlow:
  Tags:
    - { Name: critical, Description: On the UPS }
  AutoTags:
    - { Match: "outlet:rack_pdu_1:*", Tags: [rack] }
  MqttExportTags:
    Include: [critical]