Keine Daten Solax X3 Hybrid 15 G4 per Modbus über Raspberry mit Home Assistant

[Mike5229]

Hallo,

bei mir läuft Home Assistant OS auf einem Rasperry.
Darüber lese ich auch problemlos Daten per Modbus (RS485 Usb Stick) vom Solax aus.
Leider funktioniert aber das Auslesen der Daten im EVCC (Installiert per HACS) nicht.
Wahrscheinlich weil nur ein Gerät die Daten per Modbus auslesen kann.
Wie kann EVCC die bereits vorhanden Daten von Home-Assistant zur verfügung stellen?

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

interval: 30s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/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: eyJh...
# 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 # use `deny` to raise modbus errors

# 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: my_grid
    type: template
    template: solax
    usage: grid
  - name: my_pv
    type: template
    template: solax
    usage: pv
  - name: my_battery
    type: template
    template: solax
    usage: battery
    modbus: rs485serial
    id: 1
    device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
    baudrate: 19200 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
    comset: "8N1" # Kommunikationsparameter für den Adapter
# 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: my_charger
    type: template
    template: cfos
    host: 192.168.188.183 # IP-Adresse oder Hostname

# 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: opel
    type: template
    template: opel
    title: # Wird in der Benutzeroberfläche angezeigt (optional)
    user: xxx
    accessToken: 6...
    refreshToken: 7...
    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: my_grid # grid meter
    pv:
      - my_pv # list of pv inverters/ meters
    battery:
      - my_battery # list of battery meters
  residualPower: 100 # additional household usage margin
  maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Einfahrt # display name for UI
    charger: my_charger # charger
    meter: # external charge meter (if charger has no meter included). NOT grid or pv meter.x
    mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available

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

# 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.300 # 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%)

    # type: entsoe # Entso-E european market data
    # domain: BZN|DE-LU # https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas
    # securitytoken: # api token
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: pun # PUN - Prezzo unico nazionale - Hourly Italian wholesale prices
    # charges: 0 # optional, additional charges per kWh
    # tax: 0 # optional, additional tax (0.1 for 10%)

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: general

    # type: custom # price from a plugin source; see https://docs.evcc.io/docs/reference/plugins
    # price:
    #   source: http
    #   uri: https://example.org/price.json
    #   jq: .price.current

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.08 # EUR/kWh

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

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: feedIn
  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> # needs to be a token with forecast (not in the free tier)
    # zone: DE

    # type: ngeso # National Grid Electricity System Operator data (Great Britain only) https://carbonintensity.org.uk/
    # provides national data if both region and postcode are omitted - Choose ONE only!
    # region: 1 # optional, coarser than using a postcode - The region details are at https://carbon-intensity.github.io/api-definitions/#region-list
    # postcode: SW1 # optional - Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only

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

