Support for Tesla Vehicle Command protocol

[RicharddeCrep]

Tesla is deprecating the REST API by the end of 2023, to be replaced by the Tesla Vehicle Command protocol.

Do you have any plans to move your support for Node Red, to this protocol?

Thanks

Rich

[github-actions]

Thank you for reporting this issue!

[mseminatore]

I will have to look into the details of the new protocol and get back to you. If I am able to support this I will.

…

On Sat, Nov 18, 2023 at 7:12 PM Richard de Crespigny < ***@***.***> wrote: Tesla is deprecating the REST API by the end of 2023, to be replaced by the Tesla Vehicle Command protocol. Do you have any plans to move your support for Node Red, to this protocol? Thanks Rich — Reply to this email directly, view it on GitHub <#353>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEANBOHOWRM2PHAX4NOGTB3YFF2JXAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYDANRXGYZDQNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[RicharddeCrep]

Thanks, Here is the page about the change. https://developer.tesla.com/docs/fleet-api#help-and-support I hope you can support it as your Node is perfect for my needs. Best wishes Rich From: Mark Seminatore ***@***.***> Sent: Sunday, November 19, 2023 6:18 PM To: mseminatore/TeslaJS ***@***.***> Cc: Richard De Crespigny ***@***.***>; Author ***@***.***> Subject: Re: [mseminatore/TeslaJS] Support for Tesla Vehicle Command protocol (Issue #353) I will have to look into the details of the new protocol and get back to you. If I am able to support this I will.

On Sat, Nov 18, 2023 at 7:12 PM Richard de Crespigny < ***@***.***<mailto:***@***.***>> wrote: Tesla is deprecating the REST API by the end of 2023, to be replaced by the Tesla Vehicle Command protocol. Do you have any plans to move your support for Node Red, to this protocol? Thanks Rich — Reply to this email directly, view it on GitHub <#353>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEANBOHOWRM2PHAX4NOGTB3YFF2JXAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYDANRXGYZDQNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***<mailto:***@***.***>>

— Reply to this email directly, view it on GitHub<#353 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APAORYLXK264QQ6BDLBCAXDYFGXEHAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXG43TCNJVGY>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[mseminatore]

Not able to access that page. I get an endless login cycle.Sent from my iPhone XOn Nov 18, 2023, at 11:38 PM, Richard de Crespigny ***@***.***> wrote: Thanks, Here is the page about the change. https://developer.tesla.com/docs/fleet-api#help-and-support I hope you can support it as your Node is perfect for my needs. Best wishes Rich From: Mark Seminatore ***@***.***> Sent: Sunday, November 19, 2023 6:18 PM To: mseminatore/TeslaJS ***@***.***> Cc: Richard De Crespigny ***@***.***>; Author ***@***.***> Subject: Re: [mseminatore/TeslaJS] Support for Tesla Vehicle Command protocol (Issue #353) I will have to look into the details of the new protocol and get back to you. If I am able to support this I will.

On Sat, Nov 18, 2023 at 7:12 PM Richard de Crespigny < ***@***.***<mailto:***@***.***>> wrote: Tesla is deprecating the REST API by the end of 2023, to be replaced by the Tesla Vehicle Command protocol. Do you have any plans to move your support for Node Red, to this protocol? Thanks Rich — Reply to this email directly, view it on GitHub <#353>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEANBOHOWRM2PHAX4NOGTB3YFF2JXAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYDANRXGYZDQNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***<mailto:***@***.***>>

— Reply to this email directly, view it on GitHub<#353 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APAORYLXK264QQ6BDLBCAXDYFGXEHAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXG43TCNJVGY>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[RicharddeCrep]

Here are some snippets Rich Announcements & API Changelog 2023-11-17: Rest API vehicle commands endpoint deprecation timeline [Action Required] Please migrate any command API integrations to the Tesla Vehicle Commands protocol using the SDK<https://github.com/teslamotors/vehicle-command>. Dates Change November 2023 Newly delivered vehicles* will only support the Tesla Vehicle Command protocol after this date Nov - Dec 2023 REST API support will be deprecated<https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning> on existing customer vehicles that have not used the REST API in the preceding 30 days January 2024 All vehicles* will require Tesla Vehicle Command protocol. The REST API will be fully deprecated *Fleet accounts are excluded from these changes until further notice When issuing a REST API command to a vehicle that requires the Tesla Vehicle Command protocol, Fleet API will return the following error: "Tesla Vehicle Command Protocol required, please refer to the documentation here: https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning (403)" From: Mark Seminatore ***@***.***> Sent: Monday, November 20, 2023 11:37 AM To: mseminatore/TeslaJS ***@***.***> Cc: Richard De Crespigny ***@***.***>; Author ***@***.***> Subject: Re: [mseminatore/TeslaJS] Support for Tesla Vehicle Command protocol (Issue #353) Not able to access that page. I get an endless login cycle.Sent from my iPhone XOn Nov 18, 2023, at 11:38 PM, Richard de Crespigny ***@***.***<mailto:***@***.***>> wrote: Thanks, Here is the page about the change. https://developer.tesla.com/docs/fleet-api#help-and-support I hope you can support it as your Node is perfect for my needs. Best wishes Rich From: Mark Seminatore ***@***.***<mailto:***@***.***>> Sent: Sunday, November 19, 2023 6:18 PM To: mseminatore/TeslaJS ***@***.***<mailto:***@***.***>> Cc: Richard De Crespigny ***@***.***<mailto:***@***.***>>; Author ***@***.***<mailto:***@***.***>> Subject: Re: [mseminatore/TeslaJS] Support for Tesla Vehicle Command protocol (Issue #353) I will have to look into the details of the new protocol and get back to you. If I am able to support this I will.

