Updated code to new vacuum state property #162
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
property from setting the state property directly
JohNan
approved these changes
Jan 4, 2025
|
Sounds like a good plan. |
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.
As of Home Assistant Core 2025.1, the constants used to return state in
StateVacuumEntityare deprecated and replaced by theVacuumActivityenum; see new vacuum state property. There is a one-year deprecation period, and the constants will stop working from 2026.1.The code has been updated to use the
VacuumActivityenum and set theactivityproperty instead of directly setting thestateproperty, ensuring the integration continues working past 2026.