Gehversuche mit evvc --> läuft nicht #888
Replies: 5 comments 73 replies
-
Bitte noch nicht über den Dienst/Service starten, sondern die in den Anleitung angegeben, erstmal zum Laufen bekommen und dann als Dienst laufen lassen. |
Beta Was this translation helpful? Give feedback.
-
Hi bicaluv,
Hardware: RP3, go-E, Solaredge WR, Hyundai Kona+Ioniq Danke ;-) |
Beta Was this translation helpful? Give feedback.
-
Oh, Binary? Rechte? Bei dem Befehl kommt: habe versucht mit der Anleitung zurecht zu kommen, aber RP war schon immer das große Fragezeichen für mich. Wenn ich mir so deine Zeilen durchlese, habe ich vielleicht grundlegendes überlesen, nicht gelesen, vielleicht auch nicht durchgeführt, oder nicht verstanden.... |
Beta Was this translation helpful? Give feedback.
-
Hallo @Oberfranke , du hattest gestern die Installation nach der Installationsanleitung (https://github.com/andig/evcc/wiki/1.1.-Manual-installation#linux-installation) nebst detect schon mal auf deinem RP erfolgreich hinbekommen. Ich würde vorschlagen mach das einfach nochmal, und führe dir die folgenden Videos mal zu Gemüte:
Wenn du damit durch bist melde dich nochmal und dann gehen wir nach der folgenden Anleitung weiter: Wenn du die Anleitung in deutsch brauchst, übersetze einfach mit http://deepl.com |
Beta Was this translation helpful? Give feedback.
-
Versuch mal die config unten. Wenn meter, charger und vehicle sauber erkannt werden starte evcc erst mal von der Komandozeile mit debug: Wenn du Fehler bekommst, bitte die log Ausgaben hier posten. Jetzt aber die config mit den Fake meter Einträgen: uri: 0.0.0.0:7070 # uri for ui
interval: 10s # control cycle interval
# log settings
log: trace
levels:
core: trace
lp-1: trace
# javascript for test purposes only
javascript:
- vm: shared
script: |
state = {
residualpower: 200,
pvpower: -3000,
batterypower: 200,
gridpower: -2000,
chargepower: 0,
maxcurrent: 0,
};
function get() {
console.log("state:", JSON.stringify(state));
}
function set() {
console.log(param+":", val);
console.log("state:", JSON.stringify(state));
}
# meter definitions
# name can be freely chosen and is used as reference when assigning meters to site and loadpoints
# for examples see https://github.com/andig/evcc-config#meters
meters:
- name: pv
type: default
power:
type: js
vm: shared
script: state.pvpower += 100*Math.random();
- name: battery
type: default
power:
type: js
vm: shared
script: state.batterypower;
soc:
type: js
vm: shared
script: "30"
#- name: Fronius Solar API V1 (PV Meter/ HTTP)
# type: custom
# sample: |
# power:
# source: http
# uri: http://192.168.178.80/solar_api/v1/GetPowerFlowRealtimeData.fcgi
# jq: if .Body.Data.Site.P_PV == null then 0 else .Body.Data.Site.P_PV end
#- name: Tesla Powerwall (Battery Meter)
# type: tesla
# sample: |
# uri: http://192.168.178.81/
# usage: battery
# charger definitions
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for examples see https://github.com/andig/evcc-config#chargers
chargers:
- name: go-eCharger
type: go-e # go-eCharger
uri: http://192.168.178.79 # go-e ip address (local)
# vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for examples see https://github.com/andig/evcc-config#vehicles
vehicles:
- name: bmw
type: bmw
title: MINI Cooper SE # display name for UI
capacity: 65 # kWh
user: UserName # user
password: UserPassword # password
vin: WMW # optional
# site describes the EVU connection, PV and home battery
site:
title: Home # display name for UI
meters:
# grid: grid # grid meter
pv: pv # pv meter
battery: battery # battery meter
prioritySoC: 60 # give home battery priority up to this soc (0 to disable)
# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
- title: Garage # display name for UI
charger: go-eCharger
vehicle: bmw
# vehicles: # use if multiple vehicles allowed to charge on this loadpoint
# - ID.3
# - e-Up
mode: pv
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
mode: charging
# poll interval defines how often the vehicle API may be polled if NOT charging
interval: 60m
min: 0 # immediately charge to 0% regardless of mode unless "off" (disabled)
target: 100 # always charge to 100%
estimate: false # set true to interpolate between api updates
levels: # target soc levels for UI
- 30
- 50
- 80
- 100
onDisconnect: # set defaults when vehicle disconnects
mode: pv # switch back to pv mode
targetSoC: 100 # charge to 100%
phases: 3 # ev phases (default 3)
enable: # pv mode enable behavior
delay: 1m # threshold must be exceeded for this long
threshold: 0 # minimum export power (W). If zero, export must exceed minimum charge power to enable
disable: # pv mode disable behavior
delay: 5m # threshold must be exceeded for this long
threshold: 200 # maximum import power (W)
guardduration: 5m # switch charger contactor not more often than this (default 10m)
mincurrent: 6 # minimum charge current (default 6A)
maxcurrent: 16 # maximum charge current (default 16A)
# mqtt message broker
mqtt:
# broker: localhost:1883
# topic: evcc # root topic for publishing, set empty to disable
# user:
# password:
# influx database
influx:
# url: http://localhost:8086
# database: evcc
# user:
# password:
# 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}
services:
# - type: pushover
# app: # app id
# recipients:
# - # list of recipient ids
# - type: telegram
# token: # bot id
# chats:
# - # list of chat ids
# - type: email
# uri: smtp://<user>:<password>@<host>:<port>/?fromAddress=<from>&toAddresses=<to> |
Beta Was this translation helpful? Give feedback.
-
Guten Morgen zusammen,
habe schwierigkeiten evcc zum laufen zu bringen. Kann mir jemand weiterhelfen?
Raspberry läuft. EVCC installiert, aber wenn ich es starte kommt:
Glaube aber auch, dass ich Yaml auch nicht richtig habe.
Technisch bin ich was Raspberry betrifft ein Anfänger. Sind gerade meine ersten geh - Versuche. Bin aber stolz wie bolle, dass ich OS auf das RP bekommen hab :-)
VG Oberfranke
Beta Was this translation helpful? Give feedback.
All reactions