Timeout error - Tesla API

[silencer2008]

Describe the bug

When plugging in and Charge mode set to off...
EVCC starts charging the car before sending stop signal. Receive error below in between the stop signal

[lp-1 ] ERROR 2024/12/08 21:16:34 vehicle odometer: Get "https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/LRWYHCFS1PC764855/vehicle_data": dial tcp: lookup fleet-api.prd.na.vn.cloud.tesla.com: i/o timeout
[lp-1 ] ERROR 2024/12/08 21:17:03 vehicle soc: Get "https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/LRWYHCFS1PC764855/vehicle_data": dial tcp: lookup fleet-api.prd.na.vn.cloud.tesla.com: i/o timeout

Steps to reproduce

1.Plug in car while in Charge Off mode
2. TW3 starts charging...receives stop command and in between errors above
3.
...

Configuration details

# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: debug
levels:
  cache: error

# unique installation id
plant: 1222afe4743c8a5ea79e421d7aa45aacff422162b068107022ebcc2300885365

interval: 30s # control cycle interval

sponsortoken: XXX

# sponsors can set telemetry: true to enable anonymous data aggregation
# see https://github.com/evcc-io/evcc/discussions/4554
telemetry: false

meters:
- type: template
  template: huawei-dongle-powersensor 
  id: 1  
  host: 192.168.4.62  
  port: 502  
  usage: grid  
  modbus: tcpip  
  timeout: 15s  
  name: grid1
- type: template
  template: huawei-dongle-powersensor 
  id: 1  
  host: 192.168.4.62  
  port: 502  
  usage: pv  
  modbus: tcpip  
  timeout: 15s  
  name: pv2
- type: template
  template: huawei-dongle-powersensor 
  id: 1  
  host: 192.168.4.62  
  port: 502  
  usage: battery  
  modbus: tcpip  
  timeout: 15s  
  name: battery3
- type: template
  template: huawei-dongle-powersensor 
  id: 2  
  host: 192.168.4.62  
  port: 502  
  usage: pv  
  modbus: tcpip  
  timeout: 15s  
  name: pv4

chargers:
- type: template
  template: twc3 
  host: 192.168.4.64  
  name: wallbox6

vehicles:
- type: template
  template: tesla 
  title: Blue Beetle
  commandProxy: http://192.168.4.150:8080  
  accessToken: XX
  refreshToken: XX
  vin: XX
  capacity: 60  
  name: ev5
  control: true

loadpoints:
- title: Genoa Home
  charger: wallbox6
  vehicle: ev5
  mode: pv
  enable: # pv mode enable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: -1200 # maximum import power (W)
  disable: # pv mode disable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: 1400 # maximum import power (W)

site:
  title: Genoa Home
  meters:
    grid: grid1
    pv:
    - pv2
    - pv4
    battery:
    - battery3
  residualPower: 200
tariffs:
  currency: AUD # (default EUR)
  grid:
    # static grid price with price zones)
    type: fixed
    price: 0.294 # EUR/kWh
    zones:
      - days: Mo-So
        hours: 9-15
        price: 0.08 # AUD/kWh
      - days: Mo-So
        hours: 15-23 
        price: 0.54 # AUD/kWh
      - days: Mo-So
        hours: 00-9
        price: 0.22 # AUD/kWh

Log details

