Switching to Fleet API causes constant "GetVehicles Error: A task was canceled." (2024 ModelY) - Maybe Firewall Issue

[1icengineer]

Tried this several times throughout the year, but I can't seem to switch teslalogger to Fleet API.
teslalogger working fine with old non-Fleet API.

However, when switching to fleet API, I am getting a constant loop like this:
20.12.2024 18:06:24 : #1[Car_1:18]: GetVehicles Error: One or more errors occurred. (A task was canceled.)
20.12.2024 18:06:24 : #1[Car_1:18]: GetVehicles Error: A task was canceled.

Credentials are entered correctly, Tesla logout/# procedure followed, key saved in tesla app...
but no way to get this up and running.

Now with the Jan 1st 2025 deadline approaching I might lose access to teslalogger, if Fleet API is not working for me.

**Vehicle:
2024 Model Y SR Grünheide (Manufactured 11/2023)

**teslalogger type:
Docker in google vm

logile attached in post below

[1icengineer]

logfile_teslalogger_ModelY_20241220.zip

[1icengineer]

fyi, my vehicle data only shows up correctly, when switching back to the old ModelS/X API, as the fleet API is not working for my car.
This is happening since appox 6months, earlier in H1/2024 fleet API was working for my car as well.

This is the logfile snippet from when I switched back from Fleet API to old API tonight, when the car is found again:

---

01.01.2025 21:45:53 : #1[Car_1:19]: GetVehicles Error: A task was canceled.

01.01.2025 21:46:34 : #1[Car_1:19]: GetVehicles Error: One or more errors occurred. (A task was canceled.)

01.01.2025 21:46:34 : #1[Car_1:19]: GetVehicles Error: A task was canceled.

01.01.2025 21:46:35 : TeslaAuth::GetLoginUrlForBrowser
01.01.2025 21:47:08 : SetPassword
01.01.2025 21:47:08 : Update Password ID:1
01.01.2025 21:47:08 : #1[Thread Pool Worker:87]: ExitCarThread: Credentials changed!
01.01.2025 21:47:08 : #1[Car_1:19]: GetVehicles Error: Thread was being aborted.

