Beginner Frage Installation EVCC OSX

[gerikern]

Ich versuche seit Tagen die EVCC zu starten aber klappt nicht. Als Beginner alles nach Wiki durchgeführt evcc startet jeweils im Demo mode evcc -h funktioniert ebenso detect. Wohin muss ich die yaml kopieren bei OSX? I Moment evcc sowie evcc.yaml in einem Ordner.

 /EV/evcc ; exit;
[main  ] ERROR 2021/05/22 11:33:34 missing evcc config - switching into demo mode
[main  ] INFO 2021/05/22 11:33:34 listening at 0.0.0.0:7070

[andig]

Zeig mal bitte ein ls aus dem Ordner

[gerikern]

GeroldKrnsiMac3:EV geroldkern$ ls
evcc evcc.yaml

[andig]

Die Config muss in cwd, /etc oder ~ liegen. An der Stelle des Binaries nutzt sie nichts.

@DerAndereAndi ist es üblich unter Linux die Config beim Binary zu haben? Wäre umsetzbar, kommt mir aber komisch vor?

[gerikern]

mit dem befehl detect habe ich folgendes hinbekommen..!

+-----------------+----------+----------+---------------------------------------------------------------------------------------------------------+
|       IP        | HOSTNAME |   TASK   |                                                 DETAILS                                                 |
+-----------------+----------+----------+---------------------------------------------------------------------------------------------------------+
| 192.168.178.110 |          | shm      | {"IP":"192.168.178.110","ShmResult":{"Serial":"1900242725","Http":false}}                               |
+-----------------+----------+----------+---------------------------------------------------------------------------------------------------------+
| 192.168.178.170 |          | sunspec  | {"IP":"192.168.178.170","Port":502,"ModbusResult":{"SlaveID":126,"Model":1,"Point":"Mn","Value":"SMA"}} |
+                 +----------+----------+---------------------------------------------------------------------------------------------------------+
|                 |          | inverter | {"IP":"192.168.178.170","Port":502,"ModbusResult":{"SlaveID":126,"Model":103,"Point":"W","Value":131}}  |
+                 +----------+----------+---------------------------------------------------------------------------------------------------------+
|                 |          | strings  | {"IP":"192.168.178.170","Port":502,"ModbusResult":{"SlaveID":126,"Model":160,"Point":"N","Value":2}}    |
+-----------------+----------+----------+---------------------------------------------------------------------------------------------------------+

[DerAndereAndi]

Und die Konfigurationsdatei sieht wie aus? Danach hatte ich auch gefragt

[gerikern]

uri: 0.0.0.0:7070 # uri for ui
interval: 10s # control cycle interval

# sponsor token enables optional features (request at https://cloud.evcc.io)
# sponsortoken:

# log settings
log: error
levels:
  core: debug
  lp-1: debug
  lp-2: debug

# 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:
- type: modbus
  uri: 192.168.178.170:502
  id: 126

# 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:
- type: shelly
  uri: http://192.168.178.102  # shelly device ip address (local)
  channel: 0  # shelly device relay channel 
  standbypower: 15  # treat as charging above this power

hems:
  type: sma
  allowcontrol: false # set true to allow SHM controlling charger in PV modes

# 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: wallbe # charger
  meters:
    charge: charge # charge meter
  vehicle: audi
  # 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
  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: 10m # 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)

# 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>

[DerAndereAndi]

Ja, das kann nicht funktionieren. Da hilft dir auch kein Raspberry Pi. Bitte lies die Dokumentation genau und mach nur Änderungen die für dich klar sind. Momentan ist das ziemlich wild. Ein paar Beispiele:

• Du definierst ein Meter, das hat aber keinen name und kann damit auch nirgendwo referenziert werden, gleiches für deinen Charger
• Du definierst einen SMA HEMS, aber definiert keinen Meter der das HEMS benutzt.
• Unter site referenzierst du 3 meter die es nicht gibt
• Unter loadpoints referenzierst du einen charger, und ein vehicle die es nicht gibt

Das ist alles dokumentiert.

[gerikern]

olala danke vielmals

[thierolm]

Versuche einfach mal nach der Step by Step Anleitung unter https://github.com/andig/evcc/wiki/1.3.-Manual-configuration#step-by-step-configuration-and-test-example unter Berücksichtigung von @DerAndereAndi 's Hinweisen vorzugehen ...