Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update entity with HA 2024.11 #1069

Merged
merged 4 commits into from
Nov 26, 2024
Merged

fix: update entity with HA 2024.11 #1069

merged 4 commits into from
Nov 26, 2024

Conversation

ehendrix23
Copy link
Contributor

@ehendrix23 ehendrix23 commented Nov 25, 2024

With HA 2024.11 a new attribute update_percentage is introduced and attribute in_progress is now set to only return a boolean.
As per Home Assistant development guide for update entity https://developers.home-assistant.io/docs/core/entity/update/ in_progress attribute should only return True or False and not a value on current installation progress.
Attribute update_percentage should be used to return current % of the installation or None.

This PR updates the logic for in_progress attribute to ensure it only returns True or False. New attribute update_percentage is added to show current progress if installing or None if update is not happening.

Breaking Change

  • Home Assistant version 2024.11 is minimum version required.
  • in_progress will not show the % of installation anymore. Note that current version Home Assistant is interpreting the provided number as a boolean and thus just returns True instead of the progress.
  • update_percentage will now show % of update progress.

@ehendrix23 ehendrix23 changed the title fix: in_progress should be a boolean and attribute update_percentage identify progress percentage fix: update entity with HA 2024.11 Nov 25, 2024
@alandtse alandtse merged commit 3367ee5 into alandtse:dev Nov 26, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants