Changelog
What changed in each release. The release workflow publishes a version's
section here as its release notes, and refuses a tag without one - so a
change worth knowing about is written here when it is made, under
Unreleased, and the heading becomes the version when it ships.
The format follows Keep a Changelog;
versions follow Semantic Versioning. Until 1.0.0 a
minor version may change the API or the configuration, and says how here.
Unreleased
0.1.0
The first release: the library for boards and hosts, and modbee-mqtt, the server
built from it, as downloads for Linux and Windows and as a Docker image.
The library
- MQTT 5.0 and 3.1.1 in C++14, with nothing that waits on the network: a
client, a broker and a bridge, the same source on a board and a host. MqttDevice, typed values, Sparkplug B (an edge node and a host
application, tested with the Eclipse Sparkplug TCK).- Boards: ESP32, ESP8266, mbed (Portenta, Opta, Nano 33), RP2040, STM32 - over
Wi-Fi, Ethernet or cellular, with TLS on each.
The server
modbee-mqtt serve: one broker per CPU core behind one port, configured with
onemodbee.yaml; sessions and retained messages that survive a restart;
device logins and provisioning.- The Kafka pipe: MQTT to Kafka and back, messages passed through untouched,
a PUBACK only once Kafka has the message. - The Application API, gRPC with a REST admin surface: consumer groups that
share a device's messages, publishing to devices, connections, sessions,
retained messages and logins - on a Unix socket, or TCP with a token. - Linux (x86-64, ARM64) and Windows (x86-64), as a service on both.
Ready to run
.deband.rpmpackages, x86-64 and ARM64.- Set up with the
modbee-mqttcommand alone, the same on Linux and Windows:
modbee-mqtt service installruns it as a service (systemd, or a Windows
service) keeping everything in one folder, andmodbee-mqtt adminsets the
admin login. No configuration file. modbee-mqttfor Linux as one static binary that runs on any distribution, and
modbee-mqtt.exefor Windows as one file - each with the broker, the Kafka pipe,
the Application API and the CLI inside;modbee-mqtt --versionlists them.- Each attested by GitHub, with a CycloneDX SBOM, and a checksum list signed
with Sigstore. docs/releases.md
shows how to check one. - The Docker image:
ghcr.io/mod-bee/modbee-mqtt:0.1.0, amd64 and arm64.
Last updated 2 hours ago
Was this helpful?