Fix-2024.7-Recorder-Errors #290
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snuffy2
force-pushed
the
Fix-2024.7-Recorder-Errors
branch
from
12440ec to
03f76dd
Compare
|
See no issues with History with this update. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uses the new
_unrecorded_attributes = frozenset({MATCH_ALL})functionality available with HA 2024.7 instead of recorder_history_prefilterhttps://developers.home-assistant.io/blog/2024/06/22/excluding-state-attributes-from-recording-match-all/
https://developers.home-assistant.io/docs/core/entity#excluding-state-attributes-from-recorder-history
Fixes #289
It would be great if someone who is having the issues could test this as well.
This may not be the best long term solution but should work for now pending: home-assistant/architecture#1106