Active Deprecation Index

This page lists all public API components that are currently deprecated in EVerest. It is at least updated with every stable release.

Each entry records the deprecated component, the release in which it was deprecated, the earliest release in which it may be removed (following the minimum deprecation period), and a link to the corresponding migration guide.

Component	Deprecated in	Earliest removal	Migration guide
OCPP module (OCPP 1.6), superseded by OCPPmulti	2026.10.0	2027.04.0	Migrate to the Combined OCPP Module
OCPP201 module (OCPP 2.0.1 / 2.1), superseded by OCPPmulti	2026.10.0	2027.04.0	Migrate to the Combined OCPP Module
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.
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.