Sets the per-session DLM boost flag for an active session.
When enabled, load management ignores the session's charging
profile, so its ceiling no longer limits the session. This covers
profiles sent through set-charging-profile or the admin panel and
the driver's smart charging and tariff-driven schedules.
Connector-default and charge point maximum profiles are sent
straight to the charger and still cap a boosted session. The session is weighted by its boost priority instead of
its session priority and any matching state-of-charge priority
rule; charge point, EVSE and user priorities still apply, so the
capacity is shared proportionally. With the default boost priority
of 1000 on a fully used circuit, other active sessions can be
reduced to 0 A for as long as the boost is on. Boosted EVSEs also
share the unused headroom between the active circuit constraint
(schedule limit and/or flexibility request) and the circuit's
maximum capacity in proportion to their boost priorities.
A boosted session is not limited by the consumption cap, so it
receives its full allocation without waiting for the vehicle to
draw more current. After a boosted session is raised from 0 A, the
vehicle has about 5 minutes to start drawing before load
management can treat it as idle.
On a circuit that applies the first-come-first-served strategy, a
boosted session takes its charge point's slot, and the other
session on that charge point is held at 0 A until the boost ends
or the boosted vehicle stops drawing. When a boosted vehicle on
the slot draws nothing for 5 minutes, the slot returns to the
other session and is offered to the boosted session again after
30 minutes, or on the next DLM algorithm run when this action is
sent again with enabled: true.
A boosted session is still limited by connector-default and charge
point maximum profiles, the EVSE's maximum supported current, the
circuit's capacity and other sessions' minimum current, and it
receives no power while the vehicle is idle.
The change applies on the next DLM algorithm run, and the circuit
is recalculated again about 30 seconds after the boost is enabled.
The flag persists for the remainder of the session. The boost ends
when either the session ends (no explicit call required) or the
client sends this action again with enabled: false. Once the
boost ends, the session's charging profiles and priority rules
apply again.
Sending enabled: true for a session that is already boosted
updates its boost priority; when priority is omitted, the default
of 1000 is used. Sending the same state and boost priority the
session already carries is accepted as an idempotent no-op
(returns 202 with no second effect), unless the session lost its
charge point's slot and is in the 30-minute pause described above.
The action is rejected with HTTP 422 if the session is not in the
active state, if priority is not an integer of at least 2, or if
priority is sent with enabled: false.
On circuits balanced by an external load balancing integration
(Dreev), the integration controls the limits, so the boost may have
no effect.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
202Action accepted