[main  ] INFO 2024/10/02 15:21:15 evcc 0.130.13
[main  ] INFO 2024/10/02 15:21:15 using config file: /config/evcc.yaml
[db    ] INFO 2024/10/02 15:21:15 using sqlite database: /data/evcc.db
[main  ] INFO 2024/10/02 15:21:16 listening at :7070
[main  ] ERROR 2024/10/02 15:21:16 creating vehicle opel failed: cannot create vehicle type 'template': cannot create vehicle type 'opel': missing credentials
[lp-1  ] DEBUG 2024/10/02 15:21:16 charge total import: 0.000kWh
[site  ] INFO 2024/10/02 15:21:16 site config:
[site  ] INFO 2024/10/02 15:21:16   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2024/10/02 15:21:16     grid:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/10/02 15:21:16     pv 1:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/10/02 15:21:16     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✗
[site  ] INFO 2024/10/02 15:21:16   vehicles:
[site  ] INFO 2024/10/02 15:21:16     vehicle 1: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[lp-1  ] INFO 2024/10/02 15:21:16 loadpoint 1:
[lp-1  ] INFO 2024/10/02 15:21:16   mode:        off
[lp-1  ] INFO 2024/10/02 15:21:16   charger:     power ✓ energy ✓ currents ✓ phases ✗ wakeup ✓
[lp-1  ] INFO 2024/10/02 15:21:16   meters:      charge ✓
[lp-1  ] INFO 2024/10/02 15:21:16     charge:    power ✓ energy ✓ currents ✓
[lp-1  ] DEBUG 2024/10/02 15:21:16 phase timer inactive
[lp-1  ] DEBUG 2024/10/02 15:21:16 pv timer inactive
[site  ] DEBUG 2024/10/02 15:21:16 ----
[lp-1  ] DEBUG 2024/10/02 15:21:16 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:21:16 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:21:18 pv 1 power: add[0]: read failed: invalid length received: 0
[site  ] DEBUG 2024/10/02 15:21:18 pv power: 0W
[site  ] ERROR 2024/10/02 15:21:21 battery 1 power: read failed: modbus: response crc '769' does not match expected '12473'
[site  ] DEBUG 2024/10/02 15:21:46 ----
[lp-1  ] DEBUG 2024/10/02 15:21:46 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:21:46 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:21:48 pv 1 power: add[0]: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:21:48 pv power: 0W
[site  ] ERROR 2024/10/02 15:21:51 battery 1 power: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:22:16 ----
[lp-1  ] DEBUG 2024/10/02 15:22:16 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:22:16 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:22:18 pv 1 power: add[0]: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:22:18 pv power: 0W
[site  ] ERROR 2024/10/02 15:22:21 battery 1 power: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:22:46 ----
[lp-1  ] DEBUG 2024/10/02 15:22:46 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:22:46 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:22:48 pv 1 power: add[0]: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:22:48 pv power: 0W
[site  ] ERROR 2024/10/02 15:22:51 battery 1 power: read failed: invalid length received: 0
[site  ] DEBUG 2024/10/02 15:23:16 ----
[lp-1  ] DEBUG 2024/10/02 15:23:16 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:23:16 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:23:18 pv 1 power: add[0]: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:23:18 pv power: 0W
[site  ] ERROR 2024/10/02 15:23:21 battery 1 power: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:23:46 ----
[lp-1  ] DEBUG 2024/10/02 15:23:46 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:23:46 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:23:48 pv 1 power: add[0]: read failed: modbus: response crc '0' does not match expected '67'
[site  ] DEBUG 2024/10/02 15:23:48 pv power: 0W
[site  ] ERROR 2024/10/02 15:23:51 battery 1 power: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:24:16 ----
[lp-1  ] DEBUG 2024/10/02 15:24:16 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:24:16 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:24:18 pv 1 power: add[0]: read failed: invalid length received: 0
[site  ] DEBUG 2024/10/02 15:24:18 pv power: 0W
[site  ] ERROR 2024/10/02 15:24:21 battery 1 power: read failed: modbus: response crc '0' does not match expected '67'
[site  ] DEBUG 2024/10/02 15:24:46 ----
[lp-1  ] DEBUG 2024/10/02 15:24:46 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:24:46 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:24:48 pv 1 power: add[0]: read failed: invalid length received: 0
[site  ] DEBUG 2024/10/02 15:24:48 pv power: 0W
[site  ] ERROR 2024/10/02 15:24:51 battery 1 power: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:25:16 ----
[lp-1  ] DEBUG 2024/10/02 15:25:16 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:25:16 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:25:18 pv 1 power: add[0]: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:25:18 pv power: 0W
[site  ] ERROR 2024/10/02 15:25:21 battery 1 power: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:25:46 ----
[lp-1  ] DEBUG 2024/10/02 15:25:46 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:25:46 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:25:48 pv 1 power: add[0]: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:25:48 pv power: 0W
[site  ] ERROR 2024/10/02 15:25:51 battery 1 power: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:26:16 ----
[lp-1  ] DEBUG 2024/10/02 15:26:16 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:26:16 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:26:18 pv 1 power: add[0]: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:26:18 pv power: 0W
[site  ] ERROR 2024/10/02 15:26:21 battery 1 power: read failed: invalid length received: 0
[site  ] DEBUG 2024/10/02 15:26:46 ----
[lp-1  ] DEBUG 2024/10/02 15:26:46 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:26:46 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:26:48 pv 1 power: add[0]: read failed: invalid length received: 0
[site  ] DEBUG 2024/10/02 15:26:48 pv power: 0W
[site  ] ERROR 2024/10/02 15:26:51 battery 1 power: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:27:16 ----
[lp-1  ] DEBUG 2024/10/02 15:27:16 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:27:16 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:27:18 pv 1 power: add[0]: read failed: invalid length received: 0
[site  ] DEBUG 2024/10/02 15:27:18 pv power: 0W
[site  ] ERROR 2024/10/02 15:27:21 battery 1 power: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:27:46 ----
[lp-1  ] DEBUG 2024/10/02 15:27:46 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:27:46 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:27:48 pv 1 power: add[0]: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:27:48 pv power: 0W
[site  ] ERROR 2024/10/02 15:27:51 battery 1 power: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:28:16 ----
[lp-1  ] DEBUG 2024/10/02 15:28:16 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:28:16 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:28:18 pv 1 power: add[0]: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:28:18 pv power: 0W
[site  ] ERROR 2024/10/02 15:28:21 battery 1 power: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:28:46 ----
[lp-1  ] DEBUG 2024/10/02 15:28:46 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:28:46 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:28:48 pv 1 power: add[0]: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:28:48 pv power: 0W
[site  ] ERROR 2024/10/02 15:28:51 battery 1 power: read failed: unexpected EOF
[lp-1  ] DEBUG 2024/10/02 15:28:53 set charge mode: minpv
[site  ] DEBUG 2024/10/02 15:28:53 ----
[lp-1  ] DEBUG 2024/10/02 15:28:53 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:28:53 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:28:54 pv 1 power: add[0]: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:28:54 pv power: 0W
[lp-1  ] DEBUG 2024/10/02 15:28:55 set charge mode: off
[site  ] ERROR 2024/10/02 15:28:57 battery 1 power: read failed: modbus: response crc '0' does not match expected '67'
[site  ] DEBUG 2024/10/02 15:28:57 ----
[lp-1  ] DEBUG 2024/10/02 15:28:57 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:28:57 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:29:00 pv 1 power: add[0]: read failed: unexpected EOF
[site  ] DEBUG 2024/10/02 15:29:00 pv power: 0W
[site  ] ERROR 2024/10/02 15:29:03 battery 1 power: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:29:16 ----
[lp-1  ] DEBUG 2024/10/02 15:29:16 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:29:16 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:29:18 pv 1 power: add[0]: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:29:18 pv power: 0W
[site  ] ERROR 2024/10/02 15:29:21 battery 1 power: read failed: resource temporarily unavailable
[site  ] DEBUG 2024/10/02 15:29:46 ----
[lp-1  ] DEBUG 2024/10/02 15:29:46 charge power: 0W
[lp-1  ] DEBUG 2024/10/02 15:29:46 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/02 15:29:48 pv 1 power: add[0]: read failed: invalid length received: 0
[site  ] DEBUG 2024/10/02 15:29:48 pv power: 0W
[site  ] ERROR 2024/10/02 15:29:51 battery 1 power: read failed: resource temporarily unavailable

