Skip to content
Notificator Docs

Firmware Updates

Notificator firmware is maintained in the public IoT-Firmware repository. Each hardware model has a stable identity, its own source directory, and independent release entries:

  • Notificator Base: notificator_base
  • Notificator Touch 3.49: notificator_touch_349 (preview)
  • Notificator Matter: notificator_matter (planned)

Keeping models together makes project-wide maintenance easier while preventing a release for one board from being installed on another.

How an update works

Section titled “How an update works”
  1. The mobile app or web dashboard reads the official firmware manifest and shows the latest compatible version.
  2. When you approve the update, the API publishes a channel request to your device over your configured HiveMQ connection.
  3. The device downloads the fixed official manifest and selects its own model, board, and release channel.
  4. The device verifies the release entry using its embedded ECDSA P-256 public key.
  5. It streams the firmware into the inactive OTA slot and verifies its SHA-256 digest before activation.
  6. The device restarts and reports the installed version and update status.

The private release-signing key is never stored in the mobile app, API, WordPress plugin, MQTT broker, or device.

Request an update from the web dashboard

Section titled “Request an update from the web dashboard”

Open Settings → Device connection and test your HiveMQ connection. Then open Devices, select a Base or Touch device, and use its firmware controls to check the compatible release and confirm the update. The request still travels over MQTT and the device performs the same signature checks described above. An active compatible account API key is required for device commands.

Release channels

Section titled “Release channels”
  • stable: recommended public releases.
  • preview: pre-release builds intended for testing.

The device rejects arbitrary download URLs and releases for another model or board.

Current public releases use independent model tags and channels:

  • Base 1.2.2: stable channel, tagged base-v1.2.2.
  • Touch 0.9.3: preview channel, tagged touch-v0.9.3.

The browser installer lists both models and checks the connected ESP32 family before flashing. Always choose the entry matching the physical board.

Base 1.2.2 and Touch 0.9.3 publish retained presence heartbeats and register a retained MQTT Last Will. If power or connectivity disappears unexpectedly, HiveMQ can publish the offline state without waiting for the device to send a final message. Presence normally changes within roughly 30–60 seconds.

Older devices

Section titled “Older devices”

Older firmware and partition layouts are not part of the current OTA compatibility path. Flash those devices once using USB or the firmware web installer. The complete installer writes the current firmware and dual-slot partition table, after which signed OTA updates are available.

Section titled “Related”