Error when creating vehicle VW ID.4: invalid character 'd'

[bolisaf]

Describe the bug

worked for a while, but doesn't anymore for some reason.

Steps to reproduce

1. copy the template from here: https://docs.evcc.io/docs/devices/vehicles/#we-connect-id
2. doesn't matter what you fill in for the user, password and vin, error stays the same
3. fire up evcc -l debug vehicle ...

Configuration details

sponsortoken: xxxxxxxxxxxxx

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

interval: 10s # 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:

# 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: debug
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: grid
#    type: modbus
#    model: sdm # SDM630
#    uri: rs485.fritz.box:23
#    rtu: true # rs485 device connected using ethernet adapter
#    id: 2
#    power: Power # default value, optionally override
#    energy: Sum # default value, optionally override
- name: SMA
  type: template
  template: sma-inverter
  usage: pv
  host: 10.10.10.47 # IP-Adresse oder Hostname
  password: xxxxxxx # Passwort für Benutzergruppe Benutzer (Optional) 
#  - name: battery
#    type: ...
#  - name: charge
#    type: ...
#  - name: aux
#    type: ...
- name: slimmelezer
  type: custom
  power:
    source: calc
    add:
    - source: http
      uri: http://10.10.10.46/sensor/power_consumed
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: 1000
      timeout: 15s
      cache: 5s
    - source: http
      uri: http://10.10.10.46/sensor/power_produced
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: -1000
      timeout: 15s
      cache: 5s
  energy:
    source: calc
    add:
    - source: http
      uri: http://10.10.10.46/sensor/energy_produced_tariff_1
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: 1
      timeout: 15s
      cache: 5s
    - source: http
      uri: http://10.10.10.46/sensor/energy_produced_tariff_2
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: 1
      timeout: 15s
      cache: 5s
  currents:
  - source: http
    uri: http://10.10.10.46/sensor/current_phase_1
    method: GET
    headers:
    - content-type: application/json
    jq: .value
    scale: 1
    timeout: 15s
    cache: 5s
  - source: http
    uri: http://10.10.10.46/sensor/current_phase_2
    method: GET
    headers:
    - content-type: application/json
    jq: .value
    scale: 1
    timeout: 15s
    cache: 5s
  - source: http
    uri: http://10.10.10.46/sensor/current_phase_3
    method: GET
    headers:
    - content-type: application/json
    jq: .value
    scale: 1
    timeout: 15s
    cache: 5s

# 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: alfeneve
    type: template # Wallbe charger
    template: alfen
    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 10.10.10.48 # 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: GTX
    type: template
    template: id
    title: GTX # Wird in der Benutzeroberfläche angezeigt (Optional)
    user: fdszedddqs # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: fzefezdezdzed # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    vin: fzedezdezrfdezd # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (Optional)
    capacity: 50 # Akkukapazität in kWh (Optional) 

# site describes the EVU connection, PV and home battery
site:
  title: VA35 # display name for UI
  meters:
    grid: slimmelezer # grid meter
    pv:
      - SMA # list of pv inverters/ meters
#    battery:
#      - battery # list of battery meters
#    aux:
#      - aux # list of auxiliary meters for adjusting grid operating point
  residualPower: 0 # additional household usage margin
  prioritySoc: 0 # give home battery priority up to this soc (empty to disable)
  bufferSoc: 0 # continue charging on battery above soc (0 to disable)
  bufferStartSoc: 0 # start charging on battery above soc (0 to disable)
  maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value
  smartCostLimit: 0 # set cost limit for automatic charging in PV mode

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Oprit # display name for UI
    charger: alfeneve # charger
    mode: pv # 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: 0 # 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: 32 # 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.207 # 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: elering # Nordpool
    # region: ee # or lt, lv, fi
    # 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.1126 # EUR/kWh
  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://a0d7b954-influxdb:8086
  database: evcc
  user: evcc
  password: evcc

# 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

C:\Users\stere\Downloads\evcc_0.118.1_windows-amd64>evcc.exe -l debug vehicle
[main  ] INFO 2023/07/31 21:46:55 evcc 0.118.1
[main  ] INFO 2023/07/31 21:46:55 using config file: C:\Users\stere\Downloads\evcc_0.118.1_windows-amd64\evcc.yaml
[main  ] ERROR 2023/07/31 21:46:56 creating vehicle GTX failed: cannot create vehicle 'template': cannot create vehicle 'id': invalid character 'd' looking for beginning of object key string
.Soc:     vehicle not available: cannot create vehicle 'template': cannot create vehicle 'id': invalid character 'd' looking for beginning of object key string
Capacity: 50.0kWh
Features: [Offline]

What type of operating system are you running?

HomeAssistant Add-on

Version

0.118.11

[premultiply]

C:\Users\stere\Downloads\evcc_0.118.1_windows-amd64>evcc.exe -l debug vehicle [main ] INFO 2023/07/31 21:46:55 evcc 0.118.1

[bolisaf]

when testing with 0.118.11

C:\Users\stere\Downloads\evcc_0.118.11_windows-amd64>evcc.exe -l debug vehicle [main ] INFO 2023/07/31 22:40:52 evcc 0.118.11 [main ] INFO 2023/07/31 22:40:52 using config file: C:\Users\stere\Downloads\evcc_0.118.11_windows-amd64\evcc.yaml [main ] ERROR 2023/07/31 22:40:58 creating vehicle GTX failed: cannot create vehicle 'template': cannot create vehicle 'id': missing state .Soc: vehicle not available: cannot create vehicle 'template': cannot create vehicle 'id': missing state Capacity: 77.0kWh Features: [Offline]

[andig]

Terms&Conditions akzeptieren. Ich sehe lokal, dass Audi und ID3 funktionieren.

[bolisaf]

Terms&Conditions akzeptieren. Ich sehe lokal, dass Audi und ID3 funktionieren.

I’m sorry, what? Where do I accept which t&c?

thanks for your answer :)

[andig]

VW App and/or website.

[bolisaf]

this is the weirdest thing. I just logged into volkswagen.com, didn't get a prompt to accept t&c's or anything, didn't do anything on the driver portal and logged back out. now it's working again...

[bolisaf]

Hi, I'm having the same issue again, but now I'm not able to get it to work by logging into volkswagen.com or vwgroup.io. what else can I try apart from this to get it to work again?

[andig]

VW und Audi funktionieren soweit ich sehe.

[bolisaf]

Yesterday evening when i wrote this it wasnt working, im checking now and its fine again… this happens every few months. im sure its on the end of volkswagen and not evcc. Are you seeing the same or is it stable for you?Thanks!LOn 1 Jun 2024, at 09:03, andig @.***> wrote: VW und Audi funktionieren soweit ich sehe.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>