Salta ai contenuti
ricarica intelligente

OCPP 1.6J compatible

Questa pagina mostra la versione nightly. Passa alla versione release.

With OCPP the connection will be established from charger (client) to evcc (server). The charger needs to be able to reach evcc via the host name (functioning DNS resolution required!) or via the IP address on port 8887. By default, the first incoming connection with any station identifier is used. In order to be able to clearly assign several charging points, the respective station identifier (stationid: ) and connector number (connector: ) must be configured. Many wallboxes automatically add the station id to the backend URL, some have to do this manually ws://<evcc-host>:8887/<stationid>. If the charger supports sending metering values, try to adjust the interval to a short time span (< 10s) . Use your RFID tags (this allows e.g. vehicle identification) or set your charger to "free charging" or "autostart" to generate the transaction required for charging release.

If the charger does not offer any option to start transactions locally, the remotestart advanced option can be used to automatically start a transaction as soon as a vehicle is connected. This should only be necessary in exceptional cases.

Requirements:

  • If necessary, remove previously configured OCPP profiles (e.g. used for a different backend connection) in the charger configuration
  • Backend URL (Central System) in the charger configuration: ws://<evcc-host>:8887/ (possibly add stationid)
  • Protocol: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// or similar
  • No encryption, no authentication, no password
  • Local network connection

The specific configuration and the actual usable functionality depend on the charger model and its software.

Funzionalità supportate

  • Regolazione mA: Regolazione più fine della corrente di ricarica (mA invece di A) per sfruttare meglio il surplus solare.
  • RFID: Lettore di tessere RFID integrato per l’identificazione del veicolo.
  • 1P/3P: Commutazione automatica delle fasi. Utile per la ricarica con surplus solare.
  • Riducibile: La potenza assorbita può essere ridotta (ad es. § 14a EnWG). Vedi Limite esterno.

Parametri

NomeDescrizioneValoreLivello
stationidStation ID

Unique identifier of the charger. Automatically detected once the charger connects.

Esempio: EVB-P12354
facoltativo
connectorConnector number

For multi-connector stations. Numbering starts at 1.

Predefinito: 1
avanzato
chargingprofileCharging profile type

Use TxProfile only if the charger ignores TxDefaultProfile changes during an active transaction. Without a transaction, TxDefaultProfile is still used; an active transaction must report its ID. TxProfile expires with its transaction. The default profile is restored on the next control cycle. If evcc is offline then, the charger may charge without this limit until it reconnects.

Predefinito: TxDefaultProfile
avanzato
remotestartStart remote transaction on vehicle connection

Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction)

avanzato
idtagAuthentication token

This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction)

Esempio: evcc
avanzato
connecttimeoutTimeout for registration

Timeout for the registration of the charging point

Predefinito: 5m
avanzato
meterintervalTransmission interval for meter values

Time interval for transmission of meter values (MeterValueSampleInterval)

Predefinito: 10s
avanzato
metervaluesMeter values for transmission

Manual specification of the meter values to be configured (MeterValuesSampledData)

Esempio: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage
avanzato
Esempio di configurazione per evcc.yaml

Se preferisci non configurare il dispositivo dall’interfaccia, puoi usare questo blocco YAML.

chargers:
- name: my_charger
type: template
template: ocpp
stationid: EVB-P12354 # Station ID, Unique identifier of the charger. Automatically detected once the charger connects. (optional)
connector: 1 # Connector number, For multi-connector stations. Numbering starts at 1. (optional)
chargingprofile: TxDefaultProfile # Charging profile type, Use TxProfile only if the charger ignores TxDefaultProfile changes during an active transaction. Without a transaction, TxDefaultProfile is still used; an active transaction must report its ID. TxProfile expires with its transaction. The default profile is restored on the next control cycle. If evcc is offline then, the charger may charge without this limit until it reconnects. [TxDefaultProfile, TxProfile] (optional)
remotestart: # Start remote transaction on vehicle connection, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (Uses OCPP RemoteStartTransaction) (optional)
idtag: evcc # Authentication token, This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (Uses OCPP RemoteStartTransaction) (optional)
connecttimeout: 5m # Timeout for registration, Timeout for the registration of the charging point (optional)
meterinterval: 10s # Transmission interval for meter values, Time interval for transmission of meter values (MeterValueSampleInterval) (optional)
metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Meter values for transmission, Manual specification of the meter values to be configured (MeterValuesSampledData) (optional)