Skip to content
Stand with Ukraine flag

OTA Updates

ThingsBoard OTA (Over-the-Air) updates let you push firmware and software packages to devices remotely. You upload a package once, assign it to a device profile or individual device, and ThingsBoard notifies all affected devices and tracks each one’s update progress.

ThingsBoard supports two package types — Firmware (FOTA) and Software (SOTA). The distinction matters mainly for LwM2M devices, which handle the two types through different protocol objects. For MQTT, HTTP, and CoAP devices the update flow is identical regardless of type.

Navigate to OTA Updates and click +. Required fields:

FieldDescription
TitlePackage name. Title + version must be unique per tenant.
VersionPackage version string.
Device ProfileLimits this package to compatible devices only.
TypeFirmware or Software.
ChecksumOptional. Defaults to SHA-256 if omitted.

Assigning a package to a profile triggers the update for every device using that profile — potentially thousands at once. ThingsBoard queues notifications to spread the load (default: ~100 devices per minute, controlled by `TB_QUEUE_CORE_FW_PACK_SIZE` and `TB_QUEUE_CORE_FW_PACK_INTERVAL_MS`).

A per-device assignment overrides the profile assignment for that device only.

States up to INITIATED are set by ThingsBoard. All subsequent states are reported by the device firmware.

StateSet byMeaning
QUEUEDThingsBoardNotification waiting to be pushed
INITIATEDThingsBoardShared attributes updated; device notified
DOWNLOADINGDeviceDownload started
DOWNLOADEDDeviceDownload complete
VERIFIEDDeviceChecksum passed
UPDATINGDeviceApplying update (device may reboot)
UPDATEDDeviceUpdate successful
FAILEDDeviceDownload, checksum, or apply error

ThingsBoard includes built-in Firmware and Software dashboards (auto-created for new tenants; importable from GitHub for existing ones). They show the update status of every device, historical records, and failure details.

Devices receive the update notification via shared attribute subscription and download the package over their transport. See the transport-specific guides for attribute topics, chunk download endpoints, and example client implementations:

  • MQTT OTA client
  • HTTP OTA client
  • CoAP OTA client
  • LwM2M OTA