Volkswagen Group disabled third party access to its vehicle cloud API on May 27 2026, abruptly cutting off popular open source tools like Home Assistant and openWB while its own branded smartphone apps kept authenticating normally. The change hit owners across Volkswagen, Audi, Skoda, and Cupra, removing features that tech focused EV owners relied on daily to control charging, precondition their cabins, and fold their cars into home energy systems. It is a small story on paper and a large one in what it signals about who really controls a connected car.
What Exactly Did Volkswagen Shut Down?
Independent developers had built far more capable tools than Volkswagen ships itself, giving owners granular control over when and how their cars charged at home compared to the basic features in the official app. The two biggest use cases ran through Home Assistant, the widely used open source home automation platform, and openWB, an open source EV charging and energy management system. On May 27, every third party client using the Volkswagen Group cloud service began failing to connect at once, while the brand apps continued working without interruption.
Volkswagen declined to comment when CarBuzz reached out. The only official response came through Skoda in Europe, which said the group now has a formal framework for third party access to vehicle data. Read plainly, that wording points to a paid business to business licensing model, where a company can license data across all the included brands under one legal framework, which functionally freezes out individual consumers and hobbyist developers. After backlash from owners, Skoda added that it understands how important smart home integrations like Home Assistant are and said it was exploring ways to preserve selected basic functions in a secure way. The phrase selected basic has not reassured anyone.
Why Does This Matter Beyond a Few Power Users?
Because it is a clean example of a pattern that keeps repeating across connected products. Automakers routinely cite data protection, cybersecurity, and system stability when they restrict access, and those concerns are not fake. But critics point out that the same justifications conveniently double as a way to limit owner control and push customers toward subscriptions. When the official app survives the cutoff and only the independent tools die, the security framing gets harder to take at face value.
This connects to a broader squeeze on people who want control over their own devices. Owners running privacy focused setups have increasingly found themselves locked out of apps through integrity checks that treat anything outside the default configuration as a threat, and the Volkswagen move is the same instinct applied to cars. You bought the hardware, but the data it generates and the ways you are allowed to use it remain firmly the manufacturer's to grant or revoke. For anyone building a home energy system around an EV, that is a real risk to plan around.
Is There Any Path Back for Third Party Access?
Possibly, but probably not on the old terms. Skoda's language suggests Volkswagen wants to formalize access through paid licensing rather than restore open consumer integrations, which means the future likely involves either a sanctioned partner program or a stripped down set of basic functions handed back to quiet the complaints. Neither outcome returns the granular control owners had through Home Assistant and openWB before the shutdown.
The practical lesson for buyers is to treat connected car features as revocable, not permanent, and to factor that into purchase decisions if home integration matters to you. The leverage owners have is collective: the backlash already forced Skoda to respond publicly, and sustained pressure is the only thing that historically moves manufacturers on this. Until then, the safe assumption is that any open integration with a modern car can vanish in a single server side update.
Check out what else is trending at Hacker News