feat(vag_vehicle): sign in with email and password, report SoC age

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## vag_vehicle 0.2.0
+
+Sign in with the account email and password instead of a pasted portal cookie, and sign in again when the portal session ends after about an hour (srcfl/device-drivers#143). The sign-in follows evcc's EU Data Act client: the identity form, the password page's `window._IDK` state, then the redirects back to the portal, skipping an optional marketing consent page. It needs an FTW Core with `host.http_request`. The host keeps the session cookies, and every redirect is a separate request checked against `allowed_hosts`. A failed sign-in waits 15 minutes before the next try, so a wrong password cannot lock the account. On an older Core, a pasted `cookie` works as before. `identity.vwgroup.io` joins `http_hosts`, `password` joins `config_secrets`, and the two sign-in form paths per brand are declared: the first in `auth_post_path`, so an older Core still accepts the driver, and the rest in `auth_post_paths`.
+
+The driver now reports the reading's age as `vehicle_soc_age_s`. The SoC data point carries the time the car measured it, and the portal's `Date` header gives the time now, so no wall clock is needed. A reading the car measured more than 20 minutes ago is not a fresh observation, even in a new file. A fresh first file after start is no longer marked stale. Ages are reported only in sign-in mode, since cookie mode reads through `host.http_get`, which does not return headers. Tested against a scripted portal, not yet against the live portal or a car.
+
 ## esphome_dsmr 1.0.7
 
 Declare an empty `host` in `connection_defaults`, so FTW setup passes the

SUPPORT_STATUS.md

@@ -168,8 +168,8 @@ Catalog source is not proof that a target can install or run a driver.
 | teslamate_vehicle | 0.1.0 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
 | tibber | 1.1.2 | ftw-core | not_assessed | — | not_recorded | not_assessed |
 | tibber | 1.1.2 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
-| vag_vehicle | 0.1.1 | ftw-core | not_assessed | — | not_recorded | not_assessed |
-| vag_vehicle | 0.1.1 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
+| vag_vehicle | 0.2.0 | ftw-core | not_assessed | — | not_recorded | not_assessed |
+| vag_vehicle | 0.2.0 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
 | varta | 1.1.1 | ftw-core | not_assessed | — | not_recorded | not_assessed |
 | varta | 1.1.1 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
 | victron | 2.1.2 | ftw-core | not_assessed | — | not_recorded | not_assessed |

devices.yaml

@@ -2064,11 +2064,11 @@ manufacturers:
         protocols:
           - protocol: http
             driver: "vag_vehicle"
-            version: "0.1.1"
+            version: "0.2.0"
             ders: [vehicle]
             control: false
         firmware_versions: ""
-        notes: "Read-only SoC and charge state from the VW Group EU Data Act portal. We Connect third-party APIs are blocked. Owner must enable a continuous 15-minute All Data request and paste a portal session cookie. Not live BMS; charging does not need this cloud. Porsche is not on this portal. Not yet run against the portal or a car."
+        notes: "Read-only SoC and charge state from the VW Group EU Data Act portal. We Connect third-party APIs are blocked. Owner must enable a continuous 15-minute All Data request. The driver signs in with the account email and password and renews the session itself on an FTW Core with host.http_request; an older host needs a pasted portal session cookie. Not live BMS; charging does not need this cloud. Porsche is not on this portal. Sign-in follows evcc and is tested against a scripted portal, not yet against the live portal or a car."
   - name: "Wallbox"
     model_families:
       - name: "Commander/Pulsar"