You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e6a95c5
Browse filesBrowse the repository at this point in the historyBrowse files
Add an option to send Session Current Limit as a TxDefaultProfile (#2158) (#2183)
Some chargers (Timxon A0, ABB Terra AC, Morek MEV11 on OCPP 1.6) refuse
both the station ChargePointMaxProfile and a transaction-bound TxProfile,
but accept a TxDefaultProfile on the connector and apply it to the
running transaction. Before #2131 the station slider reached them through
its TxDefaultProfile fallback; since 0.12.0 nothing does.
A per-charger option, session_limit_default_profile (off by default),
makes Session Current Limit send a Relative TxDefaultProfile instead: on
the connector on 1.6, on the connector's EVSE on 2.0.1. It uses profile
id 2000+n and one stack level below the reported maximum (at least 1, and
0 for a maximum of 0), which on 1.6 is the profile the set_charge_rate
action writes for its TxDefaultProfile leg.
With the option on, the slider needs no transaction. It is available
whenever the charger is up with SmartCharging and, on 2.0.1, has reported
which EVSE the connector is on; nothing is sent to a guessed EVSE. Its
value is the last limit the charger accepted, kept across transactions
and restored after a restart, saving only accepted values and only those
this mode set. A cancelled request reverts the display, in both modes.
The option is stored only while it is on and needs no migration, so a
charger that never enables it stays loadable by older releases. Settings
are now built from the keys their dataclass knows, so later releases can
add settings without breaking a rollback to this one.
The station slider and the transaction-bound mode are unchanged.
Co-authored-by: KingHavok <shane@shanewilliams.com.au>
0 commit comments