Skip to content

Conversation

@agners
Copy link
Member

@agners agners commented Aug 4, 2025

Proposed change

This avoids that we display a 10% life time use for a brand new eMMC storage. The values are estimates anyways, and there is a separate value which represents life time completely used (100%).

For a detailed description of the eMMC life time used meaning see #2413 (comment).

Related to home-assistant/frontend#26379.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (which adds functionality to the supervisor)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to cli pull request:
  • Link to client library pull request:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • The code has been formatted using Ruff (ruff format supervisor tests)
  • Tests have been added to verify that the new code works.

If API endpoints or add-on configuration are added/changed:

This avoids that we display a 10% life time use for a brand new
eMMC storage. The values are estimates anyways, and there is a
separate value which represents life time completely used (100%).
@agners agners force-pushed the return-optimistic-life-time-estimate branch from 7545a7a to 70709b4 Compare August 4, 2025 15:16
@agners agners merged commit f150d1b into main Aug 5, 2025
23 checks passed
@agners agners deleted the return-optimistic-life-time-estimate branch August 5, 2025 08:43
@github-actions github-actions bot locked and limited conversation to collaborators Aug 7, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants