Merge pull request #344 from renaudallard/main

Update README: NK charging prediction works via charging.power

Author: kvanbiesen

README.md

@@ -464,7 +464,7 @@ The integration is organized into focused modules:
 - The CarData API is read-only; sending commands remains outside this integration.
 - **Premature Continue in auth flow: If you hit Continue before authorizing on BMW's site, the device-code flow gets stuck. Cancel the flow and restart the integration (or Home Assistant) once you've completed the BMW login.**
 - **Older models (i3, i3s, iDrive 6 cars, older F-series)**: These vehicles send telemetry very infrequently — typically only when the car is stopped/turned off and when charging reaches 100%. There are no real-time MQTT updates while charging or driving, so most sensors will appear stale between events. The Predicted SOC sensor can help during charging, but accuracy depends on receiving at least an initial SOC value. This is a BMW platform limitation, not a bug in the integration.
-- **Neue Klasse (NK/NA5) vehicles**: BMW's CarData API does not currently provide `batteryManagement.header` or `charging.level` for NK vehicles. The integration uses `stateOfCharge.displayed` as the primary SOC source, with `trip...hvSoc` (trip-end battery level) as a last resort. `stateOfCharge.displayed` updates via API polls but may not refresh in real-time during driving. Charging prediction is not available. BMW may add proper NK support to CarData in the future.
+- **Neue Klasse (NK/NA5) vehicles**: BMW's CarData API does not provide `batteryManagement.header` or `charging.level` for NK vehicles. The integration uses `stateOfCharge.displayed` as the primary SOC source, with `trip...hvSoc` (trip-end battery level) as a last resort. `stateOfCharge.displayed` updates via API polls but may not refresh in real-time during driving. Charging prediction works via `charging.power`.
 
 ## Stale Issue Policy