Hat hier jemand eine Idee?

[andig]

Einfach custom meter konfigurieren oder Modbus Proxy nutzen (falls das Modbus ist)?

[Mike5229]

Modbus Proxy wäre natürlich super, aber geht glaube ich nicht, weil die ganzen Addons nur auf Modbux TCP aufbauen, ich aber die Daten per Seriell-RS485 auf den Raspberry bekomme. Ich wüsste nicht, wie ich das realisieren könnte.

Gibt es für dei custom meter eine eine Anleitung für Solax Wechselrichter?

[andig]

Die Addons kenne ich nicht. Evcc kann mit Beidem umgehen.

[SolarPower2024]

Wenn du eh schon alle Daten in HA hast, könntest du als Backup Lösung auch einfach alle benötigten Daten von HA an evcc per MQTT schicken.

[Mike5229]

@SolarPower2024 Gibt es dazu ein ausführliche Dokumentation, wie das mit Solax und MQTT funktioniert? Ich bin auf dem Gebiet EVCC wirklich absoluter Anfänger. Am einfachsten wäre es, wenn man die eh schon vorhandenen Entitäten von HA nutzen könnte, aber scheinbar geht das nicht.

[Mike5229]

Ich versuche nun die Daten per HA API auzulesen. Über Powershell per "Invoke-RestMethod -Method Get -Uri" funktioniert das auch einwandfrei. Aber im EVCC leider nicht.
Folgende Fehlermeldung steht im Log von EVCC:

[lp-1  ] DEBUG 2024/10/08 15:17:21 charge power: 0W
[lp-1  ] DEBUG 2024/10/08 15:17:21 charge currents: [0 0 0]A
[site  ] ERROR 2024/10/08 15:17:21 pv 1 power: unexpected status: 401 (Unauthorized)
[site  ] DEBUG 2024/10/08 15:17:21 pv power: 0W
[site  ] ERROR 2024/10/08 15:17:22 battery 1 power: unexpected status: 401 (Unauthorized)

Im EVCC.YAML steht folgendes in der Section meters:

meters:
  - name: grid
    type: custom
    power:
      source: http
      uri: http://192.168.188.201:8123/api/states/sensor.stromfluss
      method: GET
      headers:
        - Authorization: Bearer ey..............................................MD
      insecure: true
      jq: .state|tonumber
      timeout: 2s
      
  - name: pv
    type: custom
    power:
      source: http
      uri: http://192.168.188.201:8123/api/states/sensor.solax_pv_power_total
      method: GET
      headers:
        - Authorization: Bearer ey......................................................MD
      insecure: true
      jq: .state|tonumber
      timeout: 2s

  - name: battery
    type: custom
    power:
      source: http
      uri: http://192.168.188.201:8123/api/states/sensor.solax_battery_current_charge
      method: GET
      headers:
        - Authorization: Bearer ey...............................................................MD
      insecure: true
      jq: .state|tonumber * -1 # Negativwert erstellen
      timeout: 2s
    soc:
      source: http
      uri: http://192.168.188.201:8123/api/states/sensor.solax_battery_capacity
      method: GET
      headers:
        - Authorization: Bearer ey...................................................MD
      insecure: true
      jq: .state|tonumber
      timeout: 2s

Hat vielleicht noch jemand eine Idee warum die Auth nicht aktzeptiert wird?

[Mike5229]

Wenn es immer wieder die gleiche Frage gibt, könnte es sein, dass es dafür einen Bedarf gibt...
Immer mehr Leute verwenden HA und perspektivisch gesehen, werden auch immer mehr ein E-Auto besitzen und dann eine Kombination aus HA und EVCC verwenden wollen.

Es macht doch wenig Sinn, extra Hardware/Resourcen nur für EVCC zu verwenden, wenn im HA schon alles vorhanden ist.

In diesem speziellen Fall scheint es auch einfach nur so zu sein, dass die Auth für den Token nicht korrekt übergeben wird, denn mit allen anderen Abrufen (wie z.b. unter linux mit curl oder eben Powershell unter Windows) funktioniert es.
Somit könnte man mit einer Problemlösung hier, bestimmt viele Anfragen in Zukunft lösen.
Ich hätte auch kein Problem einen Workaround für das Ganze zu schreiben, dafür müsste es aber erst funktionieren...

[andig]

Hier gehts nicht um HA.

In diesem speziellen Fall scheint es auch einfach nur so zu sein, dass die Auth für den Token nicht korrekt übergeben wird,

Die Annahme würde das Log verifizieren. Deshalb die Frage. Das kann man jetzt endlos im Kreis diskutieren oder ins Logfile schauen. Danke!

[Mike5229]

@andig

Ich habe das Ganze jetzt nochmal extra auf einen separaten Raspberry installiert.

Im Anhang die --log-headers Ausgabe und das Logfile

evcc-20241012-102350-debug.log

--log-headers evcc.txt

[andig]

Offensichtlich:

GET /api/states/sensor.solax_pv_power_total HTTP/1.1
Host: 192.168.188.201:8123
User-Agent: Go-http-client/1.1
Authorization: Bearer eyxxxxxxwIjoyMD
Accept-Encoding: gzip

HTTP/1.1 401 Unauthorized

Das Token wird übergeben, aber abgelehnt.

[Mike5229]

Es geht!!!

Das gibt es einfach nicht... der sch..ß Editor in welchem ich die EVCC.YAML bearbeitet habe hat den Token-Code wegen einem Zeilenumbruch aufgrund der Länge nicht vollständig kopiert bzw. eingefügt.
Unter Powershell hat es geklappt und deshalb habe ich dort auch eine Ausgabe bekommen.

Auf jeden Fall kann ich nun bestätigen, dass EVCC auch als HACS Integration auf Home-Assistant-OS läuft.
Als entschuldigung für den unnötigen Stress setze ich mich mal an eine ausführliche bebilderte Anleitung für dieses Setup.
Muss es nun nur noch bei mir erst vollständig konfigurieren...