Skip to content
GitHub

HotLoop Flow 2.9.0 release notes

HotLoop Flow 2.9.0 adds native connector nodes for a real plant migration. It runs the Node-RED nodes a plant’s flows lean on, Modbus, the dashboard, PostgreSQL and e-mail, plus the Buffer and setInterval the function nodes around them call. A flow captured from a Node-RED box that uses them loads, runs and saves unchanged. It also lets one Flow keep a tab for each machine on a box whose one port carries a VLAN for each, even when every VLAN has the same subnet and the same device addresses.

  • Node-RED Modbus. modbus-client, modbus-read, modbus-getter, modbus-flex-getter, modbus-write, modbus-flex-write, modbus-server, and the passive modbustcp-server. The output is what the community nodes send: msg.payload as the list of values, msg.responseBuffer as {data, buffer}, msg.input, and errors out the second output.
  • The dashboard. ui_base, ui_tab, ui_group, ui_link, ui_spacer, ui_text, ui_numeric, ui_button, ui_switch, ui_text_input, ui_led, ui_gauge, ui_chart and ui_template, served at /ui from the binary, with nothing fetched from outside the plant. What an operator does on the page comes out of the node as a message. ui_template runs the AngularJS-style subset plants use: {{ }}, ng-click, ng-class, ng-init, ng-show, ng-hide, ng-if, ng-bind, scope.$watch, scope.send.
  • PostgreSQL. postgreSQLConfig and postgresql. The connection opens on the first query, so a database that is not up yet does not stop the flow.
  • E-mail. The e-mail output node over SMTP, with STARTTLS, a certificate switch and XOAUTH2.
  • Buffer, setInterval and setTimeout in the function node. The timers run on the node’s clock, every callback has the same CPU limit as a message, and every timer is cleared when the flow stops or is redeployed.
  • A network interface for every client. A node, a tab or a client config can name the interface its connections bind to (SO_BINDTODEVICE), so a tab for dryer 14 reaches only VLAN 14’s 192.168.1.5. The tab way is the environment variable FLOW_NETWORK_INTERFACE on the tab, which every client node on it inherits. It is on the Modbus, PostgreSQL, e-mail, TCP request, UDP out and HTTP request nodes.

The README has a new section, docs/node-red-types.md says what runs and how it differs, and docs/compatibility.md is regenerated from the registry.

  • The function node had Buffer, setTimeout and setInterval absent on purpose, and two tests pinned that. They are present now, because a plant’s functions use them. Nothing else about the sandbox changed: there is still no require, no process and no Node standard library.
  • With the hook unset it behaves as the upstream does. NOTICE and HOTLOOP_PATCH.txt say what changed.
  • The reason is the native Node-RED connector nodes for a real plant migration.
  • HOTLOOP_FLOW_UI_PATH, default /ui: where the dashboard is served.
  • FLOW_NETWORK_INTERFACE, a tab, subflow or process environment variable: the interface that tab’s clients bind to. Empty by default, which lets the host choose, as before.
  • A Network interface field on each client node and config.
  • Chart value bindToInterface.netRaw, default false. Binding a socket to an interface takes no capability on Linux 5.7 and later. On an older kernel it takes CAP_NET_RAW, and setting this to true adds that one capability to the pod and nothing else. The pod also needs the host’s network (network.mode: host) to see a VLAN interface.

A plain helm upgrade to the 2.9.0 image and chart, or the new tag in your Quadlet unit. Nothing happens on first start, nothing needs migrating, and a flow that used none of the new types runs as it did. A flow that already has these types in it (a captured Node-RED file) now starts them where it used to report each one as an unknown node type.

NOTICE gains the Modbus library’s entry, which is now a modified copy. No new third-party module is in the image.

Image: ghcr.io/hotloop-io/hotloop-flow:2.9.0, linux/amd64 first, with arm64 following in 2.9.1. Chart: https://hotloop.io/hotloop-flow/. The README at this tag has the rest, with pictures: https://github.com/HotLoop-io/hotloop-flow/blob/v2.9.0/README.md