The RsIskraMeter deprecates its meter implementation_id in favor of main. |
2026.10.0 |
2027.04.0 |
Change implementation_id: meter to implementation_id: main in the config connection |
The evse_id topics of the evse_manager_consumer_API AsyncAPI
(e2m/evse_id and m2e/evse_id/get), superseded by the get_evse
command |
2026.10.0 |
2027.04.0 |
Use the get_evse command, which provides both the eMI3-format EVSE ID
(ISO 15118-2 Annex H) and the DIN 70121 EVSE ID (DIN SPEC 91286) |
manager --conf, alias of --config
(see Manager Command Line Options)
|
2026.10.0 |
2027.04.0 |
Replace --conf <path> with --config <path> in start scripts and
service units. Passing both is rejected; using --conf logs a warning
at startup. |
manager --db-init, now a no-op
(see Manager Command Line Options)
|
2026.10.0 |
2027.04.0 |
Drop the flag. Seeding the database from the YAML config when it holds no
valid configuration is the default with --config --db. Use the
experimental --reset-from-yaml to force re-seeding. |
settings: block in the EVerest config file
(see Manager Settings)
|
2026.10.0 |
2027.04.0 |
Move the keys of the block into a settings file and pass it with
manager --settings <path>. Drop www_dir, controller_port,
controller_rpc_timeout_ms and prefix/config_file, which have
no effect; run_as_user has no settings file equivalent, see its own
entry. The manager logs a warning at startup while the block is used. |
ocpp_consumer_API: is_connected variable and its
get_is_connected request/reply (operations receive_is_connected,
send_request_get_is_connected, receive_reply_get_is_connected,
schema ConnectedStatus), superseded by connection_status
|
2026.10.0 |
2027.04.0 |
Subscribe to receive_connection_status (or request it via
send_request_get_connection_status) and read its connected
property; the message also carries the details of the connection the
status refers to. |
ocpp_consumer_API and ocpp interface: OCPP 1.6 key-only variable
addressing (empty component.name, variable.name = configuration
key) in get_variables, set_variables and monitor_variables,
superseded by canonical component/variable addressing
|
2026.10.0 |
2027.04.0 |
Migration from OCPP 1.6 key addressing. OCPPmulti
logs a warning naming the canonical address on the first use of each
legacy key. |
EvseManager configuration option
lock_connector_in_state_b: false |
2026.10.0 |
2027.04.0 |
Remove the option and set unlock_when_deauthorized: true instead.
The connector then stays unlocked in CP state B until the session is
authorized, which covers the original use case (no lock on plug-in
before authorization). Unlike the deprecated option it keeps the
connector locked while an authorized session is paused in state B and
does not lock in state C/D without authorization or closed relays.
Both options violate IEC 61851-1:2019 D.6.5 Table D.9 line 4 and must
not be used in public environments; the module logs a warning at
startup for either. |
API module (everest_api/<connector>/cmd/* and
everest_api/<connector>/var/* topics), superseded by the
EVerest API modules |
2026.10.0 |
2027.04.0 |
Replace the module with the EVerest API modules covering the topics in use:
evse_manager_consumer_API for charging control (enable_disable,
pause_charging, resume_charging, stop_charging,
force_unlock, uk_random_delay) and EVSE state (session_info,
ev_info, hardware_capabilities, powermeter, limits,
selected_protocol), external_energy_limits_consumer_API for
set_limit_amps, set_limit_amps_phases and set_limit_watts,
ocpp_consumer_API for ocpp/var/connection_status and
ocpp/var/charging_schedules, and error_history_consumer_API for
errors/var/active_errors. info/var/info (charger information) has
no replacement. The module logs a deprecation warning at startup. |
EvAPI module (everest_api/ev_connectors
and everest_api/<connector>/var/* topics) |
2026.10.0 |
2027.04.0 |
No replacement. The module logs a deprecation warning at startup. |
error_history_consumer_API: severity property of ErrorObject
(all messages carrying errors: get_errors, active_errors,
error_raised, error_cleared), the severity_filter argument of
get_errors, and the Severity and SeverityFilter schemas
|
2026.10.0 |
2027.04.0 |
No replacement: EVerest defines no clear semantics for error severity.
Stop reading severity from error objects and do not treat it as
required; drop severity_filter from get_errors requests and
filter by type_filter, origin_filter or state_filter instead. |
settings.run_as_user in the EVerest config file
|
2026.10.0 |
2027.04.0 |
Start the manager as the unprivileged user from the service manager
instead, e.g. User=everest in the systemd unit, and grant
privileged modules file capabilities (see
Security Best Practices). The manager logs a
warning at startup when the setting is used. |
capabilities key of a module entry in the EVerest config file
(active_modules.<id>.capabilities)
|
2026.10.0 |
2027.04.0 |
Remove the key. Modules declare their capabilities in their
manifest.yaml, and the deployment grants them as file capabilities:
the everest_file_capabilities class in meta-everest, or
applications/utils/scripts/set_module_capabilities.py elsewhere (see
Security Best Practices). The key is already
ignored, and the manager logs a warning at startup. |
EvseV2G module (DIN SPEC 70121 and
ISO 15118-2 on the C implementation), superseded by
Evse15118D20, which runs DIN SPEC
70121, ISO 15118-2 and ISO 15118-20 on the C++ ISO 15118 stack |
2026.10.0 |
2027.04.0 |
Migrate from EvseV2G and IsoMux to Evse15118D20. The module logs a deprecation warning
at startup. SAE J2847/2 bidirectional power transfer is only available in
EvseV2G until the C++ stack provides it. |
IsoMux module (multiplexer between EvseV2G
and Evse15118D20), superseded by
Evse15118D20 alone |
2026.10.0 |
2027.04.0 |
Migrate from EvseV2G and IsoMux to Evse15118D20. The module logs a deprecation warning
at startup. |
Evse15118D20 configuration option
logging_path |
2026.10.0 |
2027.04.0 |
Remove the option. The built-in session logger is removed and the
option has no effect; capture sessions with PacketSniffer, tcpdump or
Wireshark instead. |
OCPPmulti configuration option
EverestDeviceModelDatabasePath |
2027.04.0 |
2027.10.0 |
Nothing to migrate by hand. At the first start the module takes the
database over into DeviceModelDatabasePath and renames it to
*.migrated, see Migrate to the Combined OCPP Module. Remove the
option from the configuration afterwards. |