triggerTestCharge

Initiate a test charge of an electric vehicle (EV).

This is to ensure that the EV or EVSE (charge point) can be controlled remotely and successfully charged for a short period.

If it is not possible to initiate a test charge, a KT-CT-4355 error will be returned. It may have a testChargeRefusalReasons extension which lists the reasons why the test charge was refused. Possible reasons include:

TC_DEVICE_LIVE (device is already live)
TC_DEVICE_ONBOARDING_IN_PROGRESS (test dispatch already in progress)
TC_DEVICE_RETIRED (device is retired)
TC_DEVICE_SUSPENDED (device is suspended)
TC_DEVICE_DISCONNECTED (device is disconnected)
TC_DEVICE_ALREADY_CHARGING (device is already charging)
TC_DEVICE_AWAY_FROM_HOME (device is away from home)
TC_DEVICE_NO_LOCATION_CONFIGURED (device has no location configured)
TC_DEVICE_LOCATION_UNABLE_TO_IDENTIFY (unable to identify device location)
TC_DEVICE_LOCATION_MISSING (device location is missing)

Arguments

input : AccountNumberInput

Returns

PerformTestCharge

Initiate a test charge of an electric vehicle (EV).

This is to ensure that the EV or EVSE (charge point) can be controlled remotely and successfully charged for a short period.

TC_DEVICE_LIVE (device is already live)
TC_DEVICE_ONBOARDING_IN_PROGRESS (test dispatch already in progress)
TC_DEVICE_RETIRED (device is retired)
TC_DEVICE_SUSPENDED (device is suspended)
TC_DEVICE_DISCONNECTED (device is disconnected)
TC_DEVICE_ALREADY_CHARGING (device is already charging)
TC_DEVICE_AWAY_FROM_HOME (device is away from home)
TC_DEVICE_NO_LOCATION_CONFIGURED (device has no location configured)
TC_DEVICE_LOCATION_UNABLE_TO_IDENTIFY (unable to identify device location)
TC_DEVICE_LOCATION_MISSING (device location is missing)

Possible Errors

Allowed Viewers

Customer

Partner User

Third party

Required Permissions

Can access customer queries
OR Can manage ev

Rate Limits

Key	Steps
`user`	['300/h']

Query Complexity

Examples

The example data in the variables and responses below are autogenerated values designed to resemble real inputs. They do not represent actual customer data, and in some cases may require additional validation.

mutation TriggerTestCharge($input: AccountNumberInput) {
  triggerTestCharge(input: $input) {
    krakenflexDevice {
      ...KrakenFlexDeviceTypeFragment
    }
  }
}

{
  "input": AccountNumberInput
}

{
  "data": {
    "triggerTestCharge": {
      "krakenflexDevice": KrakenFlexDeviceType
    }
  }
}