Connectivity states

A vehicle must also be validated when registered into Astara Connect. Once the validate request is sent, an asynchronous validation process is launched to validate and activate data access.

This security step confirms that you can access the vehicle data.

For the validation process, we have three categories of states:

pendingis a transition state of the validation process. It is listening for a user or a provider trigger to continue the process.
error: an error states during the transition from one state to another. The specific cause may vary depending on the data provider involved in the validation process.
connected: a final state to indicate that we are ingesting data from the data provider.

The validation process could work synchronously or asynchronously, following a process with different states that depend on each provider.

Default tracker states

These are the states that a hardware tracker can have and provided in the validation_status field of the tracker:

pending: This is the initial state of the tracker.
wrong_tracker_id: The tracker ID is incorrect when registering the tracker.
pending_for_data: The tracker has been validated and is waiting for valid data.
error_data: The tracker has received data that's erroneous.
connected: The tracker has been validated, received the correct data, and is now effectively connected.
disconnected: The tracker owner within CONNECT has disconnected the tracker via our API.

Possible changes from one status to another

In general, a tracker, independently of its provider, can pass from:

pending → wrong_tracker_id
wrong_tracker_id → pending
pending → pending_for_data
pending_for_data → error_data
error_data → pending_for_data
pending_for_data → connected

BMW states

BMW has the default tracker's states, plus the following ones:

pending_validation: The tracker has been moved into pending validation because its provider needs to run some checks on it.
error_capability: The vehicle does not have the required capability set to true.
error_rejected: The vehicle or driver of the vehicle has rejected to enable the connectivity.
error_revoked: The vehicle connectivity has been revoked.
error_timed_out: The vehicle connectivity request has timed out.

And with these new states, we have the following new transitions, allowing us to pass from:

pending → pending_validation
pending → error_capability
wrong_tracker_id → error_capability
error_capability → pending
pending_validation → error_rejected
pending_validation → error_revoked
pending_validation → error_timed_out
pending_validation → pending_for_data
error_revoked → error_timed_out
pending_for_data → error_revoked
connected → error_revoked

Mercedes-Benz states

Mercedes-Benz has the default trackers's states, plus the following ones:

pending_validation: The tracker has been moved into pending validation because its provider needs to run some checks on it.
error_access: The vehicle's connection requirements have not been met.
error_timed_out: The vehicle connectivity request has timed out.

And with these new states, we have the following new transitions, allowing us to pass from:

pending → pending_validation
pending_validation → error_access
pending_validation → error_timed_out
error_access → pending_validation
error_timed_out → pending_validation
pending_validation → pending_for_data

Cartrack states

Cartrack has the default trackers's states, plus the following ones:

error_credentials: The credentials are wrong.

And with these new states, we have the following new transitions, allowing us to pass from:

pending → error_credentials
error_credentials → wrong_gracker_id
error_credentials → pending