[Discussion] What would it take to selfhost some of the backend that Tesla's connect to?
-
I saw this article earlier:
Tesla 'going bankrupt' is endpoint of protests, says local organizer
In the spirit of right to repair, self-hosting, giving a second life to old devices, and limiting data collection by car companies:
- What are some considerations?
- Are there any projects worth keeping an eye on?
An example that came to mind was Valetudo, which is a cloud replacement for vacuum robots enabling local-only operation. Some robot vacuums are easy to install this on, and others require more invasive modifications.
What I've found so far:
Just sell the car to a derby demolition show. We all win.
-
First, second and third most important point is :
Tesla needs to allow the connection to an alternative server.The fourth should be access to the api and data that are exchanged.
You shouldn't mess with the FW of your own car even for some innocent feature like this one, you don't know/understand the interactions that may happen between different Sw components and the hw layer, you can not provide a similar of level of testing, including some worst case scenarios, that can make your car unsafe during some problems or unforeseen conditions. And perhaps also, the car could loose its license for driving....
If tesla allows that, then we can start speaking about it. But last time I check on that was not possible
Yeah, the potential for real hazard to life and limb is very high here. This isn't like fucking around with your IOT lightbulbs. This could kill somebody.
-
I saw this article earlier:
Tesla 'going bankrupt' is endpoint of protests, says local organizer
In the spirit of right to repair, self-hosting, giving a second life to old devices, and limiting data collection by car companies:
- What are some considerations?
- Are there any projects worth keeping an eye on?
An example that came to mind was Valetudo, which is a cloud replacement for vacuum robots enabling local-only operation. Some robot vacuums are easy to install this on, and others require more invasive modifications.
What I've found so far:
A problem is volunteers and critical mass.
Open source "hacks" need a big pool of people who want something to seed a few brilliant souls to develop it in their free time. It has to be at least proportional to the problem.
This kinda makes sense for robot vacuums: a lot of people have them, and the cloud service is annoying, simpler, and not life critical.
Teslas are a whole different deal. They are very expensive, and fewer people own them. Replicating even part of the cloud API calls is a completely different scope. The pool of Tesla owners willing to dedicate their time to that is just… smaller.
Also, I think buying a Tesla, for many, was a vote of implicit trust in the company and its software. It’s harder for someone cynical of its cloud dependence to end up with one.
-
Assuming that Tesla goes bankrupt, actually shuts down forever, and shuts its servers down…
At a minimum someone would have to find out where the software sends and receives data from. Then you’d have to reverse engineer the software to control the vehicles.
Then you’d have to reprogram the software to send to your C&C server. I don’t think it would really take all that much to host that… it’s getting there that’s difficult.
You'd likely need all kinds of cryptographic keys to get anywhere with that. Tesla is unlikely to ever publish those, even if they go bankrupt.
-
I saw this article earlier:
Tesla 'going bankrupt' is endpoint of protests, says local organizer
In the spirit of right to repair, self-hosting, giving a second life to old devices, and limiting data collection by car companies:
- What are some considerations?
- Are there any projects worth keeping an eye on?
An example that came to mind was Valetudo, which is a cloud replacement for vacuum robots enabling local-only operation. Some robot vacuums are easy to install this on, and others require more invasive modifications.
What I've found so far:
The right to repair. It's going to require the ability to make changes to the software on the vehicle. At a minimum the ability to replace the public encryption keys used to communicate with the servers. The bootloader and software is probably locked behind signing keys; so you need to be able to disable or add your own keys. I doubt anyone has access to the full protocols used to communicate with the servers. So, the full technical standard need to be released (which is never going to happen) or reversed engineered through unencrypted traffic analysis and reverse engineering the software.
A good right to repair law could require some of that be releasable while the company is still active or all if the company goes belly up. IIRC there was a smaller EV company that went bankrupt and there was a concern that once the servers were shutdown the vehicles would be bricked. Not sure what happened in the end. In any case, cars as IOT is the stupidest idea ever created.
-
If I had a Tesla and someone smart enough to hack into I wouldn't doubt I could probably figure out how they build their dashboards, they're most likely browser based or qt or something like it. It'd be too costly to do it in anything else and Id bet many spacex dashes are the same tech. But I ain't rich enough to get one of those things so someone else has to
They are browser based, their whole UI and much of the in car backend is a JavaScript.
-
I saw this article earlier:
Tesla 'going bankrupt' is endpoint of protests, says local organizer
In the spirit of right to repair, self-hosting, giving a second life to old devices, and limiting data collection by car companies:
- What are some considerations?
- Are there any projects worth keeping an eye on?
An example that came to mind was Valetudo, which is a cloud replacement for vacuum robots enabling local-only operation. Some robot vacuums are easy to install this on, and others require more invasive modifications.
What I've found so far:
Not in these next 4 years.
Afterwards, if judges still exist, you can try to force Tesla (with the help of judges) to allow your right to repair.
-
I saw this article earlier:
Tesla 'going bankrupt' is endpoint of protests, says local organizer
In the spirit of right to repair, self-hosting, giving a second life to old devices, and limiting data collection by car companies:
- What are some considerations?
- Are there any projects worth keeping an eye on?
An example that came to mind was Valetudo, which is a cloud replacement for vacuum robots enabling local-only operation. Some robot vacuums are easy to install this on, and others require more invasive modifications.
What I've found so far:
You can't
-
You'd likely need all kinds of cryptographic keys to get anywhere with that. Tesla is unlikely to ever publish those, even if they go bankrupt.
On the upside: if you mod your car to get around all that, you'll probably be able to emulate old consoles on it and play pokemon games while driving.
-
Some brainstorming from me:
- Ideally people do not buy more teslas
- An initial goal would be to use the vehicle without it phoning home. Would the TeslaMate project be sufficient for that?
- Long term, would it be possible to replace the software running on the car's console? Or would it be better to tear out the console and replace it with something else.
Alternatively, what would a recycling program look like?
Everything that polls Tesla data goes through (at lease negotiated access) Tesla servers.
That includes TesMate, TeslaFi, Tessie, etc.
-
They are browser based, their whole UI and much of the in car backend is a JavaScript.
JavaScript
Ah, they're that kind of evil.
-
You can't
Not that you aren't entitled to your opinion, but software running on a Tesla is, in many ways just as mallaible as code on a vacuum robot.
There are several challenges, but basically the protections stopping people from reading and writing firmware would need to be defeated.
I think there have been some software jailbreaks on earlier models already that have been patched, but software is complicated, it's hard be bug free.
-
The right to repair. It's going to require the ability to make changes to the software on the vehicle. At a minimum the ability to replace the public encryption keys used to communicate with the servers. The bootloader and software is probably locked behind signing keys; so you need to be able to disable or add your own keys. I doubt anyone has access to the full protocols used to communicate with the servers. So, the full technical standard need to be released (which is never going to happen) or reversed engineered through unencrypted traffic analysis and reverse engineering the software.
A good right to repair law could require some of that be releasable while the company is still active or all if the company goes belly up. IIRC there was a smaller EV company that went bankrupt and there was a concern that once the servers were shutdown the vehicles would be bricked. Not sure what happened in the end. In any case, cars as IOT is the stupidest idea ever created.
-
Just sell the car to a derby demolition show. We all win.
That's wasteful and dangerous
Harvest the beast for batteries and GPUs
-
On the upside: if you mod your car to get around all that, you'll probably be able to emulate old consoles on it and play pokemon games while driving.
...But will it run DOOM?
-
I saw this article earlier:
Tesla 'going bankrupt' is endpoint of protests, says local organizer
In the spirit of right to repair, self-hosting, giving a second life to old devices, and limiting data collection by car companies:
- What are some considerations?
- Are there any projects worth keeping an eye on?
An example that came to mind was Valetudo, which is a cloud replacement for vacuum robots enabling local-only operation. Some robot vacuums are easy to install this on, and others require more invasive modifications.
What I've found so far:
If you bought a live service car you're probably shit out of luck
-
That mentality is how we got here in the first place. A person should have a right to understand and repair everything happening in devices they own. Because they don't, we get stuck in the shitty situation where Elon Musk can unlock any Tesla he pleases and I can't refuse to send my data to him. Or any other car manufacturer. Or tractor manufacturer. Or IoT manufacturer.
Mixed feelings on this. Yeah, you buy it you should own it. But if your ability to fuck with a two-ton rolling death machine puts my ass at risk, we've git a fucking problem.
-
I saw this article earlier:
Tesla 'going bankrupt' is endpoint of protests, says local organizer
In the spirit of right to repair, self-hosting, giving a second life to old devices, and limiting data collection by car companies:
- What are some considerations?
- Are there any projects worth keeping an eye on?
An example that came to mind was Valetudo, which is a cloud replacement for vacuum robots enabling local-only operation. Some robot vacuums are easy to install this on, and others require more invasive modifications.
What I've found so far:
probabaly full replacement of the motor controller and user facing hardware. basically a diy ev conversion using tesla motors but converting the tesla itself. you would lose features but they would be lost regardless.
-
Mixed feelings on this. Yeah, you buy it you should own it. But if your ability to fuck with a two-ton rolling death machine puts my ass at risk, we've git a fucking problem.
I have some bad news for you - any random idiot with a driver's license and a two-ton death machine already puts your ass at risk, all the time. We call it "traffic" because we've just gotten used to it
-
I have some bad news for you - any random idiot with a driver's license and a two-ton death machine already puts your ass at risk, all the time. We call it "traffic" because we've just gotten used to it
It is not comparable, not even by far.
Assuming your are not a psycho, to safely drive a car is orders of magnitude (in plural) easier than modifying the Sw in a safe and deterministic way.
It is not only that bad people exists, it is about that making a small mistake can kill you
