HotLoop Flow 2.13.0 release notes
HotLoop Flow 2.13.0 tells people and Kafka things, finishes more of FlowLab, and stops a deploy from restarting a run that did not change. It adds five nodes that send what a message carries (ntfy, Gotify, a Discord webhook, a Discord bot, Kafka), an intensity chart, flow control on the serial port, and diagram tests you can run in CI. Nothing you have changes unless you use the new parts, except that a deploy no longer restarts a diagram you did not touch.
What’s new
Section titled “What’s new”- Notification nodes.
ntfy out,gotify out,discord out(a webhook) anddiscord bot out, with config nodes that take the same settings HotLoop core sends its alarms with: an ntfy server and a token or a login (or neither for a server that lets anyone publish), a Gotify application token, a Discord webhook URL, a Discord bot token and a channel. They sendmsg.payload, take a title, topic, priority, channel or color from the node or from the message when the node leaves it empty, and pass the message on. A secret is in no error, status or log: a Discord webhook URL is the whole credential, an ntfy topic on a public server is one too, and even a network error that names the address is cleaned. A refusal keeps the server’s own reason. A rate limit is waited out once, as long as the server asks and no longer than a minute, and then the message fails. Discord content is cut at 2,000 characters and an embed’s description at 4,096, counted the way Discord counts them, and nothing in a message can ping anyone. No Slack and no Teams. - Kafka out.
kafka outwith ahotloop-flow-kafkaconfig node: brokers, SASL PLAIN or SCRAM-SHA-256 or SCRAM-SHA-512, TLS. It producesmsg.payloadto a topic with an optional key, as text or as JSON when it is not text, and passes the message on once the cluster has acknowledged it from every in-sync replica. It uses franz-go, the client HotLoop core’s Kafka output uses, so anything that speaks the Kafka API answers it. - Intensity chart. A chart’s mode can be
intensity. It takes an array of rows of numbers, up to 512 by 512, draws each value as a color from the smallest to the largest, and replaces the picture with each grid. A flat or ragged array is an error on the node’s error wire. - Serial flow control.
dia-serial-openhas aflowsetting (none, rtscts, xonxoff), and aserial://instrument address takesflow=. It is set on the terminal after the port opens, so a port that is opened again after a pulled cable gets it again, and none clears what another program left on. Linux only: on any other system a diagram that asks for more than none is refused instead of run without it. - Diagram tests. A flow test file can hold a test of a FlowLab diagram: set its controls by label or id, run it once, and check its indicators (a number to a millionth, or
{min, max}). A diagram with a node that would reach outside the test (a serial port, an instrument, a data acquisition device, MQTT out, a HotLoop write, a log file) is refused.
What changed
Section titled “What changed”- A deploy keeps a run that did not change. A deploy used to stop every diagram run and start the autostart ones again, so deploying anything restarted a plant’s logger. A run now goes on when its diagram, every body it runs and every config node are exactly what they were. Where a node is drawn is not part of that, so moving a node on the canvas never restarts anything. A diagram that did change is stopped and, if it autostarts, started again, as before.
- The Flow chart carries
artifacthub.io/license: LicenseRef-EmberNet-Source-1.0. - Nothing else behaves differently from 2.12.1. The editor and the panel are the same everywhere you do not use the new nodes, the intensity mode, flow control or a diagram test, which is what a before and after inventory of the editor on one fixed flow shows.
New settings
Section titled “New settings”None in the config file or the environment. New nodes: ntfy out, gotify out, discord out, discord bot out, kafka out, and the config nodes hotloop-flow-ntfy, hotloop-flow-gotify, hotloop-flow-discord-bot and hotloop-flow-kafka. New properties: flow on dia-serial-open, and the intensity value of a chart’s mode.
Upgrade
Section titled “Upgrade”A plain helm upgrade to the 2.13.0 image and chart, or the new tag in your Quadlet unit. Nothing happens on first start and nothing needs migrating. The new dependency is compiled in: the image still has no shell and runs as before. This release is amd64 first, with the arm64 build following in 2.13.1, so an arm64 box stays on 2.12.1 until then.
Image: ghcr.io/hotloop-io/hotloop-flow:2.13.0, linux/amd64 first, with arm64 following in 2.13.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.13.0/README.md