What this is really about
Forget, for a moment, whether what I did was right. Forget whether using FSD was legal. Neither is the point.
What matters is this: Tesla didn’t like that I modified a car I own outright — so it reached in and remotely bricked part of it. Not just the feature some people assume is illegal (it isn’t, on private roads) — but fully legal safety features the car shipped with from new, part of the very €6,200 + VAT package I had paid for.
This is not the Kindle store. It is not Steam. It is a car — a physical thing I bought and own — sold to me with a list of features, every one of which Tesla can switch off from a server. (Ask anyone who remembers the old “Winter Package.”) Break Tesla’s terms and, in effect, the car drives itself back to the factory. No refund. Tens of thousands of euros, gone.
Tesla stays silent — but it behaves as though I never bought a car at all. As though I only ever licensed the right to use one. So the real question isn’t about me. It’s about everyone who drives:
01What I bought
In Tesla’s ordering system, the Full Self-Driving Capability package was listed at €6,200 (net, pre-VAT). I paid it. The screenshot below is exactly what I bought.
That last line matters. Traffic Light and Stop Sign Control was a genuine safety feature for me: it stops the car automatically at red lights and stop signs. To this day, the official Tesla mobile app still lists the Full Self-Driving Capability package as included with my vehicle.
02It worked — for months
After delivery I used the package’s advertised features throughout Europe. Traffic Light and Stop Sign Control operated alongside Autopilot, fully and reliably. The car ran without issue for months.
I own the car outright — I do not lease it from Tesla. I take the view that I am entitled to modify a car I own, the same way I might fit custom wheels, a body kit, or new suspension, without the manufacturer penalising me for it.
The “modifications,” in full
I used two CANBUS diagnostic devices — “Commander” by enhauto.com and a device called “Cybertool.” Neither modifies the car or its software. They connect only to the standard CANBUS diagnostic port — the same interface manufacturers provide for diagnostics — and send commands the vehicle already supports.
For example, Commander makes the interior LEDs turn blue when Autopilot is engaged. The car reads a supported signal, sends a supported command, and the colour changes. If the car didn’t support that command, nothing would happen. No PCB altered. No component changed. No original part modified. Tesla itself states publicly that the vehicle software is immutable by third parties.
Cybertool works the same way. Just as Commander tells the car to turn its interior LEDs blue, Cybertool sent the car a command it already supported — to switch on the Full Self-Driving package in regions where Tesla had not yet enabled it. It unlocked nothing new: it simply turned on the feature my car was built for and I had already paid for. The car either supports a command or it doesn’t; mine did, because the package was licensed to it.
This is the same category of action as Commander disabling the reversing-gear chime — something Commander openly does, even though that chime is mandatory in the EU. And to be completely fair: Full Self-Driving is not yet approved for public roads in every region, in the same way a loud exhaust or slick tyres aren’t road-approved. That doesn’t make the equipment itself illegal — you can run slicks and a loud exhaust on a track. Enabling a feature the car was built and paid for is not the same as breaking the law with it: where and how it is used is the driver’s responsibility, not something a diagnostic command decides.
No safety system — hardware or software — has been modified in any way.
03What happened
On 8 April at 22:27, my car received a remote package-configuration update via Tesla Cloud Config. In effect, Tesla remotely told my car that the €6,200 + VAT package had never been purchased.
Roughly three hours later, at 02:00, this email arrived.
It is notably vague. It does not say which device was detected, what the safety risk was, how long features would be disabled, or even whether they would return. And the phrase puzzles me: unauthorized third-party device — unauthorised by whom? Every device on my car was authorised by its owner. Me.
04The contradiction
FSD approval rolled out across Europe — the Netherlands first, then Lithuania, then Estonia on 29 May (where my car is registered), and Belgium after that. My car received update 2026.17.5, which enables the new system. This was the moment my investment should finally have paid off.
Instead, the car offers me a “Subscribe” button — as if I had never bought it.
I paid €6,200 + VAT for a package. The car confirms the package is “Included.” And the same car behaves as though it was never bought.
05How the car knows what it has
Every Tesla ships with the same software and the same full set of capabilities. Individual features are switched on or off remotely through “Tesla Cloud Config,” tied to your specific car. It’s the same mechanism that once let Tesla sell cars with the hardware for heated rear seats physically present but disabled — and later let owners pay online to unlock them.
It’s also how Tesla distinguishes Basic Autopilot from Enhanced Autopilot from Full Self-Driving. The distinction is purely software-defined. Which means a feature you paid for can be revoked with a single remote flag — exactly what happened to me.
06Warranty service was refused
My car is under warranty, so I contacted Tesla service centres in Turku, Finland and Warsaw, Poland. Both confirmed the functionality does not work. Both confirmed the car is under warranty. Both refused the claim — saying it is “not serviceable” because the car was intentionally disabled “for safety reasons.”
The Finnish centre told me they could not reactivate the feature even though the device had been removed, because “you may install it again.” By that logic, why not disable the feature on every Tesla — since any car could have such a device fitted?
I am left unable to find any explanation other than this: the “safety reasons” cited actually reduce my safety. For eight weeks my car could not detect stop signs or traffic signals — functionality I had come to rely on.
07The questions Tesla won’t answer
I put these questions to Tesla and its service centres. They remain unanswered. I’ve grouped them by theme.
A The warranty refusal
B The decision to disable
C The claimed “safety reasons”
D Restoration of the paid features
E Compensation
F Policy on modifications & third-party devices
I requested a written response within 14 days, addressing each point. I’m still waiting.
08I’m not anti-Tesla
I’m a genuine believer in this technology. I bought two Teslas and pre-paid €12,400 + VAT in total against the promise of FSD. That promise took so long to materialise that I sold one of the cars — losing the value of the package on it.
Now I finally have a working car, with FSD purchased, in a country that permits FSD. And Tesla is deliberately preventing me from using what I paid for. I just want the feature I bought, an answer to my questions, and for this not to happen quietly to anyone else.
09Timeline
- 2025Buy a 2025 Model Y as first owner with FSD Capability — €6,200 + VAT.
- Months after deliveryFSD features, including stop-sign and traffic-light control, work reliably across Europe.
- 8 Apr 2026 · 22:27Remote Cloud Config update: “Your Autopilot package has returned to its original configuration.” Features lost.
- 9 Apr 2026 · 02:00Tesla emails about an “unauthorized third-party device” disabled “for safety reasons.”
- 8 weeksNo further information. The diagnostic device is removed; no third-party device remains on the car.
- 29 May 2026Estonia — where my car is registered — approves FSD on public roads (after the Netherlands and Lithuania, before Belgium). Update 2026.17.5 arrives.
- NowCar offers a “Subscribe” button for FSD it says is “Included.” Two service centres refuse warranty repair.