search

evcc-io / evcc

Sonne tanken ☀️🚘
https://evcc.io
MIT License
3.29k stars 604 forks source link

Does not work on BMW, Solax, Innogy eBox #9248

Closed bertos03 closed 1 year ago

bertos03 commented 1 year ago

Describe the bug

No connection to the Solax Inverter is established. No connection to the BMW backend is established. No connection to the Innogy eBox is established.

Modbus TCP connection to the inverter and the eBox is tested manually with a Python script - it works.

Steps to reproduce

  1. Installed a new HA on a Raspi3B (connected via LAN)
  2. Installed EVCC
  3. adapted the evcc.yaml as shown ...

Configuration details

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: homeassistant.local
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 30s # control cycle interval

# database configuration for persisting charge sessions and settings
# database:
#   type: sqlite
#   dsn: <path-to-db-file>

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

# telemetry enables aggregated statistics
#
# Telemetry allows collecting usage data (grid and green energy, charge power).
# Data is aggregated, no individual charging sessions are tracked. The collected,
# anonymous data can be retrieved using https://api.evcc.io.
#
# See https://github.com/evcc-io/evcc/pull/4343 or details.
#
# For time being, this is only available to sponsors, hence data is associated with
# the sponsor token's identity.
#
# telemetry: true

# 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: solar-edge: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: CosmoGrid
    type: template
    template: solax
    usage: grid

    # RS485 via TCP/IP (Modbus RTU)
    modbus: rs485tcpip
    id: 1
    host: 192.168.178.45 # Hostname
    port: 502 # Port

  - name: CosmoPV
    type: template
    template: solax
    usage: pv

    # RS485 via TCP/IP (Modbus RTU)
    modbus: rs485tcpip
    id: 1
    host: 192.168.178.45 # Hostname
    port: 502 # Port

  - name: CosmoBattery
    type: template
    template: solax
    usage: battery

    # RS485 via TCP/IP (Modbus RTU)
    modbus: rs485tcpip
    id: 1
    host: 192.168.178.45 # Hostname
    port: 502 # Port

# 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: CosmoCharger
    type: template
    template: innogy-ebox

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.200 # Hostname
    port: 502 # Port 

# 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: BMW
    type: template
    template: bmw
    title: # Wird in der Benutzeroberfläche angezeigt (Optional)
    user: # undisclosed # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: # undisclosed # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    vin: # undisclosed #WBMW... # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (Optional)
    capacity: 13 # Akkukapazität in kWh (Optional) 

# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
    grid: CosmoGrid
    pv: CosmoPV # list of pv inverters/ meters
    battery: CosmoBattery # list of battery meters

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Carport # display name for UI
    charger: CosmoCharger # charger
    meter: # CosmoPV # charge meter
    mode: "off" # set default charge mode, use "off" to disable by default if charger is publicly available
    # vehicle: car1 # set default vehicle (disables vehicle detection)
    resetOnDisconnect: true # set defaults when vehicle disconnects
    phases: 3 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    minCurrent: 6 # minimum charge current (default 6A)
    maxCurrent: 16 # maximum charge current (default 16A)

    # remaining settings are experts-only and best left at default values
    priority: 0 # 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: charging
        # poll interval defines how often the vehicle API may be polled if NOT charging
        interval: 60m
      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)

# tariffs are the fixed or variable tariffs
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type: fixed
    price: 0.34 # EUR/kWh
    zones:
      - days: Mo-Fr
        hours: 2-5
        price: 0.2 # EUR/kWh
      - days: Sa,So
        price: 0.15 # EUR/kWh

    # or variable tariffs
    # type: tibber
    # token: "476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4" # access token
    # homeid: "cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c" # optional if multiple homes associated to account

    # type: awattar
    # region: de # optional, choose at for Austria
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional

    # type: elering # Nordpool
    # region: ee # or lt, lv, fi
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: energinet # Energinet using the price in DKK
    # region: dk1 # or dk2
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)
  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.082 # EUR/kWh

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional
  co2:
    # co2 tariff provides co2 intensity forecast and is for co2-optimized target charging if no variable grid tariff is specified
    # type: grünstromindex # GrünStromIndex (Germany only)
    # zip: <zip>

    # type: electricitymaps # https://app.electricitymaps.com/map
    # uri: <uri>
    # token: <token>
    # zone: DE

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

