SOC_LIMIT_REACHED

State of charge limit reached - Charging prevented due to a device specific charging limit setting (current state of charge is equal to or above the set limit).
COMMUNICATION_ERROR

Unable to communicate with device - Dispatches were created but no telemetry readings available during the charge session.
THIRD_PARTY_CHARGING_INTERFERENCE

Third-party charging interference - Telemetry for an at-home charging event was found outside of Dispatch Schedules.
POWER_DISCREPANCY

Observed power discrepancy - Power during the session was observed to be significantly different from the value of the max. import in static data.
POWER_TAPERING

Observed power tapering - Power decreased at state of charge levels or towards the end of the session.
NO_SCHEDULED_CHARGE

No scheduled charge within session - There were no schedules for the given charge session period.
FAILURE_CAUSE_ERROR

Unable to determine cause of failure - If the charge session was not achieved, butwe are unable to determine the cause of failure.
CUSTOMER_ACTION_REQUIRED

Action required - Customer needs to take action to re-enable our control (i.e attemptto re-onboard).
NO_CHARGING

No charging - No charging (import of energy) was observed during the session.
FULL_CHARGE

Device fully charged - Device conducting a relative charge session indicated it hadreached 100% SoC or an internal SoC limit. Applied regardless of whether or not wewere able to add the energy requested.
POST_CHARGE_BATTERY_DRAIN

Post-charge battery drain - Target was hit but session ended below target due tobattery drain (caused e.g. by cell balancing).
UNKNOWN_CHARGING_ERROR_CAUSE

Unknown failure cause

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.

Example

"SOC_LIMIT_REACHED"