HotLoop core 4.20.0 release notes
The new web UI is the one at / now, and an agent can change everything it can read through MCP. There are no migrations, and a plain helm upgrade or the Quadlet auto-update takes it. The previous release, 4.19.11, is the last one whose default screens were the old ones.
This build is amd64 only, and the next release is one small version bump that builds the arm images, the way the two runs go. stable keeps the arm images it holds in the meantime.
What changed
Section titled “What changed”- The new web UI is the default, and the old one is gone. Every screen was rebuilt as a static page (Astro, with Svelte parts), embedded in the one binary, with no Node on the box and no CDN. It was at
/nextthrough 4.19.x. At/it is the same nineteen screens with the same controls, fields, columns, forms, and words, for the viewer, the operator, and the administrator. What looks different, on purpose:- The colors are HotLoop’s warm ground and orange, the same as the site, Flow, and Cascade, and the mark is the official one.
- The screens are grouped Operate, Plant, Build, and System in a rail on a desk. On a phone there is a bar of five (Board, Alarms, Dashboards, Entities, More), and More opens every screen.
- The theme control says Dark or Light, where it showed a moon.
- The installed app’s icons, theme color and splash color follow the new look.
- A drawer keeps room for its scrollbar, so a card in it does not move when its history loads.
- Signing in with HotLoop unreachable says why and recovers by itself. A phone that never signed in, or signed out, and opens the page with no connection gets the sign-in screen with a sentence saying HotLoop is not answering from here. The page asks again every three seconds, and when the connection returns it reloads without a touch. It is the old behavior, kept.
- MCP can change everything it can read. There were twenty-seven tools that read the plant and commanded equipment; there are 128. Sixty-four more change configuration: devices and tags, discovery and brokers, UniFi networks, entities, helpers, equipment and labels, alarms, automations and blueprints (an agent can now make the rule from a blueprint, which it could only preview), scripts, recipes, dashboards, and the rest of what a screen can save. Thirty-seven reach the administrator’s own functions: users and PINs, settings, backups, escalation, historian targets, broker logins, the fleet of edge relays, and reports. None is a second implementation. Each is one route of the REST API run through that route’s own handler, so the validation, the permission check, the runtime reload, and the audit line are the route’s, with the agent as the actor.
- What stands in front of a change. The switch
HOTLOOP_ALLOW_MCP_WRITES(on by default) must be on, and a caller withHOTLOOP_MCP_OIDC_WRITE_ROLEset must hold that role. The call carries exactly the one permission its route asks for (devices.write,alarms.write,users.manage,settings.write, and so on) and is refused in the route’s own words without it. Every change takes a requiredreason, recorded as aconfigline in the system log beside the route’s own. Commanding equipment is stillwrite_tag,call_service,run_script,apply_recipe, andtrigger_automationbehindHOTLOOP_ALLOW_WRITES, the tag’s writable mark, and its range. Making a tag writable, a rule, or a recipe is configuration and commands nothing until it is used; what it commands then meets the same gate. The two write switches have no route, sosave_settingsrefuses them for an agent as the Settings screen does, and an agent cannot turn on the switch its own writes wait on. A user’s password goes through the call as it does through the API, and the audit line never carries it. The tools exist under--mcp-stdiotoo. MCP.md has every tool, its route, and its permission.
API changes
Section titled “API changes”GET /nextandGET /next/are a301to the root, so a bookmark made while the new UI was beside the old one still lands. TheLocationis relative, so it is right under a base path.GET /static/is gone, and with itGET /next/manifest.webmanifest. The page, its files, the icons,/manifest.webmanifest, and/sw.jsare served from the root as before; the old stylesheet and scripts were not linked from anywhere and are not served.HOTLOOP_UIis no longer read. Setting it does nothing.- No other route changed. The MCP tools are new surface, not REST routes.
Upgrading from 4.19.11
Section titled “Upgrading from 4.19.11”A plain helm upgrade, or the Quadlet auto-update. There are no migrations and nothing to configure. The first load fetches the new page and the service worker replaces the old one’s cache, so a phone that had the app installed shows the new screens on its next open. Nothing can be undone by upgrading, and a rollback to 4.19.11 is safe because nothing in the database changed.
- Nothing new. What is still open under Broken or missing in the roadmap: OPC UA X.509 user tokens, the deprecated
Basic128Rsa15andBasic256policies our OPC UA server offers and passwords over 64 bytes (both the library’s), and S7comm and EtherNet/IP silent-device tests against real devices.