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
I am running evcc for almost one year and until December 2023 it worked absolutly fine. It is running as HACS Add-on in Home Assistant. And this is running in a "virtuel maschine" on a synology DS1522. Any idea, what I can do? Thanks!!!
On port 7070 I do get this error:
Fehler beim Starten
cannot create vehicle 'Citroen'
cannot create vehicle type 'template'
invalid key: targetsoc
I did get nearly the same error only with the Hyundai. It changes after a reboot sometimes.
I am running evcc for almost one year and until December 2023 it worked absolutly fine. It is running as HACS Add-on in Home Assistant. And this is running in a "virtuel maschine" on a synology DS1522. Any idea, what I can do? Thanks!!!
On port 7070 I do get this error:
I did get nearly the same error only with the Hyundai. It changes after a reboot sometimes.
This is my config:
meters:
type: template
template: rct-power
usage: grid
host: 192.168.178.197
type: template
template: rct-power
usage: pv
host: 192.168.178.197
type: template
template: rct-power
usage: battery
host: 192.168.178.197
chargers:
template: keba
host: 192.168.178.169
serial: *****
name: Keba Wallbox
tariffs:
currency: EUR
grid:
type: fixed
price: 0.3368 # [currency]/kWh
feedin:
type: fixed
price: 0.08 # [currency]/kWh
vehicles:
type: template
template: hyundai
title: Ioniq5
user: *****
password: *****
vin: *****
capacity: 72
phases: 3
icon: car
cache: 15m
language: de
mode: minpv
targetSoc: 80
type: template
template: citroen
title: c5 aircross hybrid
user: *****
password: *****
vin: *****
capacity: 12
phases: 1
icon: car
cache: 15m
language: de
mode: pv
targetSoc: 100
loadpoints:
charger: Keba Wallbox
mode: now
phases: 3
mincurrent: 10
maxcurrent: 16
resetOnDisconnect: true
site:
title: F19 Home
meters:
grid: my_grid
pvs:
- my_pv
The text was updated successfully, but these errors were encountered: