The automation base for the plant floor.

• Entities and the equipment tree

  In 4.18.10

  Every tag gets an entity with an id that never changes, on one ISA-95 tree. A motor is one entity built from the tags it really is, so rules and agents talk about the pump, not register 40001.

• Automations

  In 4.18.10

  Eleven trigger types, entity state and the sun included, compiled when you save. A broken rule dies in the editor, not at 3am halfway through a batch.

• The automation language

  In 4.18.10

  Condition, wait and stop steps inside a sequence, and forSec on a state trigger. "The pump has been on for five minutes" is one trigger, not a timer hack.

• Helpers

  In 4.18.10

  The values the plant's people own, like today's batch target or which shift is on: toggles, numbers, selects, text, counters, timers and schedules. Kept across restarts, never clamped.

• Logbook

  In 4.18.10

  State changes, writes, alarms, rule runs and config changes on one timeline, for the plant, one area or one entity. "What happened right before?" is one list, not five screens.

• Scripts

  In 4.18.10

  Write the CIP cycle once, name it, run it from a rule, a screen, MCP or its own entity. A dry run goes through the real gate, so you see the refusal before anything moves.

• Recipes

  In 4.18.10

  Grade A's setpoints off the laminated sheet and into the plant in one go: checked whole, refused whole, written in order and read back from the device.

• Blueprints

  In 4.18.10

  Write a rule once with blanks and fill it in per pump. Each rule keeps the blueprint version it was made from, so one edit never quietly changes forty rules.

• Dashboards

  In 4.18.10

  A card builder with drag and drop: gauges, numbers, trends, entity lists, write buttons, script and recipe buttons, alarm lists, text, cameras and a floor plan. Give a dashboard to the roles that need it, or bind it to one physical screen. One layout folds from twelve columns on a panel PC to one on a phone, so nobody ever builds the phone version. A card commands nothing itself, so a button still meets the write gate.

• ISA-18.2 alarms

  In 4.18.10

  rtn-unack included, so a trip that fixed itself is still there at shift change. Shelving ends, and unshelve brings the alarm back in the state it's really in.

• Notifications

  In 4.18.10

  ntfy, Gotify, Discord (a webhook, or a bot), webhooks and email. Press Acknowledge on an ntfy push or in the Discord bot and the alarm is acknowledged, signed and single use. Gotify and the Discord webhook are one way. Discord has only met a stand-in, not the real thing.

• MCP

  In 4.18.10

  An agent can read the whole plant and touch only what you armed, through the write gate, and never without a stated reason, which goes in the system log next to the write.

• MQTT and an embedded broker

  In 4.18.10

  Plain topics with JSON paths, Sparkplug B, and an optional broker in the same process, so one box can be the whole install.

• The sun

  In 4.18.10

  Sunrise, sunset, dawn, dusk and the sun's height and bearing, worked out on the box from the site's latitude and longitude, plus a sun trigger with an offset. A site whose uplink died three weeks ago still turns the yard lights on at dusk.

• MQTT discovery

  In 4.18.10

  ESPHome, Zigbee2MQTT, Tasmota and Shelly Gen2 and later show up on their own, reading, on the embedded broker or any other. Nothing is armed until a person accepts the device and arms each point, so a device announcing itself never earns the right to flip a relay. Proven against recordings of real devices, not yet a bench of them.

• Network discovery

  In 4.18.10

  mDNS and SSDP are overheard, and DHCP is heard if the deployment allows it. Finds land next to the MQTT devices with what they are and how HotLoop could talk to them. Probing stays off until a network is named, because a port sweep has knocked over PLCs. Nothing is added by itself.

• Broker logins with rules

  In 4.18.10

  A twelve dollar plug's login can't publish to the boiler's command topic. Logins made in HotLoop carry publish and subscribe rules from a profile, checked on every publish, subscription and outgoing message. Logins from HOTLOOP_BROKER_USERS are unrestricted, as before.

• Historian targets

  In 4.18.10

  Every reading also goes to the plant's own database: PostgreSQL and TimescaleDB, SQL Server, InfluxDB 2 and 3, MySQL and MariaDB. Same readings, same deadband, same quality. Polling never waits for a target, and one that falls behind catches up from HotLoop's own history.

• SQLite or PostgreSQL, your pick

  In 4.18.10

  The database is a setting. A Pi can run any product on a SQLite file with no second container and no 300 MB database image on the SD card. Moving between databases is a backup and a restore.

• Updates that roll themselves back

  In 4.18.10

  Quadlet boxes follow the stable tag and update themselves, and an update that can't pass its healthcheck is rolled back instead of reported as a success. On Helm you run the upgrade. Rolling back is only safe because migrations only add.

• Every protocol driver

  In 4.18.10

  OPC UA, Modbus, MQTT and Sparkplug B, EtherNet/IP, S7comm, MTConnect, HTTP and UniFi. Protocols don't split the products, so nobody runs the Gateway just to reach one PLC.

• UniFi, read-only

  In 4.18.10

  Devices, ports, PoE, WAN failover and clients as tags, and a quiet PLC tells you which switch port it's on. WAN health comes from the console's own checks, so a backup link that's been dead for two days reads dead. Read on two real consoles, though a PoE draw above zero has not been seen yet. Nothing writes to a console yet.

• UniFi screens and events

  In 4.18.10

  An overview with the WAN strip, a topology map that zooms and pinches and is laid out the same way every time, switch faceplates with port traffic traces, clients, networks and WiFi, one button that makes the usual alarms, and the console's event stream so a switch dropping off lands in the logbook in seconds. An agent can ask over MCP for the topology and the latest events. Proven against a lab controller, with touch emulated, and not yet looked at on real gear.

• UniFi writes

  Not built yet

  Writes through the gate, starting with the locate LED. Then Protect, Access and PDUs, each only after it has run on real gear. Nothing writes to a console today.

• Backups and restore

  In 4.18.10

  Pure Go over the database connection, in IoT, Edge and the Gateway. It's also how you move between them, so it has to work every time.

helm repo add hotloop https://hotloop.io/hotloop
helm repo update
helm install hotloop hotloop/hotloop-iot --version 4.18.10 \
  --namespace hotloop --create-namespace

Open http://localhost:8080 once it's up, sign in, add a device. Then notice you can't write to anything. That's on purpose: every tag starts read-only and gets armed one at a time.