Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 404 #62

Open
kierenblack opened this issue Apr 28, 2023 · 9 comments
Open

Error 404 #62

kierenblack opened this issue Apr 28, 2023 · 9 comments

Comments

@kierenblack
Copy link

As of this morning I am getting a 404 error. I have added a new refresh token but that hasn't fixed the problem.

@PhotonHebs
Copy link

I'm getting 404 for chargeState calls now for some reason. After playing around, I have noticed that vehicleData is working fine, so now I'm using that instead to get the data I need. chargeState has been working fine for months, not sure why it has stopped working now. I seem to be able to start/stop charge, lock/unlock just fine too. Did Tesla change the API? I tried refreshing the token, waiting for vehicle to repopulate, even tried it in an entirely new instance of node-red.... all the same, chargeState gives a 404 error and vehicleData works just fine.... strange.

@onokje
Copy link
Owner

onokje commented Apr 30, 2023

It's possible Tesla changed the API indeed. I haven't updated this project in a while, I'll probably have more time coming summer :)

@paede81
Copy link

paede81 commented May 1, 2023

Yes Tesla changed the API. See details and workaround here:
bogosj/tesla#98
and here:
bogosj/tesla@0d6e63e

@hitnrun30
Copy link

What can we do till then, is there an updated fork somewhere

@demod-au
Copy link

demod-au commented May 3, 2023

Most (all?) the data is still returned using the "vehicleData" command. I was using "chargeState" msg.payload.battery_level, but have switched to "vehicleData" msg.payload.charge_state.battery_level, for the same info.

@hitnrun30
Copy link

I use it for charge state and climate. At least I can get the info. But if I want to set something I'm sol

@PhotonHebs
Copy link

I use it for charge state and climate. At least I can get the info. But if I want to set something I'm sol

I can still set charging amps, climate control, locks and charging just fine. I did notice that if I sent too many requests to chargeState (getting the 404 response) then I couldn’t set post requests sometimes. Now that I have stopped using chargeState and use vehicleData instead, the other post requests work just fine.

@hitnrun30
Copy link

I use it for charge state and climate. At least I can get the info. But if I want to set something I'm sol

I can still set charging amps, climate control, locks and charging just fine. I did notice that if I sent too many requests to chargeState (getting the 404 response) then I couldn’t set post requests sometimes. Now that I have stopped using chargeState and use vehicleData instead, the other post requests work just fine.

I need to do 4 things, Stop Charging, Unlock Charge Port, Unlock Doors and set the scheduled departure, how do I do that if I only get vehicle data?

@Lineflyer
Copy link

Can someone update their recent experience with this "404" problem?

I just started using this node-red addon and getting data via vehicleData works just fine.
I do however sometimes (!) get 404 responses when using start Charge or stopCharge. If I try again it works sooner or later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants