fix(eu-data-act): demote optional-source logs + survive classic-login failure

EU Data Act is now an optional additional source for type=id, not a
required one. Two changes:

1) When the classic VW login fails but EU Data Act came up, don't
   schedule the 30-min restart loop — that would also kill the working
   EU Data Act poller. Log a single warn explaining what's degraded
   (no remote climatisation / force refresh) and keep running. Self-
   heals on next adapter restart.

2) Tone down all EU-Data-Act-related main.js logs so the user doesn't
   read them as errors when the portal side just isn't set up:
   - 'Login in with id (EU Data Act portal)' -> 'Trying EU Data Act
     portal (optional 15-min data source)'
   - failure-in-runEuDataAct prints info-level instructions for
     enabling the portal instead of warn-level 'continuing with legacy
     login only'.

Updated the README accordingly: section title is now 'Optional: EU
Data Act portal as additional data source', the prerequisite section
makes clear that skipping it leaves the adapter fully functional, and
troubleshooting bullets explicitly say these symptoms 'never block the
classic flow'.

Author: TA2k

README.md

@@ -13,20 +13,20 @@
 
 ## vw-connect adapter for ioBroker
 
-Adapter for VW We Connect, We Connect ID (now via the EU Data Act portal), We Charge, myAudi, Skoda Connect, Seat Connect and We Connect Go
+Adapter for VW We Connect, We Connect ID, We Charge, myAudi, Skoda Connect, Seat Connect and We Connect Go
 
 Please update your system on Node 10.
 <https://forum.iobroker.net/topic/22867/how-to-node-js-f%C3%BCr-iobroker-richtig-updaten>
 
-## VW ID via EU Data Act portal (since v0.9.0)
+## Optional: EU Data Act portal as additional data source (since v0.9.0)
 
-Volkswagen retired the WeConnect/MBB API for ID-series vehicles. The adapter now consumes the **continuous 15-minute datasets** that VW publishes via the EU Data Act portal at <https://eu-data-act.drivesomethinggreater.com>. Your data shows up under `<vin>.statuseudata.*` (snake_case dotted names like `battery_state_report.soc`, `mileage.value`, `parking_brake`, `charging_state_report.current_charge_state` and friends).
+For ID-series vehicles the adapter can **additionally** consume the continuous 15-minute datasets that VW publishes via the EU Data Act portal at <https://eu-data-act.drivesomethinggreater.com>. This is **optional** — the classic VW login is the primary source and works on its own. The EU Data Act path adds a few hundred extra data points per dataset (mostly diagnostics, configuration and report fields) under `<vin>.statuseudata.*` (snake_case dotted names like `battery_state_report.soc`, `mileage.value`, `parking_brake`, `charging_state_report.current_charge_state`).
 
-### Prerequisite — enable a continuous data request once
+To enable it you have to set up a continuous data request **once in a browser**; the adapter only downloads what the portal produces, it can't create the request for you. If you skip this step the adapter still works fine, the EU Data Act side just stays silent in the log.
 
-The adapter only **downloads** datasets the portal generates; it cannot create the data request for you. You have to do that **once in a browser** before adding the adapter:
+### Setup the data request (one-time, in a browser)
 
-1. Open <https://eu-data-act.drivesomethinggreater.com/> and **log in with your Volkswagen ID** (same email/password you use in the Volkswagen App).
+1. Open <https://eu-data-act.drivesomethinggreater.com/> and **log in with your Volkswagen ID** (same email/password as in the Volkswagen App and the adapter settings).
 2. Go to **Data clusters → Vehicle overview**.
 3. Click **Connect your car** if your VIN isn't already listed and follow the on-screen pairing/consent steps.
 4. Klicke **Benutzerdefinierte Daten anfragen** ("Get customised data"). Hinweis vom Portal: es kann immer nur eine benutzerdefinierte Datenanfrage gleichzeitig aktiv sein.
@@ -35,17 +35,17 @@ The adapter only **downloads** datasets the portal generates; it cannot create t
 7. **Name des Datenpakets** vergeben (frei wählbar, z.B. "ioBroker"). Erscheint später als `_dataset_name`-Prefix in den Filenames.
 8. **Frequenz wählen**: **Alle 15 Minuten**. Andere Optionen (täglich) liefern nicht genug Auflösung für Live-Werte.
 9. **Dauer**: **Kein Enddatum** (fortlaufend ohne Enddatum).
-10. Anfrage absenden. Wait for datasets to start appearing in the portal's data delivery list — typically **15 minutes to a few hours**. The first batch may show up as `*_no_content_found.zip` until your car wakes up. Force-syncing the car via the Volkswagen app or driving once kicks the producer side awake.
+10. Anfrage absenden. Datasets typically start appearing **15 minutes to a few hours** later. The first batch may show up as `*_no_content_found.zip` until your car wakes up. Force-syncing via the Volkswagen app or driving once kicks the producer side awake.
 
-### Configure the adapter
+The adapter picks up the request automatically — no extra setting in ioBroker. As long as `type` is `VW ID / Volkswagen App` and your credentials match the portal, it polls the listing every minute and downloads only when a new ZIP appears.
 
-In the adapter settings select **VW ID / Volkswagen App (EU Data Act portal)** as type, enter the same email/password you used on the portal, save. Polling defaults are sane — the adapter checks the listing every minute and only downloads when a new ZIP appears (so 14 of 15 cycles short-circuit on the filename cache).
+Object tree per VIN once the EU Data Act side is active:
 
-Object tree per VIN:
-
-```
+```text
 <vin>.general.vin
 <vin>.general.nickname
+<vin>.general.licensePlate
+<vin>.general.imageLocation
 <vin>.statuseudata.battery_state_report.soc          (= 58 %)
 <vin>.statuseudata.battery_state_report.charge_power (= 0.0 kW)
 <vin>.statuseudata.charging_state_report.current_charge_state
@@ -54,15 +54,16 @@ Object tree per VIN:
 <vin>.statuseudata.locked
 <vin>.statuseudata._dataset_name
 <vin>.statuseudata._dataset_created_on
