You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zachary Nathan Goode edited this page Oct 4, 2026
·
1 revision
OTA Updates
The OTA path consists of a Windows pre-flight check and firmware partition update.
The desktop app inspects a selected .bin for FILELINK_FW_ID:<project-id>:<version>; and has a less precise version fallback.
The UI requires matching project ID and a newer semantic version.
Firmware streams the upload into the next OTA partition in 4096-byte chunks.
Firmware runs normal ESP-IDF image validation with esp_ota_end(), selects the partition, returns success, and reboots.
The firmware handler does not repeat project/version checks. The supplied implementation does not establish signed images, secure boot, encrypted OTA transport, anti-rollback, or password authorization for the OTA endpoint. A connection reset during the reboot can be an uncertain—not confirmed successful—outcome.