Purpose
Semi-Online mode optimizes how the AI-14 handles specific remote operations while parked.
This mode provides the following benefits:
Reduced vehicle battery drain: The camera imagers are the highest power-consuming components on the device. Semi-Online mode keeps the imagers turned off during supported remote operations that do not require recording. This behavior significantly reduces power consumption during parked remote operations.
Status stays accurate: During supported remote operations, the cloud platform and portals continue to display the device status as “Standby” because the vehicle is not actively in use. This behavior helps prevent confusion for fleet operators who may otherwise see unexpected Online statuses for parked vehicles.
Clear distinction between wake scenarios: The AI-14 behaves differently depending on the reason for the wake event:
Remote operation wake: The device wakes to process a supported API request. The camera imagers and screen remain off.
True wake: The device wakes because of a vehicle event, user interaction, or an explicit Wakeup request. Full device functionality becomes available.
Requirements
Semi-Online mode and the power state management capabilities are available only for AI-14 devices that meet all the following requirements:
Requirement | Supported Version |
|---|---|
Device Model | AI-14 |
Firmware version | 14.3.5 or later |
Wake Mechanism | MQTT wakeup capability |
Note
Devices that do not meet these requirements do not support the isSemiOnline field, the Semi-Online endpoint, or Semi-Online behavior for supported operations.
Operation
When the AI-14 wakes from hibernation to handle a supported remote operation, it operates in a minimized mode. The following table describes the status of each device component during Semi-Online mode:
Component | State in Semi-online |
|---|---|
Camera imagers (lenses) | OFF |
Screen / display | OFF |
Recording | OFF |
GPS | OFF |
Cloud-visible status | Remains “Standby” |
Network, storage, streaming services | Active (as needed) |
Note
When the AI-14 exits hibernation, the device does not immediately identify which operation it needs to process. The device initially keeps the imagers off by default and then enables only the minimum functionality required after it identifies and processes the request.
Note
When the AI-14 enters the fully Online state because of a true wake event, normal Online behavior applies. Semi-Online limitations no longer apply until the device returns to hibernation (Standby).
Supported Operations
Semi-Online mode applies only to the following operations. For these operations, the device keeps the imagers and screen turned off, while the cloud continues to display the device status as Standby:
Operation | Endpoint | Description |
|---|---|---|
Recordings Availability | GET /devices/{imei}/recording-ranges | Check whether recordings are available on the device while it is parked. |
Connect to Media Core | POST /devices/{imei}/connect-media | Establish the required media connection to support media workflows. |
Virtual Event | POST /devices/{imei}/virtual-event | Create a virtual event workflow while keeping imagers and screen off. |
Note
Each supported endpoint independently triggers Semi-Online mode. The operations do not depend on one another. For example, you can call the Virtual Event endpoint directly without first calling the Recordings Availability endpoint.
Note
If the device is already fully Online and the cloud status shows as online, Semi-Online behavior does not apply until the device returns to hibernation (Standby).
Return to Hibernation
After the AI-14 completes the last supported remote operation:
The device returns to hibernation after 120 seconds of inactivity.
If another supported operation is requested during this period, the inactivity timer resets.
For operations that involve recording upload or streaming, the device completes the entire transfer before returning to hibernation.
Note
When the device is fully Online, it always transitions directly back to hibernation (Standby). The device does not transition through Semi-Online mode during this process.