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
According to the info related to battery setup, the battery locking should be applied during fast charging as well as planned charging.
When selecting fast charging the locking is applied and after a cycle the battery utilisation goes down to zero and the power is pulled from the grid.
Using a planning the system is not applying the battery locking and continues to charge from the battery.
Graphical UI configuration:
Steps to reproduce
Failure steps:
Enable min + PV
Setup a charging plan
Check the locking is applied or not
Success steps:
Enable fast
Check the locking is applied or not.
Configuration details
The setup of PV, battery and car are done via the graphical UI.Screenshot is shared above.## minimal configuration examplenetwork:
# schema is the HTTP schema# setting to `https` does not enable https, it only changes the way URLs are generatedschema: http# host is the hostname or IP address# if the host name contains a `.local` suffix, the name will be announced on MDNS# docker: MDNS announcements don't work. host must be set to the docker host's name.host: evcc.local# port is the listening port for UI and api# evcc will listen on all available interfacesport: 7070site:
title: Home # display name for UImeters:
grid: SMA_Home_Manager# pv:# - SMA_SB4.0# - SMA_TRI6.0#battery:# - SMA_SBS5.0residualPower: 100sponsortoken: xxxx# define your loadpoints according your needs# see https://docs.evcc.io/en/docs/reference/configuration/loadpointsloadpoints:
- title: Garage # display name for UIcharger: Alfen_Eve # charger# vehicle: Tesla # default vehiclemode: MinPV # charge mode (off, now, minpv, pv)# meter definitions# name can be freely chosen and is used as reference when assigning meters to site and loadpoints# for documentation see https://docs.evcc.io/docs/devices/metersmeters:
- name: SMA_Home_Managertype: templatetemplate: sma-home-managerusage: gridhost: 192.168.x.x # IP address or hostname#- name: SMA_SBS5.0# type: template# template: sma-sbs-modbus# usage: battery# Modbus TCP# modbus: tcpip# id: 3# host: 192.168.x.x # Hostname# port: 502 # Port# capacity: 11 # Battery capacity in kWh (optional)# - name: SMA_SB4.0# type: template# template: sma-inverter-modbus# usage: pv# # Modbus TCP# modbus: tcpip# id: 3# host: 192.168.x.x # Hostname# port: 502 # Port# - name: SMA_TRI6.0# type: template# template: sma-inverter-modbus# usage: pv# # Modbus TCP# modbus: tcpip# id: 3# host: 192.168.x.x # Hostname# port: 502 # Port# replace with your real charger# see https://docs.evcc.io/docs/devices/chargerschargers:
- name: Alfen_Evetype: templatetemplate: alfen# Modbus TCPmodbus: tcpipid: 1host: 192.168.0.103 # Hostnameport: 502# Port# replace with your real vehicle (optional)# see https://docs.evcc.io/docs/devices/vehiclesvehicles:
# - name: Tesla# type: template# template: tesla# title: Tesla # Will be displayed in the user interface (optional)# accessToken: !secret access_token# refreshToken: !secret refresh_token# capacity: 75 # Battery capacity in kWh (optional)# icon: car # Icon as shown in user interface (optional)# phases: 3 # The maximum number of phases which can be used (optional)# commandProxy: https://tesla.evcc.io/ # When using a TWC3 (or other 'dumb' charger not capable of control), evcc can manage the charge directly by communicating with the vehicle through a Command Proxy. By default, the proxy provided by evcc is used. With this parameter, you set the base URL of a custom Command Proxy to use instead of the default evcc one. See for example https://github.com/wimaha/TeslaBleHttpProxy for a proxy sending commands via bluetooth. (optional)# mode: MinPV # Possible values are Off, Now, MinPV and PV, or empty if none should be set (optional)# minCurrent: 6 # The minimum amperage per connected phase with which the car should be charged (optional)# maxCurrent: 16 # The maximum amperage per connected phase with which the car shuold be charged (optional)# priority: 5 # Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating pv energy (optional)# enter your real grid tariff and feed-in price# see https://docs.evcc.io/docs/devices/tariffs#tariffs:# currency: EUR# grid:# type: fixed# price: 0.31 # EUR/kWh# feedin:# type: fixed# price: 0.03 # EUR/kWh# tariffs:# currency: EUR# grid:# type: template# template: entsoe# securitytoken: xxxxx # Registration and subsequent helpdesk request required. Details on the process can be found here https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_authentication_and_authorisation (optional)# domain: BZN|BE # see https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas (optional)# charges: 0.0777455 # Additional fixed charge per kWh (e.g. 0.05 for 5 cents) (optional)# tax: 0.06 # Additional percentage charge (e.g. 0.2 for 20%) (optional)# feedin:# type: template# template: entsoe# securitytoken: xxxxx# domain: BZN|BEhems:
type: smaallowcontrol: falseplant: xxxxx
Describe the bug
According to the info related to battery setup, the battery locking should be applied during fast charging as well as planned charging.
When selecting fast charging the locking is applied and after a cycle the battery utilisation goes down to zero and the power is pulled from the grid.
Using a planning the system is not applying the battery locking and continues to charge from the battery.
Graphical UI configuration:
Steps to reproduce
Failure steps:
Success steps:
Configuration details
Log details
What type of operating system are you running?
HomeAssistant Add-on
Nightly build
Version
No response
The text was updated successfully, but these errors were encountered: