Appearance
Firmware And OTA
Platform admins can upload TapiCube firmware binaries and roll them out deliberately.
Release Library
Firmware releases can be draft, active, paused, or retired. Only active releases can be assigned to TapiCubes.
Each uploaded binary stores a SHA-256 checksum. When an active release is assigned, the checksum is delivered to the TapiCube through remote config with the target version and update URL.
Retired firmware can be deleted once no TapiCube targets that version. Deletion removes the release record and attempts to remove the hosted .bin file.
Release states:
- Draft: uploaded but not ready for assignment.
- Active: can be assigned to TapiCubes.
- Paused: temporarily unavailable for new assignment.
- Retired: historical only; can be deleted if unused.
Assigning Firmware
Open a TapiCube, go to Operations, and assign a target release. The device receives the target through remote config and updates when the target differs from the running firmware.
If an old release is missing a checksum, the admin attempts to calculate it from the hosted .bin file. If that is not possible, re-upload the binary before assigning it.
Roll out firmware to one test TapiCube first. Confirm status and console logs before assigning the release to more stores.
Status
Open Status on a TapiCube to review current firmware, target firmware, OTA status, last check, errors, heartbeat, uptime, heap, WiFi RSSI, and IP address.
Safety Notes
Firmware builds can be hosted from the admin firmware library and assigned to TapiCubes in controlled rollouts.
The TapiCube verifies the downloaded binary against the SHA-256 checksum stored in the admin release library before activating the update.
Before a production rollout, confirm:
- the binary is built for the correct board
- the firmware version constant matches the release version
- the release has a SHA-256 checksum
- the device has enough OTA space
- the target URL is reachable by the device
- remote console logs are available for failures
- rollback strategy is defined