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
@swinp implemented in 2.47.0, together with the VS Code extension 1.2.0 (see #60 for the details). Declare the compatibility fields before including the OTA header:
Instead of a THINGER_OTA_CHECK resource, the fields are embedded in the firmware binary and reported by the device in $ota/options. The extension compares them with the new firmware and asks for confirmation if they differ, and the device itself rejects a different firmware unless the user confirmed it. Devices without fields are updated as before, and it works on every board with OTA updates.
Activity
alvarolb commentedon Oct 20, 2026
@swinp implemented in 2.47.0, together with the VS Code extension 1.2.0 (see #60 for the details). Declare the compatibility fields before including the OTA header:
Instead of a
THINGER_OTA_CHECKresource, the fields are embedded in the firmware binary and reported by the device in$ota/options. The extension compares them with the new firmware and asks for confirmation if they differ, and the device itself rejects a different firmware unless the user confirmed it. Devices without fields are updated as before, and it works on every board with OTA updates.Thanks for the idea!