Repository navigation
v0.43.0
What's Changed
⚡ New: Smart Charging sensors
Some newer cars got the smart charging feature in the last weeks. Your car reports what smart charging is doing, and the integration now shows it in four sensors:
| Sensor | What it shows |
|---|---|
| Smart Charging Location | the charging location your car reports, e.g. Home |
| Smart Charging Station | the charging station at that location |
| Smart Charging Strategy | the strategy that applies, e.g. PRICE_OPTIMIZED_CHARGING |
| Smart Charging Error | what is currently standing in the way, unknown when nothing is |
Note
This is most likely limited to cars on the newer MMA platform (the CLA from 2025 onwards and the models that follow it). Smart charging does not exist on older cars, and a car that does not report it simply does not get these four sensors — they will not show up as unknown or unavailable, they are not created at all. If your car charges and you still see no sensors, a debug log would be very welcome.
Your car can report more than one problem at a time. The Smart Charging Error sensor then shows the most serious one, and keeps the full list as an attribute:
smartChargingErrorList:
- code: UNAVAILABLE_MISSING_VEHICLE_CONNECTION
severity: MAJOR_ERROR
- code: UNAVAILABLE_WITHOUT_OPTIMIZATION
severity: WARNINGWhen your car reports no problem, the sensor stays unknown rather than claiming everything is fine — that is a state your car never sends.
Under the hood
- The message definitions were refreshed against the current state of the car API, including states that cars already report but the integration did not recognise, such as a window or sunroof that is still moving. (#464)
- When the server sends a message type this version does not know, the debug log now names it instead of writing
None— which is what makes such things reportable in the first place. (#460) - The app and SDK version the integration announces moved to the current release (
1.73.0/4.20.1, and the regional equivalents). Running an outdated version risks requests being refused by the backend. (#463, #465)
Full Changelog: v0.42.0...v0.43.0