Volkswagen Connect API shutdown stalls Home Assistant integration

![Featured image]()

The problem

Users of the open‑source homeassistant‑volkswagencarnet integration suddenly started receiving the error "Anmeldung bei Volkswagen Connect nicht möglich. Bitte überprüfe deine Zugangsdaten und stelle sicher, dass der Dienst verfügbar ist." When they try to authenticate, the service reports that the login has expired and no new credentials can be created. The same credentials still work in the official Volkswagen Android app and on the web portal https://vwid.vwgroup.io/, which shows that the issue is not with the user’s account but with the API endpoint the integration talks to.

Why it matters

The integration is a key bridge for Home Assistant users who want to automate charging, climate control, and remote locking of their VW, Audi, Skoda, or Seat vehicles. It pulls data such as battery state‑of‑charge, charging power, door lock status, and vehicle location, enabling scripts that balance solar production with charging, trigger alerts when the car is left unlocked, or log mileage for fleet management.

When Volkswagen permanently disabled the unofficial API, the integration lost its only communication channel. The community has confirmed that the official, paid API still works for the native app, but it is not publicly documented and requires a commercial contract (e.g., services like Tronity). As a result, any Home Assistant instance that relied on the free API can no longer fetch live data, and the token‑based authentication used by the integration cannot be refreshed after a Home Assistant restart.

Community reaction and work‑arounds

• Guetld noted that the shutdown appears intentional and that the commercial API is still functional for paying customers.
• Tillsteinbach’s CarConnectivity plugin (https://github.com/tillsteinbach/CarConnectivity-plugin-mqtt) continues to work only for users who had previously obtained a token; it will stop once that token expires.
• Some users reported a temporary recovery after updating Home Assistant to v5.4.7, but the issue re‑appeared after a restart, confirming that the root cause is the missing token refresh capability.
• A handful of participants have reached out to Volkswagen support channels (e.g., gis‑[email protected], [email protected]) and even contacted a VW board member, but Volkswagen has not issued a public statement about the API closure.

Regulatory angle

The shutdown raises questions under the EU Data Act (Regulation (EU) 2023/2854), which obliges data holders to provide real‑time access to data generated by connected devices. Several commenters, including UdoRat, suggested filing a compliance incident via Volkswagen’s reporting portal https://goto.speakup.report/volkswagen, arguing that removing the API without a replacement may constitute a breach of the regulation.

What’s next for users?

1. Switch to the paid API – Companies like Tronity offer a commercial gateway that can be integrated into Home Assistant via MQTT, but this incurs a subscription cost.
2. Wait for an official replacement – If Volkswagen decides to open a new developer program, the community may be able to build a new integration. Until then, the current repository is effectively deprecated.
3. Explore alternative telematics services – Some owners have moved to third‑party platforms that aggregate data from multiple manufacturers, though they often require additional hardware or cloud subscriptions.

Bottom line

The abrupt termination of the unofficial Volkswagen Connect API has left a sizable segment of the Home Assistant community without a free way to monitor their cars. While the official Android app remains functional, the open‑source integration that powered many clever automations is now unusable. Users must either accept the commercial route or wait for Volkswagen to publish a new, supported API.