# eebus credentials
eebus:
  # uri: # :4712
  # interfaces: # limit eebus to specific network interfaces
  # - en0
  # certificate: # local signed certificate, required, can be generated via `evcc eebus-cert`
  #   public: # public key
  #   private: # private key

# 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:
  # - 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>
  # - type: ntfy
  #   uri: https://<host>/<topics>
  #   priority: <priority>
  #   tags: <tags>

Log details

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2023/08/04 21:39:43 evcc 0.118.11
[main  ] INFO 2023/08/04 21:39:43 using config file: /config/evcc.yaml
[main  ] INFO 2023/08/04 21:39:43 starting ui and api at :7070
[site  ] WARN 2023/08/04 21:40:03 battery configured but residualPower is missing (add residualPower: 100 to site)
[site  ] INFO 2023/08/04 21:40:03 site config:
[site  ] INFO 2023/08/04 21:40:03   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2023/08/04 21:40:03     grid:      power ✓ energy ✓ currents ✗
[site  ] INFO 2023/08/04 21:40:03     pv 1:      power ✓ energy ✓ currents ✗
[site  ] INFO 2023/08/04 21:40:03     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✗
[site  ] INFO 2023/08/04 21:40:03   vehicles:
[site  ] INFO 2023/08/04 21:40:04     vehicle 1: range ✓ finish ✗ status ✓ climate ✗ wakeup ✗
[lp-1  ] INFO 2023/08/04 21:40:04 loadpoint 1:
[lp-1  ] INFO 2023/08/04 21:40:04   mode:        off
[lp-1  ] INFO 2023/08/04 21:40:04   charger:     power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-1  ] INFO 2023/08/04 21:40:04   meters:      charge ✓
[lp-1  ] INFO 2023/08/04 21:40:04     charge:    power ✓ energy ✗ currents ✓
[lp-1  ] DEBUG 2023/08/04 21:40:04 phase timer inactive
[lp-1  ] DEBUG 2023/08/04 21:40:04 pv timer inactive
[lp-1  ] DEBUG 2023/08/04 21:40:04 guard timer inactive
[lp-1  ] DEBUG 2023/08/04 21:40:04 max charge current: 6A
[site  ] DEBUG 2023/08/04 21:40:05 ----
[lp-1  ] DEBUG 2023/08/04 21:40:05 charge power: 0W
[site  ] ERROR 2023/08/04 21:40:30 pv 1 power: add[0]: read failed: modbus: response slave id '0' does not match request '1'
[site  ] DEBUG 2023/08/04 21:40:30 pv power: 0W
[site  ] ERROR 2023/08/04 21:40:50 battery 1 power: read failed: modbus: response slave id '0' does not match request '1'
[site  ] ERROR 2023/08/04 21:41:00 battery 1 soc: read failed: read tcp 192.168.178.46:50632->192.168.178.45:502: i/o timeout
[site  ] DEBUG 2023/08/04 21:41:00 battery soc: 0%
[site  ] DEBUG 2023/08/04 21:41:00 battery power: 0W
[site  ] ERROR 2023/08/04 21:41:04 grid meter: read failed: modbus: response slave id '0' does not match request '1'
[site  ] ERROR 2023/08/04 21:41:04 grid meter: read failed: modbus: response slave id '0' does not match request '1'
[site  ] DEBUG 2023/08/04 21:41:04 ----
[lp-1  ] DEBUG 2023/08/04 21:41:04 charge power: 0W
[site  ] ERROR 2023/08/04 21:41:09 pv 1 power: add[0]: read failed: modbus: response slave id '0' does not match request '1'
[site  ] DEBUG 2023/08/04 21:41:09 pv power: 0W
[site  ] ERROR 2023/08/04 21:41:21 battery 1 power: read failed: modbus: response slave id '0' does not match request '1'
[site  ] ERROR 2023/08/04 21:41:28 battery 1 soc: read failed: modbus: response slave id '0' does not match request '1'
[site  ] DEBUG 2023/08/04 21:41:28 battery soc: 0%
[site  ] DEBUG 2023/08/04 21:41:28 battery power: 0W

What type of operating system are you running?

Linux

Version

No response

manny4566 commented 1 year ago

Hi,

i think there is a problem between evcc and the BMW Api. In my evcc the car is displayed as offline.

But evcc -l debug vehicle shows something:

Soc: 30% Capacity: 42.2kWh Charge status: C Range: 73km Odometer: 15673km Features: []

But then is my question, why is the car displayed in the gui as offline ?