Device Management

Device management in Luxonis Hub is the part of the platform that lets you inspect device state, perform supported device operations, and open remote workflows after a device has been adopted into Hub.

Why it matters

Once a device is connected, Hub gives you a shared place to understand whether it is online, what software it is running, which applications are installed, and whether remote access or supported update actions are available. That is the practical control-plane layer most teams need before they can operate a real fleet.

Mental model

Think of device management in Hub as three layers:

Device visibility: the device list and overview tell you which devices exist, whether they are healthy, and what they are currently running.
Supported device actions: Hub can expose actions such as reboot or supported OTA updates where that path exists.
Remote operations: Web Terminal and related workflows give you operational access for debugging or maintenance.

Self-hosted boundary

For self-hosted deployments, Hub does not manage the underlying host operating system. The host remains customer-managed even when Hub is used for remote access and app lifecycle workflows.

What you can inspect today

From the Devices page, you can monitor all adopted devices in one place and open the detail view for a specific device.

Devices list in Luxonis Hub — Devices page in Luxonis Hub showing adopted devices and current fleet state.

From the device detail view, you can inspect:

Uptime and recent device status
Device information such as name, ID, serial number, and installed OS version
Connection and network details relevant to current device reachability
Installed applications and their current states
Supported update state where OTA actions are available for that device path

Device overview in practice

The Device Overview page is the main operational summary for one device.

Device overview page in Luxonis Hub with status, system details, and available actions.

From there, you can typically:

review the current device state before making changes
rename the device
reboot the device
move into app-management or remote-access workflows

Connect a device first

If the device has not been adopted yet, start with the Connect OAK guide.

Update Device (OTA)

Learn which OTA flows are supported today and where the self-hosted boundary stops.

Web Terminal

Open browser-based shell access for remote debugging and maintenance workflows.

Manage Applications

Install, start, stop, and inspect OAK Apps running on a connected device.

ON THIS PAGE