Alexander Blach

I've installed the latest version of TWCManager and I'm now using it with tesla-http-proxy running on another server on the local network and the Fleet API successfully. It works for...

Yes, I also think that this would be the way to go. Do you currently have the Fleet API working with TWCManager and are not running into the rate limits...

This morning I was running a mix of an old version of TWCManager with the latest TeslaAPI.py. I did this because I made modifications to the source code in the...

I'll check how it behaves tomorrow when there is enough solar power. Maybe the issue was due to a mix of the old and new source code.

`stopAskingToStartCharging` is also set to `False` here: https://github.com/ngardiner/TWCManager/blob/b4d1536cfccf30f9b901cb2e471eebbe1f4ff594/lib/TWCManager/TWCSlave.py#L559 It looks like stopAskingToStartCharging is reset for all cars if at least one TWCSlave has `reportedAmpsActual` > 1.0. I do have two...

Ok, I just tested this: - I have two cars connected to two TWCs - One of the two cars has finished charging, the other has not yet reached the...

With those lines in TWCSlave.py commented out, I now get this in the log file: ``` Jun 11 13:21:43 TWCManager python3[28742]: 13:21:43 🚗 TeslaAPI 13 Don't charge NCC-1701-D because vehicle.stopAskingToStartCharging...

Yeah, I also think this has been broken for a long time, but it never really mattered because the legacy Tesla owner API didn't put any limits on the number...

Today I ran into another rate limit: One of the cars was not at home, so I think `car_api_charge` caused `update_location` and in turn `update_vehicle_data` in TeslaAPI.py to be called...

I just saw that there is a backoff mechanism that should be triggered when the API returns 429. Unfortunately, `update_vehicle_data` and `get_car_api` do not seem to look at `getCarApiRetryRemaining` etc....