Skip to content

fix(dashboard): decode vacuum-extend diagnostics values#30

Merged
dacrypt merged 1 commit into
mainfrom
fix/dashboard-vacuum-extend-value-decoding-20260526
May 26, 2026
Merged

fix(dashboard): decode vacuum-extend diagnostics values#30
dacrypt merged 1 commit into
mainfrom
fix/dashboard-vacuum-extend-value-decoding-20260526

Conversation

@dacrypt
Copy link
Copy Markdown
Owner

@dacrypt dacrypt commented May 26, 2026

Summary

  • decode the known X20+ vacuum-extend enum-backed diagnostics tiles into human labels in Mission Control
  • preserve the raw siid 4 values beside each decoded label for debugging
  • bump version/changelog/backlog for the shipped patch release

User value

Mission Control no longer makes users mentally translate raw diagnostics values like 0, 1, or 3 for cleaning mode, mop mode, waterbox status, resume-after-charge, and carpet boost.

Research basis

  • official xiaomi.vacuum.c102gl MIoT/OpenHAB mappings confirm cleaning-mode = Quiet/Standard/Medium/Strong and mop-mode = Low/Medium/High
  • the same sources confirm waterbox-status = No/Yes and both break-point-restart + carpet-press = Close/Open
  • hass-xiaomi-miot issue #2767 still keeps room-cleaning changes in the higher-risk bucket, so this stays in the safe diagnostics/UI lane

Tests

  • added a dashboard regression that failed before the new enum formatter/mappings existed
  • ran:
    • .venv/bin/python -m pytest tests/ -v
    • .venv/bin/ruff check src/ tests/
    • .venv/bin/ruff format --check src/ tests/
    • .venv/bin/mypy src/xiao/

Risk

Low: frontend-only formatting change for existing diagnostics values; raw values remain visible and task-status stays untouched.

@dacrypt dacrypt merged commit c2d5925 into main May 26, 2026
4 checks passed
@dacrypt dacrypt deleted the fix/dashboard-vacuum-extend-value-decoding-20260526 branch May 26, 2026 07:07
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.

1 participant