Tesla owners using the Tesla REST API will get some (hopefully short term) pain because Tesla is increasing the security on vehicle commands. I was writing a program to optimize the charging times of my cars in order to get the lowest possible charging cost (I already use apps for this but they can't take into account other electricity usage in my house) and got the following error when trying to start charging my new Model S: "Tesla Vehicle Command Protocol required, please refer to the documentation here:
Tesla Fleet API". If you read the announcements on that page it turns out that in January 2024 all vehicles will require the Tesla Vehicle Command protocol, and the REST (command) API will be fully deprecated.
If I understand it correctly it means that any app that sends commands to a Tesla will not only need to be authenticated, it will also need to identify itself to the car, with the car being able to verify that identity (much like the car knows about key fobs and cell phone keys) - end-to-end command authentication.
It means that apps like Jedlix will be completely broken as of januari (they are already broken for cars delivered since November).
The bar for being able to control a Tesla is now significantly higher: it requires registration (and acceptance) at Tesla, a verifiable endpoint on the internet and increased programming complexity.
That's ok for commercial apps like Jedlix, TeslaFi etc (and good for the peace-of-mind of the Tesla owners), but really bad for hobbyists as it has gotten very complex and expensive to keep doing what they could easily do with the soon to be deprecated REST API.
I expect some bad media coverage around this.