v0.2.0
Release Notes — v0.2.0 (2025-12-21)
-
New: End-of-cycle feedback prompt (Learning UX)
- Cycle verification now reliably triggers at cycle end (feedback request happens before match state is cleared).
- Emits
ha_washdata_feedback_requestedand creates a persistent notification so users actually see the prompt. - Ensures a stable
cycle_idexists for feedback submission, even if storage write fails.
-
Improved: Feedback submission service UX
- Added full Developer Tools schema for
ha_washdata.submit_cycle_feedbackincustom_components/ha_washdata/services.yaml(proper fields + selectors). - Service handler now accepts
device_id(recommended) orentry_id(advanced); derivesentry_idautomatically from the device registry whendevice_idis provided. - Best-effort dismisses the feedback notification after successful submission and rebuilds the relevant profile envelope so future matching benefits.
- Added full Developer Tools schema for
-
Internal: Safer storage + typing/refactors
- Refactored
ProfileStoreand learning-related paths for improved type safety and safer access patterns. - Hardened config/migration defaults and aligned config entry migration target to version 3.
- Misc cleanup across manager/detector/config flow/diagnostics/sensor and updated unit tests.
- Refactored
-
Docs: Broader appliance applicability
- Documentation now clearly states the integration is suitable for washers and also dryers/dishwashers with predictable cycles.
- Updated guidance in docs/devtools text to match the new feedback workflow and recommended
device_idusage.
-
Maintenance
custom_components/ha_washdata/manifest.jsonupdated with corrected integration name/version (0.2.0).- Tests remain green (
pytest: 20 passed).