Kaco Blueplanet über modbus einbinden #811

jojo8897 · 2021-03-28T11:10:22Z

jojo8897
Mar 28, 2021

Hallo zusammen,
erst einmal vielen Dank für das tolle Projekt!
Ich Habe eine 6.05KwP Anlage neu, zwei Keba Boxen und einen ID3, der Wechselrichter ist ein Kaco Blueplanet 6.5TL3

Ich versuche es derzeit mit folgender Konfiguration:

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

# 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
power:
type: modbus
uri: 192.168.179.189:502 # IP address of the SolarLog device and ModBus port address
id: 1
register: # manual register configuration
address: 40085
type: holding
decode: uint16

# 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: keba
type: keba
uri: 192.168.179.179
serial: 09834567

evcc ist per Docker auf der Synology, ich bekomme derzeit folgende Fehlermeldung:

While parsing config: yaml: line 18: mapping values are not allowed in this context

Das ist diese: register: # manual register configuration
Hat evtl. jemand den Kaco schon eigebunden und kann mir hier die richtigen Werte geben?

DANKE
LG Jörg

Answered by premultiply

Mar 28, 2021

Das ist ein stinknormaler SunSpec-kompatibler WR.
Also https://github.com/andig/evcc-config#meter-generic-sunspec-pv-inverter-pv-meter

Viel wichtiger ist allerdings die Frage was hier das Gridmeter/der Netzzähler ist?

View full answer

premultiply · 2021-03-28T11:21:25Z

premultiply
Mar 28, 2021
Maintainer

Bitte erstmal gescheit formatieren. Durch den Markup-Unfall kann man nichts erkennen.

2 replies

jojo8897 Mar 28, 2021
Author

Sorry, nicht gesehen das es so ein Durcheinander war :(

bicaluv Mar 28, 2021
Sponsor

Auch Einrückungen und "-" etc. sind in der yaml-Datei wichtig. Bei dir ist oben nichts eingerückt.

premultiply · 2021-03-28T12:17:40Z

premultiply
Mar 28, 2021
Maintainer

Das ist ein stinknormaler SunSpec-kompatibler WR.
Also https://github.com/andig/evcc-config#meter-generic-sunspec-pv-inverter-pv-meter

Viel wichtiger ist allerdings die Frage was hier das Gridmeter/der Netzzähler ist?

2 replies

jojo8897 Mar 28, 2021
Author

Hallo Danke für die Antwort.
Gridmeter wird das USB-IEC-Interface von ELV eingebunden dann wahrscheinlich über Volkszähler, geht aber noch nicht warte noch auf den Zählertausch, habe noch einen alten Zähler den man nicht auslesen kann.

Wenn ich das so einbaue:

- type: modbus
  uri: 192.168.179.189:502
  id: 1

bekomme ich wieder folgende Fehlermeldung:

panic: invalid log level 
goroutine 1 [running]:
github.com/andig/evcc/util.LogLevelToThreshold(0x0, 0x0, 0xc0004c1605)
	/build/util/log.go:113 +0x1b3
github.com/andig/evcc/util.LogLevel(0xc0004c15a0, 0x5, 0xc00044fb00)
	/build/util/log.go:89 +0x102
github.com/andig/evcc/cmd.run(0x215ff20, 0x2197eb0, 0x0, 0x0)
	/build/cmd/root.go:140 +0xbe
github.com/spf13/cobra.(*Command).execute(0x215ff20, 0xc0000322c0, 0x0, 0x0, 0x215ff20, 0xc0000322c0)
	/go/pkg/mod/github.com/spf13/[email protected]/command.go:854 +0x29d
github.com/spf13/cobra.(*Command).ExecuteC(0x215ff20, 0x44604a, 0x2102260, 0xc000000180)
	/go/pkg/mod/github.com/spf13/[email protected]/command.go:958 +0x349
github.com/spf13/cobra.(*Command).Execute(...)
	/go/pkg/mod/github.com/spf13/[email protected]/command.go:895
github.com/andig/evcc/cmd.Execute()
	/build/cmd/root.go:133 +0x31
main.main()
	/build/main.go:10 +0x20

Wenn ich es so mache:

  power:
    type: modbus
    uri: 192.168.179.189:502 # IP address of the SolarLog  device and ModBus port address
    id: 1  
      register: 113 # manual register configuration
      address: 40160
      type: holding
      decode: uint16

kommt das:
While parsing config: yaml: line 18: mapping values are not allowed in this context

DANKE fürs helfen

premultiply Mar 28, 2021
Maintainer

Mit der Formatierung deiner Konfig-Datei stimmt was nicht.
Bitte mal die gesamte Datei 1:1 und als Code formatiert hier posten.

jojo8897 · 2021-03-28T12:48:31Z

jojo8897
Mar 28, 2021
Author

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

# 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
  power:
    type: modbus
    uri: 192.168.179.189:502 # IP address of the SolarLog  device and ModBus port address
    id: 1  
      register: 113 # manual register configuration
      address: 40160
      type: holding
      decode: uint16
      

# 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: keba
  type: keba
  uri: 192.168.179.179
  serial: 09834567

# 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:
- type: id
  title: ID.3 # display name for UI
  capacity: 50 # kWh
  user: [email protected] # user
  password: xxx # password
  vin: xxxxx # optional

# site describes the EVU connection, PV and home battery
site:
  title: Garage  # display name for UI

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
- title: Garage # display name for UI
  charger: keba # charger
  meters:
#    charge: charge # charge meter
#  vehicle: id
  # 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>

8 replies

premultiply Mar 28, 2021
Maintainer

Also eher so in der Art:

# 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: grid
  type: default
  power: # power reading
    type: http # use http plugin
    uri: http://demo.volkszaehler.org/api/data/<uuid>.json?from=now
    jq: .data.tuples[0][1] # parse response json
- name: pv
  type: modbus
  uri: 192.0.2.2:502
  id: 1

# 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: keba1
  type: keba
  uri: 192.0.2.2
- name: keba2
  type: keba
  uri: 192.0.2.2

# 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: id3
  type: id
  title: ID.3 # display name for UI
  capacity: 50 # kWh
  user: # user
  password: # password
  vin: WVWZZZ... # 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

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
- title: Keba 1 # display name for UI
  charger: keba1 # charger
  vehicle: id3
  # 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: true # set true to interpolate between api updates
    levels: # target soc levels for UI
    - 30
    - 50
    - 80
    - 100
  phases: 3 # ev phases (default 3)
  enable: # pv mode enable behavior
    delay: 2m # 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: 2m # threshold must be exceeded for this long
    threshold: 0 # maximum import power (W)
  guardduration: 10m # switch charger contactor not more often than this (default 10m)
  mincurrent: 6 # minimum charge current (default 6A)
  maxcurrent: 16 # maximum charge current (default 16A)

jojo8897 Mar 28, 2021
Author

@premultiply
Vielen vielen Dank für deinen Einsatz, ich warte dann jetzt erstmal bis zum Zählertausch damit ich dann auch den Meter habe :) und arbeite dann mit deiner Config.
DANKE