[tesla ] TRACE 2024/12/08 21:30:58 GET https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/users/region
[tesla ] TRACE 2024/12/08 21:30:59 {"response":{"region":"na","fleet_api_base_url":"https://fleet-api.prd.na.vn.cloud.tesla.com"}}
[tesla ] TRACE 2024/12/08 21:30:59 GET https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles
[tesla ] TRACE 2024/12/08 21:30:59 {"response":[{"id":3744434288795333,"vehicle_id":2252192521848260,"vin":"LRWYHCFS1PC764855","color":null,"access_type":"OWNER","display_name":null,"option_codes":null,"granular_access":{"hide_private":false},"tokens":null,"state":"online","in_service":false,"id_s":"3744434288795333","calendar_enabled":true,"api_version":82,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false}],"pagination":{"previous":null,"next":null,"current":1,"per_page":1,"count":1,"pages":1},"count":1}
[lp-1  ] INFO 2024/12/08 21:30:59 loadpoint 1:
[lp-1  ] INFO 2024/12/08 21:30:59   mode:        pv
[lp-1  ] INFO 2024/12/08 21:30:59   charger:     power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-1  ] INFO 2024/12/08 21:30:59   meters:      charge ✓
[lp-1  ] INFO 2024/12/08 21:30:59     charge:    power ✓ energy ✗ currents ✓
[lp-1  ] DEBUG 2024/12/08 21:30:59 phase timer inactive
[lp-1  ] DEBUG 2024/12/08 21:30:59 pv timer inactive
[lp-1  ] INFO 2024/12/08 21:30:59 vehicle updated: unknown -> Blue Beetle
[lp-1  ] DEBUG 2024/12/08 21:30:59 charge power: 0W
[lp-1  ] DEBUG 2024/12/08 21:30:59 charge currents: [0.6 0.3 0.3]A
[tesla ] TRACE 2024/12/08 21:31:00 GET https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/LRWYHCFS1PC764855/vehicle_data
[tesla ] TRACE 2024/12/08 21:31:01 
[lp-1  ] DEBUG 2024/12/08 21:31:01 vehicle odometer: 35003km
[lp-1  ] DEBUG 2024/12/08 21:31:01 charge voltages: [3.2 7.4 0]V
[lp-1  ] DEBUG 2024/12/08 21:31:01 charger status: A
[lp-1  ] INFO 2024/12/08 21:31:01 car disconnected
[lp-1  ] DEBUG 2024/12/08 21:31:01 set battery boost: false
[lp-1  ] DEBUG 2024/12/08 21:31:01 set session soc limit: 0
[lp-1  ] DEBUG 2024/12/08 21:31:01 set session energy limit: 0
[lp-1  ] DEBUG 2024/12/08 21:31:29 set charge mode: off
[lp-1  ] DEBUG 2024/12/08 21:31:29 charge power: 0W
[lp-1  ] DEBUG 2024/12/08 21:31:29 charge currents: [0.6 0.3 0.3]A
[lp-1  ] DEBUG 2024/12/08 21:31:29 vehicle odometer: 35003km
[lp-1  ] DEBUG 2024/12/08 21:31:29 charge voltages: [3.2 7.4 0]V
[lp-1  ] DEBUG 2024/12/08 21:31:29 charger status: A
[lp-1  ] DEBUG 2024/12/08 21:31:31 charge power: 0W
[lp-1  ] DEBUG 2024/12/08 21:31:31 charge currents: [0.6 0.3 0.3]A
[lp-1  ] DEBUG 2024/12/08 21:31:31 charge voltages: [3.2 7.4 0]V
[lp-1  ] DEBUG 2024/12/08 21:31:31 charger status: A
[lp-1  ] DEBUG 2024/12/08 21:32:01 charge power: 1331W
[lp-1  ] DEBUG 2024/12/08 21:32:01 charge currents: [3.3 1.9 0.4]A
[lp-1  ] DEBUG 2024/12/08 21:32:01 charge voltages: [237 238 236]V
[lp-1  ] DEBUG 2024/12/08 21:32:01 detected connected phases: 3p
[lp-1  ] DEBUG 2024/12/08 21:32:01 charger status: C
[lp-1  ] INFO 2024/12/08 21:32:01 car connected
[lp-1  ] DEBUG 2024/12/08 21:32:01 pv timer elapse
[lp-1  ] DEBUG 2024/12/08 21:32:01 pv timer inactive
[lp-1  ] INFO 2024/12/08 21:32:01 start charging ->
[lp-1  ] DEBUG 2024/12/08 21:32:01 wake-up timer: stop
[lp-1  ] DEBUG 2024/12/08 21:32:01 vehicle status: A
[lp-1  ] DEBUG 2024/12/08 21:32:01 vehicle soc: 60%
[lp-1  ] DEBUG 2024/12/08 21:32:01 vehicle soc limit: 100%
[lp-1  ] DEBUG 2024/12/08 21:32:01 vehicle range: 242km
[lp-1  ] WARN 2024/12/08 21:32:01 charger out of sync: expected disabled, got enabled
[lp-1  ] DEBUG 2024/12/08 21:32:01 charger enable
[tesla ] TRACE 2024/12/08 21:32:01 POST http://192.168.4.150:8080/api/1/vehicles/LRWYHCFS1PC764855/command/charge_stop
[tesla ] TRACE 2024/12/08 21:32:01 {"response":{"result":true,"reason":"The command was successfully received and will be processed shortly.","vin":"LRWYHCFS1PC764855","command":"charge_stop"}}
[lp-1  ] DEBUG 2024/12/08 21:32:01 charger disable
[lp-1  ] DEBUG 2024/12/08 21:32:01 wake-up timer: stop
[lp-1  ] DEBUG 2024/12/08 21:32:31 charge power: 0W
[lp-1  ] DEBUG 2024/12/08 21:32:31 charge currents: [0.6 0.3 0.3]A
[lp-1  ] DEBUG 2024/12/08 21:32:31 vehicle odometer: 35003km
[lp-1  ] DEBUG 2024/12/08 21:32:31 charge voltages: [3.2 7.4 0]V
[lp-1  ] DEBUG 2024/12/08 21:32:31 charger status: B
[lp-1  ] INFO 2024/12/08 21:32:31 stop charging <-
[tesla ] TRACE 2024/12/08 21:32:31 GET https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/LRWYHCFS1PC764855/vehicle_data
[lp-1  ] WARN 2024/12/08 21:32:36 vehicle soc: Get "https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/LRWYHCFS1PC764855/vehicle_data": dial tcp: lookup fleet-api.prd.na.vn.cloud.tesla.com: i/o timeout (ignored by estimator)
[lp-1  ] DEBUG 2024/12/08 21:32:36 soc estimated: 60.00% (vehicle: 60.00%)
[lp-1  ] DEBUG 2024/12/08 21:32:36 vehicle soc: 60%
[lp-1  ] ERROR 2024/12/08 21:32:36 vehicle soc limit: Get "https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/LRWYHCFS1PC764855/vehicle_data": dial tcp: lookup fleet-api.prd.na.vn.cloud.tesla.com: i/o timeout
[lp-1  ] ERROR 2024/12/08 21:32:36 vehicle range: Get "https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/LRWYHCFS1PC764855/vehicle_data": dial tcp: lookup fleet-api.prd.na.vn.cloud.tesla.com: i/o timeout
[lp-1  ] DEBUG 2024/12/08 21:33:01 charge power: 0W
[lp-1  ] DEBUG 2024/12/08 21:33:01 charge currents: [0.6 0.3 0.3]A
[lp-1  ] DEBUG 2024/12/08 21:33:01 charge voltages: [3.2 7.4 0]V
[lp-1  ] DEBUG 2024/12/08 21:33:01 charger status: B
[lp-1  ] DEBUG 2024/12/08 21:33:31 charge power: 0W
[lp-1  ] DEBUG 2024/12/08 21:33:31 charge currents: [0.6 0.3 0.3]A
[lp-1  ] DEBUG 2024/12/08 21:33:31 charge voltages: [3.2 7.4 0]V
[lp-1  ] DEBUG 2024/12/08 21:33:31 charger status: B
[lp-1  ] DEBUG 2024/12/08 21:34:01 charge power: 0W

