Volkswagen blocks Home Assistant by requiring client assertion

Re:Volkswagen blocks Home Assistant by requiring client asse... by V1ndaar on Friday May 29, 2026 @04:37AM (#48320643)

Huh, I completely missed that. I've been using python-garminconnect [0] for a few months without issues. I agree though that it's annoying, though not reason enough for me to switch away from Garmin yet.

  [0]: https://github.com/cyberjunky/python-garminconnect

[ Parent | on HN ]

Re:Volkswagen blocks Home Assistant by requiring client asse... by aenis on Friday May 29, 2026 @05:42AM (#48321036)

Already minted tokens work, they broke the login process.

For now its just tls fingerprinting, not client attestation - so, I managed to implement a working solution. But I am sure they will tighten the screws still further.

[ Parent | on HN ]

Re:Volkswagen blocks Home Assistant by requiring client asse... by msiemens on Friday May 29, 2026 @04:42AM (#48320671)

Same here. I've been scraping the data from my Garmin watch for years with very little problems (first with https://github.com/tcgoetz/GarminDB, then https://github.com/sealbro/dotnet.garmin.connect).

The only annoyance is that Garmin requires 2FA if you enable the ECG feature on your smart watch/fitness tracker, but I have a small program that reads the 2FA codes from my Gmail inbox and supplies them to the scraper without too much trouble.

[ Parent | on HN ]

Re:Volkswagen blocks Home Assistant by requiring client asse... by saltcured on Friday May 29, 2026 @11:21AM (#48324294)

Have you looked at the feasibility of making your own CIQ app to push data from the watch to your alternate internet endpoint?

I have the impression there are permissions and APIs to access sensor history and activity records, but I haven't had a need to dig in and learn what restrictions there might be...

[ Parent | on HN ]