jojo8897 Mar 28, 2021
Author

Also es sieht so schon besser aus :)
Kommt jetzt das:

2021/03/28 17:52:27 unrecognised model identifier skipped @ offset: 64204, 908
[main  ] FATAL 2021/03/28 17:52:28 cannot create vehicle 'id3': cannot create type 'id': login failed: Get "/signin-service/v1/a24fba63-34b3-4d43-b181-942111e6bda8@apps_vw-dilab_com/terms-and-conditions?relayState=c6d0a5200125190a79c91211021253820db3d3cc&updated=dataprivacy": unsupported protocol scheme ""

DerAndereAndi Mar 28, 2021

Du musst dich im Web Interface von VW einloggen und 1 Mal die aktualisierten Term & Conditions akzeptieren.

jojo8897 Mar 28, 2021
Author

Läuft,,, DANKE

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Kaco Blueplanet über modbus einbinden #811

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 3 comments 12 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Kaco Blueplanet über modbus einbinden #811

jojo8897 Mar 28, 2021

Replies: 3 comments · 12 replies

premultiply Mar 28, 2021 Maintainer

jojo8897 Mar 28, 2021 Author

bicaluv Mar 28, 2021 Sponsor

premultiply Mar 28, 2021 Maintainer

jojo8897 Mar 28, 2021 Author

premultiply Mar 28, 2021 Maintainer

jojo8897 Mar 28, 2021 Author

premultiply Mar 28, 2021 Maintainer

jojo8897 Mar 28, 2021 Author

jojo8897 Mar 28, 2021 Author

DerAndereAndi Mar 28, 2021

jojo8897 Mar 28, 2021 Author

jojo8897
Mar 28, 2021

Replies: 3 comments 12 replies

premultiply
Mar 28, 2021
Maintainer

jojo8897 Mar 28, 2021
Author

bicaluv Mar 28, 2021
Sponsor

premultiply
Mar 28, 2021
Maintainer

jojo8897 Mar 28, 2021
Author

premultiply Mar 28, 2021
Maintainer

jojo8897
Mar 28, 2021
Author

premultiply Mar 28, 2021
Maintainer

jojo8897 Mar 28, 2021
Author

jojo8897 Mar 28, 2021
Author

jojo8897 Mar 28, 2021
Author