The implemented cluster.
Readonly
eventsAccess the behavior's events.
Readonly
energyThis event shall be generated when the EV starts charging or discharging.
Readonly
energyThis event shall be generated when the EV stops charging or discharging.
Readonly
evThis event shall be generated when the EV is plugged in.
Readonly
evThis 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.
Readonly
fault: ClusterEvents.EventObservable<Event<TypeFromFields<{ 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.
Supported features as a flag object.
Readonly
stateAccess the behavior's state.
Readonly
chargingIndicates the time, in UTC, that the EVSE will automatically stop current flow to the EV.
A null value indicates the EVSE is always enabled for charging.
A value in the past or 0x0 indicates that EVSE charging shall be disabled. The attribute is only set via the payload of the EnableCharging command.
This attribute shall be persisted, for example a temporary power failure should not stop the vehicle from being charged.
Readonly
circuitIndicates the capacity that the circuit that the EVSE is connected to can provide. It is intended to allow implementation of a self-managed network of EVSEs. It is assumed that the device will allow the setting of such values by an installer.
Readonly
faultIndicates the type of fault detected by the EVSE (internally or as detected in the pilot signal).
When the SupplyState attribute is DisabledError, the FaultState attribute will be one of the values listed in FaultStateEnum, except NoError. For all values of SupplyState other than DisabledError, the FaultState attribute shall be NoError.
Readonly
maximumIndicates the maximum current that can be delivered by the EVSE to the EV.
This shall represent the actual maximum current offered to the EV at any time. Note that the EV can draw less current than this value. For example, the EV may be limiting its power draw based on the operating conditions of the battery, such as temperature and state of charge.
The attribute can be initially set using the EnableCharging command or by adjusting the UserMaximumChargeCurrent attribute.
This attribute value shall be the minimum of:
• CircuitCapacity - Electrician’s installation setting
• CableAssemblyCurrentLimit (detected by the EVSE when the cable is plugged in)
• MaximumChargeCurrent field in the EnableCharging command
• UserMaximumChargeCurrent attribute
Readonly
minimumIndicates the minimum current that can be delivered by the EVSE to the EV. The attribute can be set using the EnableCharging command.
Readonly
sessionReadonly
sessionReadonly
sessionReadonly
state: null | EnergyEvse.StateIndicates the current status of the EVSE. This higher-level status is partly derived from the signaling protocol as communicated between the EVSE and the vehicle through the pilot signal.
The State attribute shall change when the EVSE detects change of condition of the EV (plugged in or unplugged, whether the vehicle is asking for demand or not, and if it is charging or discharging).
NOTE
SessionEnding is not really a state but a transition. However, the transition period
may take a few seconds and is useful for some clean up purposes. The Fault state is used to indicate that the FaultState attribute is not NoError.
Readonly
supplyIndicates whether the EV is currently allowed to charge from or discharge to the EVSE.
Optional
Readonly
randomizationIndicates the size of a random window over which the EVSE will randomize the start of a charging session. This value is in seconds.
This is a feature that is mandated in some markets (such as UK) where the EVSE should by default randomize its start time within the randomization window. By default in the UK this should be 600s.
For example, if the RandomizationDelayWindow is 600s (i.e. 10 minutes) and if there was a cheap rate energy starting at 00:30, then the EVSE must compute a random delay between 0-599s and add this to its initial planned start time.
Optional
Readonly
userIndicates a maximum current that can set by the consumer (e.g. via an app) as a preference to further reduce the charging rate. This may be desirable if the home owner has a solar PV or battery storage system which may only be able to deliver a limited amount of power. The consumer can manually control how much they allow the EV to take.
This attribute value shall be limited by the EVSE to be in the range of:
MinimumChargeCurrent <= UserMaximumChargeCurrent <= MaximumChargeCurrent
where MinimumChargeCurrent and MaximumChargeCurrent are the values received in the EnableCharging command.
Its default value SHOULD be initialized to the same as the CircuitCapacity attribute. This value shall be persisted across reboots to ensure it does not cause charging issues during temporary power failures.
Static
Readonly
clusterBase cluster state include all attribute values but may be extended by subclasses.
Static
Readonly
defaultsStatic
Optional
Readonly
dependenciesStatic
Readonly
earlyStatic
Readonly
EventsStatic
Readonly
ExtensionStatic
Readonly
idThe behavior ID for ClusterBehaviors is the name of the cluster.
Static
Readonly
InterfaceStatic
Readonly
InternalImplementation of internal state. Subclasses may override to extend.
Static
Readonly
nameStatic
Optional
Readonly
schemaStatic
Readonly
StateStatic
Readonly
supervisorStatic
supportsDoes this behavior support functionality of a specific implementation?
Release resources. This is the public API for releasing application resources held by behaviors in internal state.
Execute logic with elevated privileges.
The provided function executes with privileges escalated to offline mode. This is not commonly necessary.
Elevated logic effectively ignores ACLs so should be used with care.
Note that interactions with the behavior will remain elevated until the synchronous completion of this call. You should only elevate privileges for synchronous logic.
the elevated logic
Protected
callbackCreate a generic callback function that has the same properties as a Reactor.
Like a reactor, the callback's "this" will be bound to an active Behavior instance. Because of this: The reactor MUST be a real JS function - arrow functions will not work!
Allows a client to disable the EVSE from charging and discharging.
Allows a client to enable the EVSE to charge an EV.
Behaviors are ephemeral and should not perform initialization in their constructor. They can override this method instead.
This method may be synchronous or asyncronous. If asynchronous, the behavior will not be available for external use until initialization completes.
Optional
_options: {}Protected
reactInstall a Reactor.
Important: The reactor MUST be a real JS function - arrow functions will not work!
Allows a client to put the EVSE into a self-diagnostics mode.
Static
alterStatic
enableStatic
forStatic
setStatic
with
This is the default server implementation of EnergyEvseBehavior.