-... and many more (which exact fields depend on the Data Clusters you ticked on the portal)
+... and many more (depending on the Data Clusters you ticked on the portal)
 ```
 
-### Troubleshooting
+### Troubleshooting (EU Data Act only — these never block the classic flow)
 
-- **No vehicles found** in the adapter logs: you skipped the portal-side setup. Open <https://eu-data-act.drivesomethinggreater.com/>, log in, and connect your car (steps above).
-- **HTTP 400 from the data delivery endpoint**: the portal hasn't finished provisioning your continuous data request yet — can take a couple of hours after activation. Adapter retries automatically.
-- **`<vin>.statuseudata` channel is missing**: the portal has no content datasets yet. Force-sync the car via the VW app, or just drive once.
-- **Stale values**: the portal merges several report snapshots into one flat array per dataset. Where the same field appears multiple times with different values, the adapter deterministically picks the entry with the smallest UUID (stable across refreshes — same approach as the home-assistant integration).
+- **`EU Data Act ... no data request configured`**: you haven't done the portal-side setup above. The classic login keeps working in the meantime.
+- **`portal has N dataset(s) but all are '_no_content_found'`**: car was asleep at every sampling slot. Force-sync the car via the VW app, or just drive once.
+- **`<vin>.statuseudata` channel is missing**: the portal has no content datasets yet — same fix as above.
+- **HTTP 400 right after activation**: the portal is still provisioning your data request. Self-heals after a few hours.
+- **Stale values**: the portal merges several report snapshots into one flat array per dataset. Where the same field appears multiple times with different values, the adapter deterministically picks the entry with the smallest UUID (stable across refreshes — same approach as the Home Assistant integration).
 - **Reference implementation** (Home Assistant, Python): <https://github.com/mikrohard/hass-vw-eu-data-act>
 
 ## Usage
@@ -86,9 +87,10 @@ You can set climatisaton temperature in
 ```
 
 ```
-### 0.9.0 (2026-05-30)
+### **WORK IN PROGRESS**
 
-- VW ID flow migrated to the EU Data Act portal (`eu-data-act.drivesomethinggreater.com`). Status data is now under `<vin>.statuseudata.*`. Requires a continuous 15-min data request set up once on the portal — see "VW ID via EU Data Act portal" above.
+- fix normal login for VW and Audi
+- add optional EU Data Act portal data flow
 
 ### 0.8.8 (2026-05-28)
 

main.js

@@ -306,24 +306,25 @@ class VwWeconnect extends utils.Adapter {
       this.tripTypes.push("cyclic");
     }
 
-    // VW ID accounts: run the EU Data Act portal pipeline ZUSÄTZLICH zum
-    // klassischen Login. Der EU Data Act Pfad liefert die offiziellen
-    // 15-min-Datasets, der klassische Login (jetzt via OIDC Hybrid Flow) liefert
-    // die Live-API über emea.bff.cariad.digital — die meisten User wollen beides.
+    // VW ID accounts: run the EU Data Act portal pipeline as an OPTIONAL
+    // additional data source alongside the legacy WeConnect login. The EU
+    // Data Act path requires the user to have set up a continuous data
+    // request on the portal first (https://eu-data-act.drivesomethinggreater.com/);
+    // if they haven't, that is fine — the legacy login below covers the
+    // primary data needs and the EU Data Act side just stays silent.
     if (this.config.type === "id") {
       this.runEuDataAct().catch((err) => {
         const msg = (err && err.message) || String(err);
-        this.log.warn("EU Data Act flow failed: " + msg);
-        // Credential / account problems don't self-heal on a restart — just
-        // log once and continue with the legacy login below.
-        if (/login failed|password_invalid|email_invalid|account.*(locked|disabled)|not entitled/i.test(msg)) {
-          this.log.warn(
-            "EU Data Act unavailable, continuing with legacy login only. " +
-              "If neither works, update user/password in the adapter settings.",
-          );
-          return;
-        }
-        this.log.warn("EU Data Act will retry on next adapter restart");
+        // Everything EU-Data-Act-related stays at info level: the portal is
+        // a bonus source, not the primary one. We don't want the log to
+        // look alarming when the user simply hasn't activated it.
+        this.log.info("EU Data Act (optional source) not available: " + msg);
+        this.log.info(
+          "EU Data Act is an optional 15-min portal data source. To enable it, " +
+            "log in once at https://eu-data-act.drivesomethinggreater.com/, link " +
+            "your vehicle and configure a continuous 15-minute data request. " +
+            "The classic VW login below covers the primary data either way.",
+        );
       });
       // Fällt durch zu this.login() unten — der Hybrid Flow läuft parallel.
     }
@@ -452,6 +453,17 @@ class VwWeconnect extends utils.Adapter {
         });
       })
       .catch(() => {
+        // For type=id we treat the classic flow as best-effort: if EU Data
+        // Act came up successfully we already have data flowing under
+        // <vin>.statuseudata, so a 30-min restart loop would only kill that.
+        if (this.config.type === "id" && this.euDataAct && this.euDataAct._loggedIn) {
+          this.log.warn(
+            "Classic VW login failed, but EU Data Act portal is connected — " +
+              "continuing with EU Data Act as the only data source. Live API features " +
+              "(remote climatisation, force refresh) won't work until the classic login recovers.",
+          );
+          return;
+        }
         this.log.error("Login Failed");
         this.log.error("Restart Adapter in 30min");
         setTimeout(() => {
@@ -6907,7 +6919,7 @@ class VwWeconnect extends utils.Adapter {
    * initial status fetch and arms the periodic refresh.
    */
   async runEuDataAct() {
-    this.log.info("Login in with id (EU Data Act portal)");
+    this.log.info("Trying EU Data Act portal (optional 15-min data source)");
     // Load json2iob enrichment maps once. Both files are derived from the
     // EU Data Act PDF data dictionary; descriptions are friendly names per
     // dataFieldName leaf, states are rawValue->label maps for enum fields.
@@ -6925,7 +6937,7 @@ class VwWeconnect extends utils.Adapter {
       log: this.log,
     });
     await this.euDataAct.login();
-    this.log.info("Login successful (EU Data Act)");
+    this.log.info("EU Data Act portal connected");
     this.setState("info.connection", true, true);
     this.extendObject("refresh", {
       type: "state",