Use this guide when you want to update a supported OAK4 device through the current Luxonis Hub OTA workflow.
Current boundary
Self-hosted OTA in Hub is not generally available today. For self-hosted systems, the host operating system remains customer-managed.
Requirements
Before starting the update:
confirm the device is online and connected to Hub
confirm the device has enough free storage for download and unpacking
confirm the device has stable power for the full update and reboot cycle
Update the device
Open the device in Hub and go to the Device Overview page.
If a newer supported version is available, click the orange Update Available button.
Review the changelog and confirm that you want to start the update.
Wait while the device downloads and applies the update.
Allow the device to reboot and reconnect to Hub.
Start the OTA flow
From the Device Overview, click Update Available when Hub shows a newer supported version for the device.
Confirm the update
Review the changelog and click Update to continue.
Monitor progress
The device downloads the new software and prepares the update before rebooting automatically.
Verify the result
After the device returns, check the update field in the overview and use the ? tooltip for detailed result information.
Verify the update
The update is complete when all of the following are true:
the device reconnects to Hub after reboot
the device overview shows the expected software version
the update field reports a successful final state
the device is ready for normal app and remote-access workflows again
Reboot is required
Completing the OTA update requires a device restart. After reboot, all services and applications, including the OAK Agent, will restart automatically.
Current availability
This page covers:
Current: supported OTA flows for OAK4 device software
Not current: broad self-hosted OTA for customer-managed Linux hosts
Not current: manifest-based rollout or large-scale fleet rollout orchestration
If you are running a self-hosted deployment, you can still use Hub for visibility, remote sessions, and app lifecycle management, but the host OS lifecycle remains your responsibility.
