How to use Attempt Remote Start
“Attempt Remote Start” is essentially the same as “Remote Start”, but provides the customer with more detailed information about the current status.
For the “Attempt Remote Start”, there are five distinct statuses. When sending the request, it initially receives the “pending” status. Subsequently, it transitions to “sending”, and depending on whether the request is accepted or rejected, the status further changes to “failed” or “waiting_for_start_transaction”, followed by “charge_log_attached”.
“Attempt Remote Start” CANNOT be used for roaming stations as we currently do not have the connection implemented between beENERGISED and these stations. In this case, the roaming stations would remain in the status “pending” and not change further.
An “Attempt Remote Start” is considered completed when:
the charging process has started
an error occurred (e.g. the station did not respond)
the station rejected the Remote Start
To effectively utilize an “Attempt Remote Start”, a pair of queries is required. The first query is employed to initiate the start, followed by a subsequent query to retrieve the current status. These two queries are interdependent and should be employed in conjunction.
Example request to start a “remote_start_attempt_mutation”:
mutation {
attemptRemoteStart(
input:
{
connectorId: "abc-123-xyz-456",
tagId: "xxx"
}
)
{
id
status
}
}
Example response from the start of an “Attempt Remote Start”:
{
"data": {
"attemptRemoteStart": {
"id": "wzi-098-bfu-765",
"status": "pending"
}
}
}
Example request for the “remote_start_attempt_status”:
query {
remoteStartAttemptStatus(id: "wzi-098-bfu-765") {
id
status
}
}
Example response from the “Remote Start Attempt Status”:
{
"data": {
"remoteStartAttemptStatus": {
"id": "wzi-098-bfu-765",
"status": "failed"
}
}
}
Here you can find more detailed informations regarding the remote_start_attempt .