What type of operating system are you running?

Linux

Nightly build

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

Version

0.131.8 (2fb046d)

[GrimmiMeloni]

EVCC starts charging the car before sending stop signal.

That's not correct. What actually happens is that evcc detects the charge is unexpectedly happening and stops it then.

That's what this message indicates.

[lp-1 ] WARN 2024/12/08 21:32:01 charger out of sync: expected disabled, got enabled

[silencer2008]

That is because while troubleshooting i have set charge mode to off and plugged the charger in.

The area of concern would be the timeout errors in between.
ERROR 2024/12/08 21:32:36 vehicle soc limit: Get "https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/LRWYHCFS1PC764855/vehicle_data": dial tcp: lookup fleet-api.prd.na.vn.cloud.tesla.com: i/o timeout
[lp-1 ] ERROR 2024/12/08 21:32:36 vehicle range: Get "https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/LRWYHCFS1PC764855/vehicle_data": dial tcp: lookup fleet-api.prd.na.vn.cloud.tesla.com: i/o timeout

[GrimmiMeloni]

The area of concern would be the timeout errors in between.

That's network related. Specifically the DNS lookup for the aforementioned tesla servers fail. The likely culprit is your DNS resolver. If the problem persists, I would start checking outside evcc, doing some name resolution tests using dig or nslookup to isolate the root cause.