This event shall be generated when the EV is unplugged or not detected (having been previously plugged
in). When the vehicle is unplugged then the session is ended.
If the EVSE detects a fault it shall generate a Fault Event. The SupplyState attribute shall be set to
DisabledError and the type of fault detected by the EVSE shall be stored in the FaultState attribute.
This event shall be generated when the FaultState changes from any error state. i.e. if it changes from
NoError to any other state and if the error then clears, this would generate 2 events.
It is assumed that the fault will be cleared locally on the EVSE device. When all faults have been
cleared, the EVSE device shall set the FaultState attribute to NoError and the SupplyState attribute
shall be set back to its previous state.
Since some EVSEs cannot obtain the SoC from the vehicle, some EV charging solutions allow the consumer
to specify a daily charging target (for adding energy to the EV’s battery). This feature allows the
consumer to specify how many miles or km of additional range they need for their typical daily commute.
This range requirement can be converted into a daily energy demand with a target charging completion
time.
The EVSE itself may use this information (or may allow a controller such as an EMS) to compute an
optimized charging schedule.
An EVSE device may implement the Device Energy Management cluster PFR (Power Forecast Reporting) and FA
(Forecast Adjustment) features. This can help a controller (such as an EMS) to optimize the EVSE against
other ESAs. For example, a solar PV ESA may share its Forecast and allow the EVSE to know the best time
to charge so that any excess solar generation is used to charge the EV.
EVSE devices that support the Device Energy Management cluster’s FA feature can have their charging
profiles set by a controller device such as an EMS. For example, if the EVSE advertises a simple power
forecast which allows the EMS to adjust over a wide range of power and time durations, then the EVSE may
allow the EMS to propose a revised optimized forecast (which is the charging profile).
See the Device Energy Management Cluster for more details.
If the EVSE supports PLC, it may be able to support the Plug and Charge feature. e.g. this may allow the
vehicle ID to be obtained which may allow an energy management system to track energy usage per vehicle
(e.g. to give the owner an indicative cost of charging, or for work place charging).
If the EVSE supports the Plug and Charge feature, it will only work if a compatible EV is connected.
If the EVSE is fitted with an RFID reader, it may be possible to obtain the User or Vehicle ID from an
RFID card. This may be used to record a charging session against a specific charging account, and may
optionally be used to authorize a charging session.
An RFID event can be generated when a user taps an RFID card onto the RFID reader. The event must be
subscribed to by the EVSE Management cluster client. This client may use this to enable the EV to charge
or discharge. The lookup and authorization of RIFD UID is outside the scope of this cluster.
Vehicles and EVSEs which support ISO 15118 may allow the vehicle to report its battery size and state of
charge. If the EVSE supports PLC it may have a vehicle connected which optionally supports reporting of
its battery size and current State of Charge (SoC).
If the EVSE supports reporting of State of Charge this feature will only work if a compatible EV is
connected.
Note some EVSEs may use other undefined mechanisms to obtain vehicle State of Charge outside the scope
of this cluster.
Allows a client to disable the EVSE from charging and discharging.