Sehr geehrtes evcc-Team,
Ich bin mir nicht 100% sicher ob das Problem seitens EVCC liegt es besteht aber schon eine gewisse Wahrscheinlichkeit.
Meine Anlage (10kW) Fronius Gen24 ist derzeit seitens Energie AG noch nicht abgenommen und DARF deshalb nicht ins Netz liefern.
Nun habe ich vorgestern EVCC mit dem WR verbunden und pv-, grid- und batterymeter configuriert.
Allerdings speißt der WR plötzlich fröhlich und munter ins Netz ein. Ich dachte EVCC ließt nur Werte vom WR? Kann der Fehler bei evcc liegen? Was ist da los?
Ein 10min Ausstecken des Raspberry Pis hat nichts verbessert.
Ich dachte immer Evcc ließt ausschließlich vom WR
Gruß
Stadlaa
Steps to reproduce
-
Configuration details
Konfiguration (/etc/evcc.yaml):
network:
# schema is the HTTP schema
# setting to `https` does not enable https, it only changes the way URLs are generated
schema: 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 interfaces
port: 7070
interval: 10s # control cycle interval
# database configuration for persisting charge sessions and settings
database:
type: sqlite
# sponsor token: *****
# trial token, valid until 2024-03-09
sponsortoken: *****
# log settings
log: info
levels:
site: debug
lp-1: debug
lp-2: debug
cache: error
db: error
# modbus proxy for allowing external programs to reuse the evcc modbus connection
# each entry will start a proxy instance at the given port speaking Modbus TCP and
# relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP)
modbusproxy:
- port: 5200
uri: 10.0.0.230:502
# rtu: true
# readonly: true
# 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/meters
meters:
- name: gen24_grid
type: template
template: fronius-gen24
usage: grid
host: 10.0.0.230 # IP-Adresse oder Hostname
port: 502 # Port (optional)
- name: gen24_pv
type: template
template: fronius-gen24
usage: pv
host: 10.0.0.230 # IP-Adresse oder Hostname
port: 502 # Port (optional)
- name: gen24_batt
type: template
template: fronius-gen24
usage: battery
host: 10.0.0.230 # IP-Adresse oder Hostname
port: 502 # Port (optional)
# charger definitions
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for documentation see https://docs.evcc.io/docs/devices/chargers
chargers:
- name: WattPilot
type: template
template: fronius-wattpilot
host: 10.0.0.120 # IP-Adresse oder Hostname
password: *****
# vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for documentation see https://docs.evcc.io/docs/devices/vehicles
vehicles:
- name: ZOE
type: template
template: renault
title: ZOE # Wird in der Benutzeroberfläche angezeigt (Optional)
user: *****
password: *****
vin: *****
capacity: 43 # Akkukapazität in kWh (Optional)
# mode: pv
priority: 5
# site describes the EVU connection, PV and home battery
site:
title: Zuhause # display name for UI
meters:
#grid: FroniusSmartMeter # grid meter
grid: gen24_grid
pv: gen24_pv
# - pv # list of pv inverters/ meters
battery: gen24_batt
# - battery # list of battery meters
# aux:
# - aux # list of auxiliary meters for adjusting grid operating point
residualPower: 0 # additional household usage margin
maxGridSupplyWhileBatteryCharging: 50 # ignore battery charging if AC consumption is above this value
# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
- title: Garage # display name for UI
charger: WattPilot # charger
#meter: # charge meter
mode: "pv" # (set default charge mode:"off","pv",minpv","now" use "off" to disable by default if charger is publicly available
vehicle: ZOE # set default vehicle (disables vehicle detection)
phases: 0 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
# remaining settings are experts-only and best left at default values
priority: 5 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
soc:
# polling defines usage of the vehicle APIs
# Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery
# or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.
poll:
# poll mode defines under which condition the vehicle API is called:
# charging: update vehicle ONLY when charging (this is the recommended default)
# connected: update vehicle when connected (not only charging), interval defines how often
# always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
mode: always
# poll interval defines how often the vehicle API may be polled if NOT charging
interval: 30m
estimate: true # set false to disable interpolating between api updates (not recommended)
enable: # pv mode enable behavior
delay: 1m # threshold must be exceeded for this long
threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
disable: # pv mode disable behavior
delay: 3m # threshold must be exceeded for this long
threshold: 0 # maximum import power (W)
guardDuration: 5m # switch charger contactor not more often than this (default 5m)
influx:
url: http://localhost:8086
database: evcc # InfluxDB v2.x uses term `bucket` but for compatibility still named `database` here
token: *****
org: Biohof_Stadler
# push messages
messaging:
events:
start: # charge start event
title: Charge started
msg: Started charging in "${mode}" mode
stop: # charge stop event
title: Charge finished
msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
connect: # vehicle connect event
title: Car connected
msg: "Car connected at ${pvPower:%.1fk}kW PV"
disconnect: # vehicle connected event
title: Car disconnected
msg: Car disconnected after ${connectedDuration}
soc: # vehicle soc update event
title: Soc updated
msg: Battery charged to ${vehicleSoc:%.0f}%
guest: # vehicle could not be identified
title: Unknown vehicle
msg: Unknown vehicle, guest connected?
services:
Version: `0.126.4`
Describe the bug
Sehr geehrtes evcc-Team, Ich bin mir nicht 100% sicher ob das Problem seitens EVCC liegt es besteht aber schon eine gewisse Wahrscheinlichkeit.
Meine Anlage (10kW) Fronius Gen24 ist derzeit seitens Energie AG noch nicht abgenommen und DARF deshalb nicht ins Netz liefern.
Nun habe ich vorgestern EVCC mit dem WR verbunden und pv-, grid- und batterymeter configuriert.
Allerdings speißt der WR plötzlich fröhlich und munter ins Netz ein. Ich dachte EVCC ließt nur Werte vom WR? Kann der Fehler bei evcc liegen? Was ist da los?
Ein 10min Ausstecken des Raspberry Pis hat nichts verbessert.
Ich dachte immer Evcc ließt ausschließlich vom WR
Gruß Stadlaa
Steps to reproduce
-
Configuration details
Log details
What type of operating system are you running?
Linux
Version
0.126.4