HotLoop Flow 2.16.6 release notes
HotLoop Flow 2.16.6 stops a Modbus write that only a timer drives from dropping messages behind a slow device. Writes an operator can reach are untouched. Nothing in your flows, settings or chart changes.
What changed
Section titled “What changed”- A write fed only by timers merges its queue, keeping the newest value for each register. A flow that reads a register every second and writes it to another, one inject at the root, sends the same register again with the newest value each time. Behind a connection shared with other nodes the writes backed up, the nodes in front of them waited on the 30 second limit, and then messages were dropped: on the plant, 848 drops in 44 minutes, all on 21 such writers. The Modbus write and flex write nodes now merge their queued messages by function code, unit id, address and quantity, and keep the newest. What goes out to the device is the latest value.
- The rule is the graph, decided when the flow is deployed. A write merges only if every path into it, back to where messages enter the flow, starts at an inject node. A button, a switch, a numeric input, a dashboard control, an input from the network or a Catch node anywhere upstream means it never merges, and a writer reachable from both kinds counts as the operator’s. A link out reaches the link in nodes it names, and a path that cannot be followed means no merging. It is worked out again on every deploy that changes the wiring, and never from a single message.
- A durable wire’s message is never merged. Writes that go over a durable wire are delivered as before.
- The count is on the metrics.
hotloop_flow_node_messages_coalesced_totalcounts merged messages for writes as it does for reads.
What it fixes, with numbers
Section titled “What it fixes, with numbers”A Modbus flex write behind a device that takes 40 ms to answer, an inject asking 100 times a second, an inbox of 16 and a block limit of 500 ms, over 6 seconds on one machine:
| Details | 2.16.5 | 2.16.6 |
|---|---|---|
| Dropped | 6 | 0 |
| Blocked senders | 13 | 0 |
| Messages merged | 0 | 376 |
| Written to the device | 124 | 123 |
A write an operator can reach, with 30 writes sent as fast as they can go to a device that takes 40 ms each, delivers all 30 in order and merges none. So does a write reachable from both an inject and an operator’s control.
New settings
Section titled “New settings”None.
Upgrade
Section titled “Upgrade”A plain helm upgrade to the 2.16.6 image and chart, or the new tag in your Quadlet unit. Nothing happens on first start and nothing needs migrating. A flow file loads and saves byte for byte as before. This release builds the amd64 image. The 2.16 and 2 tags keep the arm64 image they already hold from 2.16.1, and arm64 comes back in 2.16.7. If you are on arm64, stay on 2.16.1 until then.
Image: ghcr.io/hotloop-io/hotloop-flow:2.16.6, linux/amd64. 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.16.6/README.md