OTA Support Checklist

Use this checklist when a gateway reports a failed OTA update.

Cloud Checks

1. Confirm /api/v1/ota/latest returns the expected version.
2. Confirm the D1 firmware row has the expected sha256 and target_hardware.
3. Confirm the R2 object exists for the published key.
4. Confirm GET /api/v1/ota/firmware/:firmwareId returns:
   • 200 OK
   • X-Firmware-Version
   • X-Firmware-Target
   • X-Firmware-SHA256

Gateway Checks

1. Confirm the gateway has a valid token.
2. Confirm OTA is enabled in gateway settings.
3. Confirm the installed firmware version is older than the published version.
4. Review the gateway-reported OTA runtime fields:
   • last result
   • offered version
   • last check timestamp

Decision

• If checksum headers and R2 object are correct, investigate gateway connectivity or storage.
• If metadata is wrong, stop rollout and correct D1 before more gateways poll.