Updating Your Coreflux

When to Update

Update Coreflux when a new release includes fixes or features you need. Check Release Notes for what changed in each version. The Coreflux HUB desktop app updates itself.

Keep your project files. Docker named volumes, package install directories, and manual install folders retain LoT, connectors, and configuration when you upgrade only the broker runtime.

LoT file names changed. The files that store your Actions, Models, Connectors and Rules in bin/ are now actions.lot, models.lot, routes.lot and rules.lot. The first start of the new version copies your existing files to these names and leaves the old ones in place, so nothing is lost. If you go back to an earlier version, it reads the old files, which do not contain changes made after the upgrade. If the broker cannot read or write one of these files, it exits with code 78 and names the file; see Startup options.

Update Coreflux

To run the latest image, stop and remove the existing container, then start a new one with the same docker run command from Installation. The --pull=always flag ensures Docker fetches the newest latest tag before each start.

Use your actual names. The examples below use the default container name coreflux_broker and volume project-volume. If you chose different names when you first installed, replace them in every command.

Stop and remove the container

docker stop coreflux_broker
docker rm coreflux_broker

This stops the broker and removes the container. Named volumes (such as project-volume) are not deleted—your project files remain on disk.

Start a new container

Run the same command you used for installation. For the standard setup:

docker run --pull=always -d --name coreflux_broker -p 1883:1883 -p 5000:5000 -p 9100:9100 -v project-volume:/etc/project coreflux/coreflux-mqtt-broker:latest

If you use TLS ports, use the command from the TLS/SSL accordion on Installation—still with --pull=always, the same container name, and the same project-volume mount.

Verify

Confirm the broker is up with curl http://localhost:9100/health, or subscribe to $SYS/Coreflux/Version from an MQTT client. The broker image does not include the HUB — if you also run the HUB container, open Coreflux HUB at http://localhost:3000.

Pull the latest images and recreate the stack. Named volumes (broker-data, hub-data) are kept unless you pass -v to docker compose down.

Pull and recreate

From the directory that contains docker-compose.yml:

docker compose --profile full pull
docker compose --profile full up -d

Both services use the latest tag, so docker compose pull fetches the newest broker and HUB images. See Installation for the Compose file.

Verify

Open the Coreflux HUB at http://localhost:3000 and connect with mqtt://broker:1883. Subscribe to $SYS/Coreflux/Version in the Data Viewer to confirm the broker version. You can also probe http://localhost:9100/health.

Update a Windows service install by stopping the service, replacing the executable, and starting it again.

Use your actual service and paths. Examples use the service name CorefluxBroker and install path C:\Coreflux. Change these if you registered the service differently—see Installation.

Stop the service

Open Command Prompt as Administrator and run:

sc stop CorefluxBroker

Replace the executable

Download the latest Windows package from the Downloads page, extract it, and copy CorefluxMQTTBroker.exe over the file in your install folder (for example C:\Coreflux). Do not remove your existing config or project files in that folder.

Start the service

sc start CorefluxBroker
sc query CorefluxBroker

~2 min if you installed the Linux package from the Downloads page — refresh indexes and upgrade the coreflux-broker package.

Use the tab that matches how you installed the broker. See Installation if you still need to add the Coreflux repository.

Debian & Ubuntu (APT)
RPM (dnf)

Refresh package lists

sudo apt update

Optional — see which version is installed and what is available:

apt-cache policy coreflux-broker

Upgrade coreflux-broker

sudo apt upgrade coreflux-broker

To upgrade only the broker without touching other packages:

sudo apt install --only-upgrade coreflux-broker

Verify

The package upgrade restarts coreflux-broker via systemd. Confirm it is running:

systemctl status coreflux-broker.service

Subscribe to $SYS/Coreflux/Version from an MQTT client, or open Coreflux HUB if you run it separately.

Refresh the package cache

sudo dnf makecache --refresh

Optional — list available versions:

dnf list --showduplicates coreflux-broker

Upgrade coreflux-broker

sudo dnf upgrade coreflux-broker

Verify

The package upgrade restarts coreflux-broker via systemd. Confirm it is running:

systemctl status coreflux-broker.service

Subscribe to $SYS/Coreflux/Version from an MQTT client, or open Coreflux HUB if you run it separately.

Quick Start

Coreflux MQTT Broker

LoT Language

Coreflux HUB

VS Code - LoT Notebooks

Coreflux Portal

Using AI with Coreflux

Product Updates

When to Update

Update Coreflux

Next Steps

Release Notes

Installation

​When to Update

​Update Coreflux

​Next Steps

Release Notes

Installation

When to Update

Update Coreflux

Next Steps