HotLoop for CODESYS chart 0.3.5 wraps HotLoop 4.20.2, and its license annotation names the EmberNet Source License 1.0.
The chart wraps HotLoop 4.20.2, which carries the EtherNet/IP batch fix and the version command.
An upgrade from 0.3.4 (HotLoop 4.20.1, installed from the published index with a profile applied) to 0.3.5 was run on a node with a CODESYS Control for Linux SL 4.22.0.0 runtime on the node's network beside it. One new pod on 4.20.2 came up, the provisioner stayed on 0.3.1, and the device and its 44 tags were still there and none writable. The page answered, and the HotLoop log had no warnings or errors.
0.3.5 is in the index at hotloop.io/hotloop-codesys/, published 2026-11-16. The chart’s license annotation is the EmberNet Source License 1.0, and the HotLoop Free Use License 1.0 comes with the next chart.
The provisioner reached the runtime at 4840 and was refused as an anonymous user, as that runtime is set up, so its own device stayed pending and the listener device and its tags were made, the same as with 0.3.4.
HotLoop for CODESYS chart 0.3.4 wraps HotLoop 4.20.1, the release with the multi-arch images.
The chart wraps HotLoop 4.20.1, the release that carries the arm images the testers pull.
An upgrade from 0.3.3 (HotLoop 4.20.0, installed from the published index with a profile applied) to 0.3.4 was run with a CODESYS Control for Linux SL 4.22.0.0 runtime beside it. One new pod on 4.20.1 came up, the provisioner stayed on 0.3.1, and the device and its 44 tags were still there and none writable. The page answered, and the HotLoop log had no warnings or errors.
0.3.4 is in the index at hotloop.io/hotloop-codesys/, published 2026-11-16. With the runtime on the node’s network, the provisioner reached it at 4840 and the runtime refused it as an anonymous user, as that runtime is set up, so its own device stayed pending and the listener device and its tags were made.
HotLoop for CODESYS chart 0.3.3 wraps HotLoop 4.20.0, so the new web UI and the MCP tools reach the testers.
The chart wraps HotLoop 4.20.0: the new web UI is the default and an agent can change everything it can read through MCP.
An upgrade from 0.3.1 (HotLoop 4.19.8, with a profile applied) to 0.3.3 was run on a node with a CODESYS Control for Linux SL 4.22.0.0 runtime beside it. One new pod on 4.20.0 came up, the devices and their 2,232 tags were still there, and the listeners connected again.
0.3.3 is in the index at hotloop.io/hotloop-codesys/, published 2026-11-15. The provisioner is the same one 0.3.2 ran.
HotLoop for CODESYS chart 0.3.2 wraps HotLoop 4.19.11, and HotLoop's page moves to a port of its own inside the pod, so it runs beside a runtime on the node's own network.
The chart wraps HotLoop 4.19.11 and runs the 0.3.1 provisioner.
HotLoop's page listens on a port of its own inside the pod. A runtime on the node's network holds the port it used before, and the scheduler refused to place HotLoop's page beside it. The Service keeps its port, so the Store tile and the provisioner reach HotLoop exactly as before.
The provisioner refuses a profile that puts two OPC UA PubSub listeners on one UDP port. HotLoop binds a port exclusively, so the second device sat connecting with address already in use.
Every earlier chart stays in the index.
Breaking
Only the container's own port moved. Anything that reaches HotLoop through its Service is unchanged, and anything that reached the pod directly on the node's network has to follow it to the new port, which the docs name.
0.3.2 is in the index at hotloop.io/hotloop-codesys/, published 2026-11-15, and the provisioner image it runs pulls with no login. It carries nothing that writes to the PLC.
HotLoop for CODESYS chart 0.3.1: the provisioner takes the app's Service and Secret names from the release the way HotLoop does, so an install with any release name works.
The provisioner finds HotLoop's Service and its credentials Secret by the same naming HotLoop's own chart uses, which is the release name, so a release called anything installs and is set up. The old rule guessed a different name for a release without "hotloop-codesys" in it, which is a name the HotLoop pod did not have.
The example profile no longer lists Variant as a RawData type, because it is not one.
Everything in 0.3.0 is still here: the provisioner 0.3.0, a list of devices in a profile, hostNetwork off by default, HotLoop 4.19.4 underneath, and nothing that writes to the PLC.
Every earlier chart stays in the index, and the publish refuses a version it already has.
0.3.1 is in the index at hotloop.io/hotloop-codesys/, published 2026-11-05, and the provisioner image it runs, ghcr.io/hotloop-io/hotloop-provision at 0.3.0, pulls with no login. The consequence: install this one, not 0.3.0, because a release name of your own choosing now works the way you would expect.
It installs from the EmberCORE App Store, where it is listed for EmberNet staff, who put it on a tenant, or with Helm from the index. The chart renders from the live index with Helm (checked 2026-11-14 with the provisioner switched off).
The first published chart of HotLoop for CODESYS: HotLoop Edge beside a CODESYS runtime, set up from a profile with nobody clicking. It wraps HotLoop 4.19.4 and runs provisioner 0.3.0.
A chart that wraps HotLoop Edge, with defaults for a runtime on the same node: SQLite on the node's own storage, no database pod, one replica, and the OPC UA server, the broker, edge publishing, and backups off.
A provisioner, one static Go binary and a public image, that reads a profile (the device, the variables to keep, the alarms, and one screen) and sets all of it up in HotLoop once the PLC's runtime answers. It looks again every five minutes.
A profile can carry a list of devices of any protocol HotLoop speaks, so an OPC UA PubSub listener comes back configured with no PLC needed. A profile with one device reads exactly as before.
A variable the profile lists that the PLC has gained since is added by itself. A variable the PLC lost reads bad with the server's reason. The screen and the alarms are replaced only when the profile's revision is higher, so a change a person made survives until a newer profile ships on purpose.
Nothing writes to the PLC. Every tag the provisioner sets up is read-only, and the profile marks none writable.
Both pods tolerate an unreachable or not-ready node with no time limit, so a node that loses its control plane keeps them. The tolerations are in the chart. The link was not cut in testing.
The chart takes hostNetwork, off by default, for a pod that has to hear a publisher's multicast on the node's own cards.
This is the first chart in the index at hotloop.io/hotloop-codesys/, published 2026-11-05. It needs HotLoop 4.19.4, which is out, and it is superseded by 0.3.1 the same day: 0.3.1 is the one to install.
What it was run against: a CODESYS Control for Linux SL 4.22.0.0 runtime in a container, running HotLoop’s own lab program, with a HotLoop Edge image built from HotLoop’s main branch. The device, its tags, the alarm, and the screen appeared with no hand step, every value read good and moved, the pods came back after a pod delete, and the install read bad with the reason “the PLC’s runtime is not answering” through a runtime restart and came back by itself about 88 seconds later.