01.01.2025 21:47:08 : #1[Thread Pool Worker:87]: CheckUseTaskerToken
01.01.2025 21:47:08 : #1[Thread Pool Worker:87]: LastTaskerToken not found - Stop using fast TaskerToken request! Reply: never!
01.01.2025 21:47:38 : #1[Car_1:19]: *** Exit Loop !!!
01.01.2025 21:47:38 : #1[Car_1:106]: GetAvgConsumption: sumkm: 10137.5; avgkm: 153.6; kwh/100km: 19.5; avgsocdiff: 51.1; maxkm: 307.1
01.01.2025 21:47:38 : #1[Car_1:106]: Restore Token OK. Valid: 1/1/2025 9:47:08 PM
01.01.2025 21:47:38 : #1[Car_1:106]: TOKEN:
(...)
01.01.2025 21:47:38 : #1[Car_1:106]: FleetApiAddress: https://fleet-api.prd.eu.vn.cloud.tesla.com/
01.01.2025 21:47:39 : INFO: ParseVehicles: unknown key device_type value - System.String
01.01.2025 21:47:39 : #1[Car_1:106]: display_name: Silver Star
01.01.2025 21:47:39 : #1[Car_1:106]: vin: XP7YGCES1RBXXXXXX
01.01.2025 21:47:39 : #1[Car_1:106]: id: erased
01.01.2025 21:47:39 : #1[Car_1:106]: vehicle_id: erased
01.01.2025 21:47:39 : #1[Car_1:106]: Tasker Config:
Server Port: https://teslalogger.de/
Path: wakeup.php
Attribute: t=212f8c4d
01.01.2025 21:47:39 : #1[Car_1:106]: Economy from DB: 0.142 Wh/km - count: 3
01.01.2025 21:47:39 : #1[Car_1:106]: Streamingtoken:
01.01.2025 21:47:45 : Reverse geocoding by Nominatim1
01.01.2025 21:47:45 : #1[Car_1:106]: Country Code: de
01.01.2025 21:47:45 : #1[Car_1:106]: Voltage at 50% SOC:0V Date:12/10/2024 2:39:23 PM
01.01.2025 21:47:45 : #1[Car_1:106]: Car: Y SR (MIG BYD) - 0.142 Wh/km
01.01.2025 21:47:45 : #1[Car_1:106]: VIN decoder: Model Y 2024 AWD:False MIC:False battery:LFP motor:3/Y single MIG:True
01.01.2025 21:47:45 : #1[Car_1:106]: Vehicle Config: car_type:'modely' car_special_type:'base' trim_badging:'50'
01.01.2025 21:47:45 : #1[Car_1:106]: No meter config
01.01.2025 21:47:45 : #1[Car_1:106]: ScanMyTesla FastMode: False
01.01.2025 21:47:45 : #1[:109]: GetChargingHistoryV2Service initializing ...
01.01.2025 21:47:45 : #1[StreamAPIThread_1:108]: StartStream
01.01.2025 21:47:45 : #1[Car_1:106]: CloseDriveState EndDate: 2025-01-01 21:47:08
01.01.2025 21:47:45 : Reverse geocoding by GeocodeCache
01.01.2025 21:47:45 : #1[Thread Pool Worker:87]: GetChargingHistoryV2: NotFound CarState: Start (OK: 0 - Fail: 1)
01.01.2025 21:47:45 : #1[:109]: GetChargingHistoryV2Service -> UpdateChargingState:
teslalogger.chargingstate.id:206
siteLocationName:Wernberg-Köblitz, Germany
chargeStartDateTime:8/31/2024 7:45:47 AM
chargeStopDateTime:8/31/2024 8:24:56 AM
sessionId:349630310
cost_total:0
cost_currency:EUR
cost_per_kwh:0.4
cost_for_charging:NaN
cost_idle_fee_total:0
cost_kwh_meter_invoice:44.942
cost_freesuc_savings_total:17.9768
freesuc:True
01.01.2025 21:47:45 : #1[:109]: ChargingState <206> updated from GetChargingHistoryV2Service
01.01.2025 21:47:45 : #1[:109]: GetChargingHistoryV2Service -> UpdateChargingState:
teslalogger.chargingstate.id:207
siteLocationName:Schleiz, Germany
chargeStartDateTime:8/31/2024 9:55:48 AM
chargeStopDateTime:8/31/2024 10:20:49 AM
sessionId:349654425
cost_total:0
cost_currency:EUR
cost_per_kwh:0.41
cost_for_charging:NaN
cost_idle_fee_total:0
cost_kwh_meter_invoice:31
cost_freesuc_savings_total:12.71
freesuc:True
01.01.2025 21:47:45 : #1[:109]: ChargingState <207> updated from GetChargingHistoryV2Service
01.01.2025 21:47:46 : #1[:109]: GetChargingHistoryV2Service -> UpdateChargingState:
teslalogger.chargingstate.id:208
siteLocationName:Irxleben, Germany
chargeStartDateTime:9/1/2024 9:38:55 AM
chargeStopDateTime:9/1/2024 9:41:26 AM
sessionId:350126967
cost_total:0
cost_currency:EUR
cost_per_kwh:0.4
cost_for_charging:NaN
cost_idle_fee_total:0
cost_kwh_meter_invoice:1
cost_freesuc_savings_total:0.4
freesuc:True
01.01.2025 21:47:46 : #1[:109]: ChargingState <208> updated from GetChargingHistoryV2Service
01.01.2025 21:47:46 : #1[:109]: GetChargingHistoryV2Service -> UpdateChargingState:
teslalogger.chargingstate.id:210
siteLocationName:Winsen (Luhe), Germany
chargeStartDateTime:9/1/2024 12:46:10 PM
chargeStopDateTime:9/1/2024 1:17:53 PM
sessionId:350174636
cost_total:0
cost_currency:EUR
cost_per_kwh:0.4
cost_for_charging:NaN
cost_idle_fee_total:0
cost_kwh_meter_invoice:35
cost_freesuc_savings_total:14
freesuc:True
01.01.2025 21:47:46 : #1[:109]: ChargingState <210> updated from GetChargingHistoryV2Service
01.01.2025 21:47:46 : #1[:109]: GetChargingHistoryV2Service initialized

[bassmaster187]

Do you have a firewall, PiHole or a FritzBox using the Guest Account.
Most Issues with GetVehicle Error is a firewall problem.