Releases: ad-ha/mg-saic-ha
0.7.0
All breaking changes are marked with 🚩
WHAT'S NEW
-
Revise backend code to re-login if authentication token expired
- Useful if you used the app and still want HA to get updated data.
-
Refactor update intervals schedule and internal management update (closes #50) (hope it closes #48)
-
Added new Update Interval for Powered On vehicle (default 15 minutes)
-
Added Last Key Seen sensor (from #47)
-
Added Last Update Time sensor (closes #49)
- This sensor will show the time elapsed since the last successful data update
WHAT'S CHANGED
-
Refactor AC and Climate Commands (from #47)
-
Fix Rear Window Defrost (from #47) 🚩
- This has been transformed into a switch.
- Now with possibility to turn on and off, with updated status
-
Change Front Defrost from button to switch 🚩
- Now with possibility to turn on and off, with updated status
-
Move "Open Boot" button to Lock, to avoid accidental calls. (from #47) 🚩
- This only works to unlock. Lock has to be done manually on the vehicle, as the API do not allow for boot closure.
-
Rename Battery Voltage to Ancillary Battery Voltage (from #47)
BACKEND CHANGES
- Revise code and sort classes alphabetically, for better understanding, and breakdown by data type (status, charging, etc..)
- Reorganize and refactor some code sections to improve handling and performance
- Update EN and ES translation files
Dev's Notes
Thank you all, once again, for your support and patience with the development of this integration.
I hope that this version is able to solve a lot of the issues reported and addresses some of the needs/improvements identified by all of you. I tried on this occasion to bring forward everything that was outstanding in issues and also make some improvements to the whole integration, which I hope translates into a easier usage for all of you.
If you have any issues or improvement suggestions, do not hesitate to provide your feedback here: ISSUES
Full Changelog: 0.6.2...0.7.0
0.6.2
0.6.1
0.6.0
What's Changed
- Reorganize Sensor definitions
- Revise Electric Range sensor. Obtain data from Charging Data with fallback on Vehicle Status (closes #41)
- Added Sensors:
- Total Battery Capacity
- Power Mode
- Added Binary Sensors:
- Engine Status
- Dipped Beam Status
- Main Beam Status
- Side Lights Status
- Wheel Tyre Monitor Status
Full Changelog: 0.5.2...0.6.0
0.5.2
What's Changed
- Fix vehicle type being override automatically
- Add new services and switches:
- Sunroof
- Charging Port Lock
- Update translations
- Minor fixes
Full Changelog: 0.5.1...0.5.2
0.5.1
What's Changed
- Fix vehicle type being override automatically. Get vehicle type defined in config flow.
Full Changelog: 0.5.0...0.5.1
0.5.0
What's Changed
- Refactor API data access. Build access blocks for Info, Status and Charging Data and separate failsafe updates.
- Redefined retry mechanisms. Each dataset is now accessed and retried separately.
- Refactor and separate sensors and entities setup and updates by dataset.
- Failsafe start. All sensors and entities shall be created and wait for updates, even if data is not available.
- Failsafe start exception to Basic Vehicle Info, which will result on integration not being deployed on first setup..
- Revise GPS sensor setup and update
Dev's Notes
First of all, thank you for your support and patience with the development of this integration. It's quite challenging to build something from scratch and getting it working properly for everyone, at least the best way possible, whilst coping with data from MG.
I hope that this version is able to solve a lot of the issues for some of the users, being the most important the "Generic Responses". On this matter, I've heard from MG Europe that, acknowledging their actual limitations on software and vehicles' SIM cards, they are working on a way to get data faster and reliably from the vehicles. Let's see when they do come up with a solution for this.
In the meanwhile, I tried to establish a ladder setup process, with several retries, to try to force data update from vehicles and get this to work as smooth as possible.
If you have any issues or suggestions, do not hesitate to provide your feedback here: https://github.com/ad-ha/mg-saic-ha/issues/new/choose
0.4.8
What's Changed
- Revise initial setup process and handling of generic responses.
- Limit maximum duration of retries under constant generic responses situation.
- Add missing country codes to Phone Login on configuration process.
Dev's Notes
I am hoping that this solves the issues with integration setup. I cannot fully test it as I do not get to the limit of generic responses to check if the setup fails or not. In theory, the way I see it, it should work.
If this do not work, please be patient with me and we can work together to find a fix and get it around.
The issue with Generic Responses in on MG's end and I cannot do anything, but I am willing to try to get this working despite those issues.
Should you find any more issue, please get them documented in here: https://github.com/ad-ha/mg-saic-ha/issues
Should you wish to cooperate on the development of the integration, please feel free to submit any PR that you find needed.
Thank you all.
Full Changelog: 0.4.7...0.4.8
0.4.8-a2
Full Changelog: 0.4.8-a1...0.4.8-a2
0.4.8-a1
Testing version to address generic responses on integration setup.
Be careful! If your integration is working fine, do not install this version
What's New
- Adjust Coordinator retry obtaining data, exhausting maximum retries defined, when API responds with Generic Data.
- If valid data fails to be obtained on a given response, setup sensors and set state to
None. - Parse partial valid data to the sensors that can get available data.
- If data fails to be obtained on initial setup, retry at defined Update Intervals.
Full Changelog: 0.4.7...0.4.8-a1