Note that the component still doesn't work properly under 2024.5; see #326 .
Description
Checklist
[x] The PR title is clear, concise and follows conventional commit formatting.
[x] Double-check your branch is based on develop and targets develop
[ ] Issue raised to compliment this PR (if no pre-existing issue exists)
[x] Code is commented, particularly in hard-to-understand areas and relevant issues are referenced.
[x] Documentation repository updated to reflect new features or changes in behaviour (VERY IMPORTANT, undocumented features cannot be discovered and used!)
[x] Description explains the issue/use-case resolved and auto-closes related issues.
[x] Breaking changes or changes in behaviour are called out and discussed in separate issues.
[x] Testing of new changes completed by person who raised the issue.
Please open an issue before embarking on any significant pull request, especially those that add a new library or change existing tests, otherwise you risk spending a lot of time working on something that might not end up being merged into the project.
License
By submitting a patch, you agree to allow the project owners to license your work under the terms of the project license. Thank you for contributing!
Throws warnings in 2024.5+
See https://developers.home-assistant.io/blog/2024/04/13/deprecate_async_track_state_change/
Note that the component still doesn't work properly under 2024.5; see #326 .
Description
Checklist
conventional commit
formatting.develop
and targetsdevelop
Please open an issue before embarking on any significant pull request, especially those that add a new library or change existing tests, otherwise you risk spending a lot of time working on something that might not end up being merged into the project.
License
By submitting a patch, you agree to allow the project owners to license your work under the terms of the project license. Thank you for contributing!
Related Issues
Closes