There is most likely an overlap on what you can get from the OBD port, but generally speaking the API will provide more high level info e.g driving status, mileage, live location - and the OBD port will provide more low level data e.g. detailed battery stats from the BMS, energy usage, etc.
Highlight where in the above post I am defending anything.
Something to note: Tesla has two vehicle APIs, the Fleet API for commercial accounts and the Owner API for individuals. This change currently only impacts the Fleet API.
If you are an individual owner who accesses your vehicle data from the Owner API (usually via a self hosted tool like TeslaMate), this does not affect you. Yet.
How often do you need to travel the entire range your car allows?
If you do need to drop everything and drive across country in an EV, you should be stopping at service stations to do short fast charge sessions anyway, as with modern fast chargers and battery tech you will typically go from something like 30% SoC to say 70% in only a few minutes. This saves a lot of time on longer trips.
If you are driving an EV by depleting the battery completely and then charging it back to 100% every time, you are doing it wrong.
That also means we can still use the expansion cards for the Framework in any other device that also has a USB-C port. Need an SD card reader or a 2.5Gb LAN adapter? Not a problem, I’ll just grab one from my laptop.
Not at all.
Lemmy is overwhelmingly militantly anti-Tesla, which is understandable considering who owns it, but it does mean that users tend to interpret any neutral or factual statements (basically anything that is not outright criticism) as having a pro-Tesla bias.
In this case, all I am stating is the fact that this specific change currently only affects corporate users. That could of course change in the future.
There is a rich history of cloud based data providers pulling the rug from under users with no warning. Look at what happened to Nest users when Google took over.