Failed to contact car using Tesla API #817
-
|
Hoping to get some help. I noticed that I'm getting very sporadic uploads to network share. I was able to quickly determine the root cause was the Pi losing power from the Tesla. I can open my Tesla app and then the upload process would resume, confirming my suspicions. Looking at the archive log, I can see that TeslaUSB is attempting to hit the Tesla API, but seemingly is failing to connect, resulting in repeated unsuccessful retry attempts (see log below). I have TeslaUSB configured with my refresh token. I only have one car on my Tesla account, but since it wasn't working, I attempted to also include TESLA_NAME and TESLA_VIN. Unfortunately, that made no difference. Any ideas of what might be happening or potential fixes? Relevant TelsaUSB Config: Hardware Archive Server: Windows 10 w/network file share Archive Log (Most recent snippet) ============================================== |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
This should work again, though unclear how long it can remain working before Tesla shuts down the old API. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply! I got around to trying this. I followed the steps you took, but when I rean the /root/bin/tesla_api.py list_vehicles command, I received the following error response: Tue 20 Feb 12:15:07 MDT 2024: { I tried other available API commands via tesla_api.py and was met with the same error response for all the ones I tried.
Based on some of your previous comments to others, I know you don't use the awake function in TeslaUSB much, so I really appreciate any guidance or support on this - as well as your overall efforts on the project. |
Beta Was this translation helpful? Give feedback.
-
|
That sounds like you didn't upgrade to the latest TeslaUSB first. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, I came to that conclusion as well after doing some digging. I have a question, disclaimer: probably a 'noob' question...part of the reason I didn't initially update was because when I looked at "releases", I saw the last release was "teslausb-20211106.2" from October 2023...but when I look at individual commits and updated files, it's clear things are being updated/changed. I'm trying to understand if/when my TeslaUSB would pull updated files down. For example, I noticed support for Optional Lightshow Drive was added to the teslausb_setup_varibles.conf file. (https://github.com/marcone/teslausb/blob/main-dev/pi-gen-sources/00-teslausb-tweaks/files/teslausb_setup_variables.conf.sample). I checked my TeslaUSB, both the /root/teslausb_setup_variables_conf and /home/pi/teslausb_setup_variables.conf.sample. Neither file seems to have the updated lightshow configuration, yet I just ran the update today. Just trying to get a better understanding of how this works. I'd like to take advantage of the lightshow and other features as they become available. Once again, many thanks for your efforts. |
Beta Was this translation helpful? Give feedback.
-
|
Those releases are for the prebuilt Raspberry Pi OS image that TeslaUSB gets installed on top of. You don't necessarily need to even use that image, and in fact in some cases you can't, like when you're not using a Raspberry Pi. |
Beta Was this translation helpful? Give feedback.
-
|
Makes sense. My other question was related to the updated teslausb_setup_variables.conf file. I can see the file was updated, on Github, but I'm not seeing the updated on my device. I would like to use the added lightshow drive. What would I need to do to take advantage of that and why would it not be updated on my device? |
Beta Was this translation helpful? Give feedback.
-
|
That file isn't updated on the device because that would overwrite the changes you made. |
Beta Was this translation helpful? Give feedback.
That sounds like you didn't upgrade to the latest TeslaUSB first.