Releases: iMicknl/ha-nest-protect
v0.4.0b7
What's changed
Please update as soon as possible. Previous beta release (0.4.0b6) had an issue with the event mechanism resulting in a high load on the Google server and additional bandwidth.
The goal is still to promote the beta release to a new stable release, but due to time constraints on my side, I haven't been able to fix all the bugs yet in the new version using cookie authentication.
Beta release
In October 2022 Google did kill the old authentication method that this integration uses. New users need to use a (hard to use) cookie method. This beta release adds support for the cookie authentication.
Please log an issue on GitHub when you face any issues.
v0.4.0b5
What's changed
Beta release
In October 2022 Google did kill the old authentication method that this integration uses. New users need to use a (hard to use) cookie method. This beta release adds support for the cookie authentication.
Please log an issue on GitHub when you face any issues.
v0.4.0b4
What's changed
Beta release
In October 2022 Google did kill the old authentication method that this integration uses. New users need to use a (hard to use) cookie method. This beta release adds support for the cookie authentication.
Please log an issue on GitHub when you face any issues.
v0.4.0b3
What's changed
Beta release
In October 2022 Google did kill the old authentication method that this integration uses. New users need to use a (hard to use) cookie method. This beta release adds support for the cookie authentication.
Please log an issue on GitHub when you face any issues.
v0.4.0b2
What's changed
Beta release
In October 2022 Google did kill the old authentication method that this integration uses. New users need to use a (hard to use) cookie method. This beta release adds support for the cookie authentication.
Please log an issue on GitHub when you face any issues.
v0.4.0b1
What's changed
Beta release
In October 2022 Google did kill the old authentication method that this integration uses. New users need to use a (hard to use) cookie method. This beta release adds support for the cookie authentication.
Please log an issue on GitHub when you face any issues.
Contributors to this release
v0.3.12
What's changed
This is a small maintenance update.
Please note that since Nest has changed authentication, multiple issues have been reported which you can read more about here. This update does not fix this, there will be a pre-release on GitHub soon that will switch the authentication.
- Bump actions/setup-python from 2 to 4 (#172) @dependabot
- Add Portuguese translation (pt-pt) (#191) @ViPeR5000
🐛 Bug Fixes
Contributors to this release
@ViPeR5000, @dependabot, @dependabot[bot] and @iMicknl
v0.3.11
What's changed
This update will fix issues with an upcoming Home Assistant version, due to breaking changes in core.
Please note that since Nest has changed authentication, multiple issues have been reported which you can read more about here. This update does not fix this.
✨ Enhancement
- Add boilerplate async_remove_config_entry_device so users can remove dead devices. (#134) @tomwilkie
- Use async_forward_entry_setups function (#135) @RobertD502
- Bump actions/checkout from 2 to 3 (#138) @dependabot
- Bump TimonVS/pr-labeler-action from 3 to 4 (#139) @dependabot
- Bump requirements to 2023.1.7 (latest HA) and CI/CD maintenance (#137) @iMicknl
Contributors to this release
@RobertD502, @dependabot, @dependabot[bot], @iMicknl and @tomwilkie
v0.3.10
What's changed
This update will fix issues with Home Assistant 2022.11 version, due to a breaking change in core.
Please note that since Nest has changed authentication, multiple issues have been reported which you can read more about here. This update does not fix this.
🐛 Bug Fixes
- Need for minor version number (add .0) (#113) @markvader
Contributors to this release
v0.3.9
What's changed
This update will fix issues with the (soon to be released) Home Assistant 2022.11 version, due to a breaking change in core.
Please note that since Nest has changed authentication, multiple issues have been reported which you can read more about here. This update does not fix this.