Fahrzeugstatus ERROR - MG4

[lmfgpeace]

Describe the bug

Fahrzeugstatus kann beim MG4 nicht mehr abgerufen werden. Error siehe Log.

Steps to reproduce

1. update from 0.13x.xx to v0.131.2
2. now you have the problem :)
   ...

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

interval: 5s # 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: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJldmNjLmlvIiwic3ViIjoidHJpYWwiLCJleHAiOjE3MjkyNzQ0MDAsImlhdCI6MTcyODQ5NjgwMCwic3BlIjp0cnVlLCJzcmMiOiJtYSJ9.gnfLjIPCnFt3TmCUhoXCmA3nHK5RkQcOrLIejCQfc4w
# trial token, valid until 2024-10-18
sponsortoken: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJldmNjLmlvIiwic3ViIjoidHJpYWwiLCJleHAiOjE3Mjk4NjQ4MDAsImlhdCI6MTcyOTA4NzIwMCwic3BlIjp0cnVlLCJzcmMiOiJtYSJ9.3iF50HEbpf7hF7nob075jJxseDt4c2rFeSS-ZHpxzuE

# 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:
  #    # 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: Sungrow_SH10.0RT_grid
    type: template
    template: sungrow-hybrid
    usage: grid

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.105 # Hostname
    port: 502 # Port
    timeout: 5s # optional
  - name: Sungrow_SH10.0RT_pv
    type: template
    template: sungrow-hybrid
    usage: pv

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.105 # Hostname
    port: 502 # Port
    timeout: 5s # optional
  - name: Sungrow_SH10.0RT_battery
    type: template
    template: sungrow-hybrid
    usage: battery

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.105 # Hostname
    port: 502 # Port
    timeout: 5s # optional
  - name: go-e_controller_grid
    type: template
    template: go-e-controller
    usage: grid
    host: 192.168.178.170 # IP-Adresse oder Hostname
  - name: go-e-controller_pv
    type: template
    template: go-e-controller
    usage: pv
    host: 192.168.178.170 # IP-Adresse oder Hostname
# 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: goe-e_charger
    type: template
    template: go-e-v3
    host: 192.168.178.195 # 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: MG-4-Luxury
    type: template
    template: mg
    title: MG 4 Luxury # Wird in der Benutzeroberfläche angezeigt (optional)
    user: xx@xx.de # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: xxxx # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    vin: xxxx # Erforderlich
    capacity: 64 # Akkukapazität in kWh (optional)
# site describes the EVU connection, PV and home battery
site:
  title: My Home # display name for UI
  meters:
    grid: Sungrow_SH10.0RT_grid # grid meter
    pv:
      - Sungrow_SH10.0RT_pv # list of pv inverters/ meters
    battery:
      - Sungrow_SH10.0RT_battery # list of battery meters
    aux: # list of auxiliary meters for adjusting grid operating point
  residualPower: 100 # additional household usage margin

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Garage # display name for UI
    charger: goe-e_charger # charger
    meter:  # external charge meter (if charger has no meter included). NOT grid or pv meter.
    mode: pv # 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: -100 # 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: 200 # maximum import power (W)
    phases: 0
# tariffs are the fixed or variable tariffs
tariffs:
  currency: EUR # (default EUR)
  grid:
    # static grid price
    type: fixed
    price: 0.2926 # [currency]/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.0811 # [currency]/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 details

[main ] ERROR 2024/10/27 17:20:47 vehicle status: Get "https://gateway-mg-eu.soimt.com/api.app/v1/vehicle/charging/mgmtData?vin=d95ee66d4a7b24d57c9fa15b6540f0d736acb349ecaab527145943bf18243076": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

[lp-1 ] ERROR 2024/10/27 17:28:07 vehicle soc: Get "https://gateway-mg-eu.soimt.com/api.app/v1/vehicle/charging/mgmtData?vin=d95ee66d4a7b24d57c9fa15b6540f0d736acb349ecaab527145943bf18243076": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

