Releases: ad-ha/mg-saic-ha
Releases · ad-ha/mg-saic-ha
0.2.1
What's Changed
- Revised vehicle type identification mechanics and conditions - closes #6
- Added new step to config_flow to allow users to select the correct vehicle type if the integration fails to do so based on API data - closes #6
- Added configuration options to the integration to manually change the update intervals.
- Revised translations
IMPORTANT NOTE
If the integration previously failed to identify correctly your type of vehicle, remove the integration and add it again. During the configuration process you will be able to set the correct vehicle type if the integration fails again to determine the correct value (BEV, PHEV, HEV or ICE). Bear in mind that this selection will affect the sensors being shown on HA.
Full Changelog: 0.2.0...0.2.1
0.2.0
What's Changed
- Revised mechanics for connection with API and data retrieval
- Services testing and adjusting to API requirements
- Renamed and revised sensor data and info
- Revise units for sensors and adapting all sensors to SensorDeviceClass from Home Assistant
- Revise Unique ID generation for all sensors
- Revise Login method to avoid blocking calls during startup
- Improve detection and discard of "Generic Responses" during API setup and updates
- Improve vehicle type detection on integration setup.
Breaking Changes
- Many sensors have been refactored and their unique ID changed, This may cause you to have duplicated sensors upon update.
- It is recommendable that you remove and add this integration again from scratch. All sensors will keep the same entity_id, so once added again any entity reference used on dashboards will be kept.
Full Changelog: 0.1.0...0.2.0
0.1.0
What's Changed
- Refactor code to work with data coordinator
- Revised mechanics for connection with API and data retrieval
- Update saic-python-client-ng requirements to version 0.2.3
- Added new sensors for charging data
- Renamed and revised sensor data and info. Most Unique IDs have changed (see breaking changes)
- Revised config_flow to allow login with phone and email
- Initial implementation of services (some services still not available, but implemented as a proof of concept). Feedback on this will be helpful
- Change update interval to 5 minutes once charging is detected
- Refactor API responses and values as needed. Charging sensors only display data if Charging is Active, otherwise 0 will be displayed
- Fuel Level, Fuel Range, EV State of Charge and Electric Range are vehicle dependent. Add logic to determine the vehicle type and show sensors accordingly.
Breaking Changes
- Many sensors have been refactored and their unique ID changed, This may cause you to have duplicated sensors upon update.
- It is recommendable that you remove and add this integration from scratch,
Full Changelog: 0.0.2...0.1.0
0.0.2
What's Changed
- Revised mechanics for connection with API
- Added new sensors (Brand, Model and MY)
- Rename sensors based on Brand and Model
- Rename sensors to have them grouped by type (windows, doors, tyres...)
- Revise config_flow (login with phone still not working and unavailable)
- Initial trialing for charging details (currently expecting support from API developers to see how to work it out)
Full Changelog: 0.0.1...0.0.2