Changes
‼️ Breaking change
- Climatisation temperature number and On/Off switch entities replaced by single Climate control entity
🚀 Features
-
Added ability to configure S-PIN and mutable (read-only mode) through the integration options flow, allowing users to update these settings without reconfiguring the entire integration. #849
-
Climate Control Implementation: #776
- Fix climate instrument instantiation in dashboard definitions
- Correct API method calls (set_climatisation_settings, set_climatisation, set_auxiliary_climatisation)
- Add comprehensive error handling and validation
- Implement temperature setting with range validation (15.5-30°C)
- Support HVAC modes (HEAT_COOL, OFF) with proper state management
- Add climate entity icons and extra state attributes
- Implement optimistic updates with coordinator refresh
- Change find_path() logging from ERROR to DEBUG for missing optional paths
-
Terms & Conditions Detection:
- Add TermsAndConditionsError exception
- Detect termsAndConditions page in redirect flow during login
- Prevent retry loops when T&C acceptance is required
- Provide clear error message directing users to accept terms at myvolkswagen.net
🐛 Bug Fixes
- Fix orphaned entity handling for unsupported features
- Improve logging levels to reduce error spam for optional vehicle features
⚠️ Important Notes
Climate control relies on two separate API calls: one to set the target temperature and another to start or stop the climate system.
Due to limitations in Volkswagen’s backend architecture, state changes are not reflected immediately and may take some time to update.
Please note that values are updated only after the corresponding operation has been executed successfully.
For additional details and behavior explanations, refer to the project’s Wiki page.