[lp-1 ] ERROR 2024/10/27 17:21:02 vehicle odometer: Get "https://gateway-mg-eu.soimt.com/api.app/v1/vehicle/charging/mgmtData?vin=d95ee66d4a7b24d57c9fa15b6540f0d736acb349ecaab527145943bf18243076": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
[lp-1 ] ERROR 2024/10/27 17:21:02 vehicle soc: Get "https://gateway-mg-eu.soimt.com/api.app/v1/vehicle/charging/mgmtData?vin=d95ee66d4a7b24d57c9fa15b6540f0d736acb349ecaab527145943bf18243076": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

What type of operating system are you running?

Docker container

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

0.131.2

[lmfgpeace]

[CarG70]

Ich kann Dir zwar nicht helfen aber Du hast oben gerade Deine Zugangsdaten zu MG verbrannt. Ändere die mal schnell...

[lmfgpeace]

Ich kann Dir zwar nicht helfen aber Du hast oben gerade Deine Zugangsdaten zu MG verbrannt. Ändere die mal schnell...

ja geil überhaupt nicht nachgedacht wie dumm - danke!

[d3ni3]

Sicher das es kein Netzwerk- / Verfügbarkeitsproblem ist?
Die SAIC-Server sind nicht gerade für ihre Zuverlässigkeit bekannt. Wenn ich heute Abend wieder zu Hause bin, schaue ich mal wie das bei mir aussieht.

[lmfgpeace]

Sicher das es kein Netzwerk- / Verfügbarkeitsproblem ist?

Die SAIC-Server sind nicht gerade für ihre Zuverlässigkeit bekannt. Wenn ich heute Abend wieder zu Hause bin, schaue ich mal wie das bei mir aussieht.

Ziemlich sicher. Unmittelbar vor dem Update war alles schick.

[d3ni3]

Okay, dann müsste ich das ja nachstellen können.

[d3ni3]

Habe den MG soeben angeschlossen, bei mir funktioniert der Abruf.
Installiert habe ich die v0.131.3.

[lmfgpeace]

Habe den MG soeben angeschlossen, bei mir funktioniert der Abruf.

Installiert habe ich die v0.131.3.

Ich teste das morgen nochmal mit v0.131.2 und mach dann Update auf v0.131.3.

Letzte Ladevorgang war bei mir am Sonntag vor Issue Erstellung.

[lmfgpeace]

Habe den MG soeben angeschlossen, bei mir funktioniert der Abruf. Installiert habe ich die v0.131.3.

@d3ni3
Funktioniert bei dir die Übermittlung des vehicleSoC beim Laden des MG auch nur so sporadisch? Mal wird der vehicleSoC direkt angezeigt, mal gar nicht.

Das nervt irgendwie ein bisschen.

Haste schonmal hier dran rumgespielt?:

cache: # Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)

oder
poll: # Definiert, wie die Fahrzeug APIs benutzt werden um aktuelle Informationen des Fahrzeugs abzurufen.

[d3ni3]

Ich achte da nicht immer so genau drauf. Gestern, beim Laden, wurde mir der SoC angezeigt. In der Konfigurationssicht werden aber irgendwie immer seltsame Werte angezeigt, auf dem Dashboard passt es dann aber. Was ich aber sagen kann ist, das der Webservice von SAIC öfter mal nicht erreichbar ist oder einfach keine Werte liefert. Die App zeigt dann auch keine Werte an. Dem MG-Forum nach kommt das relativ häufig vor.

Jetzt gerade habe ich mal auf Schnellladen gestellt und bekomme keinen SoC... im Log steht dazu:

[mg ] TRACE 2024/11/18 06:15:29 GET https://gateway-mg-eu.soimt.com/api.app/v1/vehicle/charging/mgmtData?vin=***
[mg ] DEBUG 2024/11/18 06:15:39 Getting event id failed
[lp-1 ] ERROR 2024/11/18 06:15:39 vehicle soc: Get "https://gateway-mg-eu.soimt.com/api.app/v1/vehicle/charging/mgmtData?vin=***": context deadline exceeded

Ich kenne mich mit Go nicht aus, sieht aber nach einer Art "Timeout" aus...