On Sat, Nov 18, 2023 at 7:12 PM Richard de Crespigny < ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>>> wrote: Tesla is deprecating the REST API by the end of 2023, to be replaced by the Tesla Vehicle Command protocol. Do you have any plans to move your support for Node Red, to this protocol? Thanks Rich — Reply to this email directly, view it on GitHub <#353>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEANBOHOWRM2PHAX4NOGTB3YFF2JXAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYDANRXGYZDQNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>>>

— Reply to this email directly, view it on GitHub<#353 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APAORYLXK264QQ6BDLBCAXDYFGXEHAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXG43TCNJVGY>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***<mailto:***@***.******@***.***>>> —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***<mailto:***@***.***>> — Reply to this email directly, view it on GitHub<#353 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APAORYJCHOSD3AGPSGKJQGTYFKQ4JAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJYGA2DCNBYGQ>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[RicharddeCrep]

Here is the Github info. Please let me know if you need more info. I am happy to test it on my Model Y. Good luck! Rich teslamotors/vehicle-command (github.com)<https://github.com/teslamotors/vehicle-command> From: Mark Seminatore ***@***.***> Sent: Monday, November 20, 2023 11:37 AM To: mseminatore/TeslaJS ***@***.***> Cc: Richard De Crespigny ***@***.***>; Author ***@***.***> Subject: Re: [mseminatore/TeslaJS] Support for Tesla Vehicle Command protocol (Issue #353) Not able to access that page. I get an endless login cycle.Sent from my iPhone XOn Nov 18, 2023, at 11:38 PM, Richard de Crespigny ***@***.***<mailto:***@***.***>> wrote: Thanks, Here is the page about the change. https://developer.tesla.com/docs/fleet-api#help-and-support I hope you can support it as your Node is perfect for my needs. Best wishes Rich From: Mark Seminatore ***@***.***<mailto:***@***.***>> Sent: Sunday, November 19, 2023 6:18 PM To: mseminatore/TeslaJS ***@***.***<mailto:***@***.***>> Cc: Richard De Crespigny ***@***.***<mailto:***@***.***>>; Author ***@***.***<mailto:***@***.***>> Subject: Re: [mseminatore/TeslaJS] Support for Tesla Vehicle Command protocol (Issue #353) I will have to look into the details of the new protocol and get back to you. If I am able to support this I will.

On Sat, Nov 18, 2023 at 7:12 PM Richard de Crespigny < ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>>> wrote: Tesla is deprecating the REST API by the end of 2023, to be replaced by the Tesla Vehicle Command protocol. Do you have any plans to move your support for Node Red, to this protocol? Thanks Rich — Reply to this email directly, view it on GitHub <#353>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEANBOHOWRM2PHAX4NOGTB3YFF2JXAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYDANRXGYZDQNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>>>

— Reply to this email directly, view it on GitHub<#353 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APAORYLXK264QQ6BDLBCAXDYFGXEHAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXG43TCNJVGY>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***<mailto:***@***.******@***.***>>> —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***<mailto:***@***.***>> — Reply to this email directly, view it on GitHub<#353 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APAORYJCHOSD3AGPSGKJQGTYFKQ4JAVCNFSM6AAAAAA7RNLR2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJYGA2DCNBYGQ>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[andrasg]

Trying to use a nodered integration that relies on this library. Looks like most of the commands are resulting in a 403, probably due to Tesla not allowing REST commands any more.

Any plans to move to vehicle command protocol?

[mseminatore]

I need to figure out auth before I can update the library.

[hitnrun30]

Is there any update on this?

[mseminatore]

Still exploring the repo and fleet-api to understand what can be done.

[tonybroadbent]

Hi, it's worth looking at the signup process.
It would appear you need to specify a domain name, which must have a valid SSL certificate installed, and which will be the endpoint for any communications. I have this and successfully signed up, but there are also comments about 'Trial' and 'Payment'.
Comparing the old API data on 31st Jan 2024 vs. 1st Oct 2023, Drive State: Latitude & Longitude have been removed.
https://developer.tesla.com/docs/fleet-api#2024-01-02-adding-support-for-registering-vehicles-for-fleet-telemetry
Above page claims old API stops after Jan24 (ie. tomorrow); but I'm not sure how the phone app will work without it.

[hitnrun30]

Hi, it's worth looking at the signup process. It would appear you need to specify a domain name, which must have a valid SSL certificate installed, and which will be the endpoint for any communications. I have this and successfully signed up, but there are also comments about 'Trial' and 'Payment'. Comparing the old API data on 31st Jan 2024 vs. 1st Oct 2023, Drive State: Latitude & Longitude have been removed. https://developer.tesla.com/docs/fleet-api#2024-01-02-adding-support-for-registering-vehicles-for-fleet-telemetry Above page claims old API stops after Jan24 (ie. tomorrow); but I'm not sure how the phone app will work without it.

It seems that you need a developer license for it to work. We just need new instructions on the front end.

[hitnrun30]

Have you seen this. It is a step in the right direction