Vehicles offline due to API changes?

hyperbart commented 10 months ago

Describe the bug

All vehicles (bmw and polestar) configured in GUI are marked offline.

Steps to reproduce

Configure bmw or polestar in GUI, validate, error exclamation mark shows up with notification about EVCC API problem code 400 for vehicle 1, when trying with other vehicle same but number 2.

Configuration details

bart@nas:~$ cat /EVO500/AppsConfig/EVCC/evcc.yml
interval: 5s

site:
- title: xxxxx
  meters:
    grid: HuisMeter
    pv:
    - pvHuis
    - pvTuinHuis
  residualpower: 10

messaging:
  events:
    connect:
      title: Wagen aangesloten
      msg: |
        Connect
        Voertuig aangesloten op de {{.title}}-lader.
        Wagen voorlopig onbekend
    disconnect:
      title: Wagen ontkoppeld
      msg: |
        Disconnect
        Er is {{round (divf .chargedEnergy 1000) 2 }} kWh geleverd op {{.chargeDuration}}.
        Voertuig {{.vehicleTitle}} was {{round (divf .connectedDuration) 8 }} aangesloten op de laadpaal
        Je kan {{.vehicleRange}} km rijden!
    start:
      title: Wagen gestart
      msg: |
        Start
        {{.vehicleTitle}} is gestart met laden op de {{.title}}-lader
        Het huidige rijbereik van {{.vehicleTitle}} is {{.vehicleRange}}km

    stop:
      title: Wagen gestopt
      msg: |
        Stop
        Voertuig {{.vehicleTitle}} is gestopt op de {{.title}}-lader
        Er is {{round (divf .chargedEnergy 1000) 2 }} kWh geleverd op {{.chargeDuration}}.

  services:
    - type: telegram
      token: xxx:xxx
      chats:
        - -xxxxx

tariffs:
  currency: EUR # (default EUR)
  grid:
    # static grid price
    type: fixed
    price: 0.52 # [currency]/kWh

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.12 # [currency]/kWh
  co2:
    type: electricitymaps
    uri: https://api.co2signal.com/
    token: xxxxx
    zone: BE

meters:
  - name: HuisMeter
    type: modbus
    model: sdm # specific non-sunspec meter
    id: 1
    energy: Sum # only required for charge meter usage
    #via TCP:
    uri: 192.168.4.184:8899
    rtu: false # serial modbus rtu (rs485) device connected using simple ethernet adapter

  - name: pvHuis
    type: sma
    uri: 192.168.4.230
    password: xx
  - name: pvTuinHuis
    type: sma
    uri: 192.168.4.231
    password: xxxx

sponsortoken: x.x.z-x

log: debug
levels:
    core: debug
    cc-main: debug

influx:
  url: http://192.168.4.250:8086
  database: EVCC
  token: "xxxx=="
  org: "xxx"

chargers:
- name: ChargingPointAlfen
  type: alfen
  uri: 192.168.4.178 # TCP ModBus address
- name: wallbox1
  type: template
  template: pulsarplus
  timeout: 5m

loadpoints:
- title: Voortuin # display name for UI
  charger: ChargingPointAlfen # Wallbox Referenz
  mode: minpv # charge mode (off, now, minpv, pv)
  phases: 0
  mincurrent: 6
  maxcurrent: 16
  guardduration: 2m
  enable:
    threshold: 0
    delay: 1m
  disable:
    threshold: 0 # maximum import power (W)
    delay: 3m
- title: Oprit
  charger: wallbox1
  mode: pv
  phases: 1
  mincurrent: 6
  maxcurrent: 20

vehicles:

Log details

Later

What type of operating system are you running?

Linux

Version

No response

fuxae commented 10 months ago

Also mein BMW wird ohne Probleme erkannt. An der allgemeinen BMW API dürfte es daher also nicht liegen.

VolkerK62 commented 10 months ago

Just to make sure, you configured the cars not within the yaml-file but by using the GUI configuration? Might be a bug, because this is still highly experimental.

andig commented 10 months ago

Missing config

hyperbart commented 10 months ago

Just to make sure, you configured the cars not within the yaml-file but by using the GUI configuration? Might be a bug, because this is still highly experimental.

Correct. And indeed, I saw another thread with @andig about API changes and I think one is related to the other.

hyperbart commented 10 months ago