Skip to content
Quick start Product guide

OTA updates

Only an MQTT project supports over-the-air (OTA) firmware updates. Paste firmware URL is on the menu of an MQTT project, and the phone can send the update only while it is connected to that project’s broker.

WizDash MQTT OTA remote firmware update architecture and 4-step verification flow diagram
MQTT OTA update flow: the app sends only the update metadata over MQTT, while the ESP32 downloads the .bin from your HTTPS server and verifies its byte size and SHA-256 digest.
  1. Flash the OTA-enabled sketch. When you generate the sketch, enable the OTA variant and flash it to your ESP32 so the board can receive the update command.
  2. Host the firmware over HTTPS. Place the compiled .bin file at your own HTTPS address and configure the matching Root CA certificate in your firmware.
  1. Confirm that both the phone and the board are connected to the project’s MQTT broker.
  2. Open Paste firmware URL from the project menu.
  3. Enter the HTTPS address, version, file size in bytes, and SHA-256 checksum, then send the update.
WizDash Generate Arduino Code dialog with the OTA Remote Firmware Update toggle enabled
Step 1 (Prerequisite): Enable “OTA Remote Firmware Update” when generating the sketch and flash it to your ESP32.
WizDash Paste firmware URL sheet showing HTTPS firmware URL, version, file size in bytes, and SHA-256 checksum fields
Step 2 (Send Update): Open “Paste firmware URL” on the MQTT project menu and enter the HTTPS URL, file size, and SHA-256 digest.

The app does not download the firmware file. It sends those details over MQTT to the board, and the board downloads the file from the HTTPS URL, checks its size and SHA-256 digest, and reports progress back to the app.

The checksum confirms that the downloaded file matches the digest you supplied. It does not identify who published the file. A project handles one update at a time. For the JSON payload format, see Protocol reference.