The AI-14 transitions between power states based on specific triggers. Understanding these transitions helps partners select the appropriate API workflow for each scenario.
Figure 1 — AI-14 State Transition Diagram
Transition Triggers
The following triggers cause the AI-14 to transition between its power states.
Standby → Online (Full Wake):
The device transitions to the fully Online state when any of the following events occur:
An explicit Wakeup API request is sent using POST /devices/{imei}/wakeup
Vehicle ignition starts
The accelerometer detects vehicle movement
The SOS button on the device is pressed
A user touches the device screen
Standby → Semi-Online (Minimized Wake):
The device transitions to Semi-Online mode when a supported remote operation is triggered through the API while the device is in Standby. The cloud automatically wakes the device to process the request.
Online → Standby (Hibernation):
When the AI-14 is Online, the device transitions directly to hibernation (Standby) after the Standby timer expires. The device does not transition through Semi-Online mode during this process.
Note
The device does not follow an Online → Semi-Online → Standby transition path. The transition always occurs directly from Online to Standby. To use Semi-Online mode after the device has been fully Online, wait for the device to return to Standby and then trigger a supported remote operation.
Semi-Online → Standby (Hibernation):
After the device completes the last supported remote operation, it returns to hibernation after 120 seconds of inactivity. If another supported operation is requested during this period, the inactivity timer resets.
Any State → Offline:
A device transitions to Offline when it loses power or network connectivity. This transition can occur from any device state.
Transitional Behavior
When the AI-14 transitions between power states, your webhook notifications and API responses may briefly show intermediate states. This is expected platform behaviour and does not indicate a device fault.
Brief Offline Status During Transitions
When the device transitions between any two states, its status may briefly appear as "Offline" before settling into the target state. The connection cycle during state changes causes this — it resolves within seconds.
Important
These transient states do not affect the dashcam’s actual functionality. Recording, event detection, and all other device capabilities continue to work normally. Only the cloud-reported status may momentarily show an intermediate state.
Recommended handling for partners:
Do not treat a brief Offline status during a transition as an error or trigger a retry loop.
Implement a short grace period in the integration logic when an Offline status appears immediately after a supported API request or Wakeup command.
Wait for the next webhook that confirms the target state, such as isSemiOnline: true or status: Online, before continuing the workflow.
If multiple webhooks arrive in quick succession, the one with the latest changedAt value reflects the true current state not the one that arrived last.