WashData
A Home Assistant integration that watches an appliance through its smart plug. It detects each cycle, recognises which program ran from the power curve, and tells you how long is left.
Works with washing machines, dryers, washer-dryers, dishwashers, air fryers, bread makers and pumps. Two catch-all types cover the rest: Other (Advanced) (full program matching) and Threshold Device (on/off detection only).
[!CAUTION] Electrical safety. A plug on a washer, dryer or dishwasher carries the full heating load for hours. It must be rated in watts at your mains voltage for the appliance's peak power, often over 2500 W (16 A is 3680 W at 230 V, but 15 A at 120 V is only 1800 W), or use a hardwired module. Cheap or under-rated plugs can overheat and catch fire. Use at your own risk and check the plug regularly. More in Smart plugs.
What you get
- Cycle detection from the power trace, with start, pause and end handled per appliance type.
- Program recognition once you have taught it your programs, plus time remaining, progress and the current phase.
- Energy and cost per cycle, with dynamic tariffs, and a lifetime sensor for the Energy dashboard.
- Notifications: ready-made pushes per event, or your own automations on WashData's events.
- Pause / Resume, door sensor support and a "laundry still inside" reminder.
- A full-screen panel in the sidebar for status, cycles, programs, settings and a what-if Playground.
- Local only. Everything runs inside Home Assistant. The optional Community Store is the only online feature and is off by default.
Install
HACS (recommended): WashData is in the HACS default list.
Click Download, then restart Home Assistant.
Manual: copy custom_components/ha_washdata from the
latest release into your custom_components
folder and restart.
Set up a device
Settings > Devices & Services > Add Integration > WashData, then fill in:
| Field | What to enter |
|---|---|
| Name | e.g. "Washing Machine" |
| Device Type | sets the detection defaults for that kind of appliance |
| Power Sensor | the plug's power entity, in watts |
| Minimum Power | below this the appliance counts as off (default 2 W) |
Everything else is in the WashData panel in the sidebar. Before you start, check your plug reports often enough: see Smart plugs.
Teach it your programs
WashData ships no programs, because every machine is different. Teach it your 2-3 most common ones:
- Record: on the panel's Overview tab, use Manual Recording > Start Recording, run the program, stop the recording, then save it to a profile.
- Or label afterwards: just use the machine. Each run is stored as an unlabelled cycle; open it in Cycles and assign it to a new profile.
After that, matching is automatic. When WashData is not sure, it puts the cycle in the review queue in Cycles (Overview links to it), where you confirm or correct it.
How many profiles? One per program you can tell apart by length or power curve (Quick vs Cotton, wash only vs wash + dry). Programs that differ only in temperature or spin look alike; WashData may mix them up at first and learns from 3-5 corrections. For a washer-dryer, make one profile per wash + dry combination.
Entities
`` is your device name, for example sensor.washing_machine_state.
| Entity | What it shows |
|---|---|
sensor._state |
off, idle, starting, running, paused, user_paused, ending, finished, anti_wrinkle, interrupted, force_stopped, clean, delay_wait, unknown |
binary_sensor._running |
On for the whole cycle, through soaks, pauses and the end wait. Use this for "is it done" automations. |
sensor._program |
The recognised program |
sensor._time_remaining |
Minutes left |
sensor._total_duration |
Elapsed + remaining (good for timer-bar-card) |
sensor._progress |
0-100 %, with projected energy and cost |
sensor._current_phase |
The phase you defined for the program at this point ("Rinse", "Spin"), else unknown |
sensor._cycle_count |
Lifetime runs, for maintenance by count |
sensor._energy_total |
Lifetime kWh, for the Energy dashboard |
sensor._suggested_settings_available |
Number of tuning suggestions waiting in Settings |
binary_sensor._maintenance_due |
On when a maintenance reminder is due |
select._cycle_program |
Pick the program by hand |
button._pause_cycle / _resume_cycle |
Pause and resume a cycle (Pause can also cut the plug's power) |
button._force_end_cycle |
End a stuck cycle |
button._mark_unloaded |
Confirm the load is out (available in clean) |
sensor._pump_runs_today |
Pump devices only: runs in the last 24 h |
State meanings: idle means the display is on between cycles; paused covers quiet spells and a
cycle halted on standby power (sub-state Stalled); user_paused is your own pause; ending is the
wait before WashData calls the end; clean means finished with the load still inside.
Services
| Service | Use |
|---|---|
ha_washdata.pause_cycle / resume_cycle |
e.g. pause during a peak tariff |
ha_washdata.record_start / record_stop |
record a program from a button |
ha_washdata.label_cycle, auto_label_cycles |
label stored cycles |
ha_washdata.mark_unloaded |
confirm the load is out (NFC tag, button) |
ha_washdata.export_config / import_config |
back up or restore one device (administrators) |
action: ha_washdata.record_start
data:
device_id: "washer_device_id"
Assist: ask "Is my washer done?". Copy
docs/custom_sentences/en/ha_washdata.yaml to
/custom_sentences/en/ and restart so Assist knows the phrases.
When something is off
| Problem | Try |
|---|---|
| Cycles start on standby blips | Raise Start Energy (e.g. 2 Wh). |
| A cycle ends during a soak or pause | Raise Off Delay or Min Off Gap above the longest quiet spell in the program. For a soak you start yourself, press Pause. |
| One run is split into two cycles | Raise Min Off Gap above the quiet gap before the tail. |
| Program shows "unknown" | Label a few runs of that program; group near-identical profiles. |
| You want a warning before the end | Set Pre-End Alert. |
Settings show suggestions from your own history, applied only when you click Use or Apply all. What each setting does: Settings guide. Quick answers: FAQ.
Documentation
| Page | Contents |
|---|---|
| Smart plugs | Choosing and configuring the plug |
| FAQ | Short answers to common questions |
| Panel walkthrough | Tour of every tab |
| Settings guide | What each setting does, with graphs |
| Notifications and events | Push options, automations, event payloads |
| Community Store | Adopt or share a setup for your model |
| Export and import | Backup, transfer, undo an import |
| Community projects | Projects that work with WashData |
| How it works | Detection, matching and learning internals |
| WebSocket API | Panel API reference |
| Changelog | Version history |
Questions? Join the Matrix / Element chat or open an issue. Contributing: CONTRIBUTING.md.
Languages
🇦🇱 Shqip • 🇧🇦 Bosanski • 🇧🇬 Български • 🇭🇷 Hrvatski • 🇨🇿 Čeština • 🇩🇰 Dansk • 🇳🇱 Nederlands • 🇬🇧 English • 🇪🇪 Eesti • 🇫🇮 Suomi • 🇫🇷 Français • 🇩🇪 Deutsch • 🇬🇷 Ελληνικά • 🇭🇺 Magyar • 🇮🇸 Íslenska • 🇮🇹 Italiano • 🇯🇵 日本語 • 🇰🇷 한국어 • 🇱🇻 Latviešu • 🇱🇹 Lietuvių • 🇲🇰 Македонски • 🇳🇴 Norsk • 🇵🇱 Polski • 🇵🇹 Português • 🇧🇷 Português (BR) • 🇷🇴 Română • 🇷🇺 Русский • 🇷🇸 Srpski • 🇸🇰 Slovenčina • 🇸🇮 Slovenščina • 🇪🇸 Español • 🇸🇪 Svenska • 🇹🇷 Türkçe • 🇺🇦 Українська • 🇨🇳 简体中文
Translations are community-maintained on GitLocalize.
License
AGPL-3.0-or-later. Free to use, study, modify and share; if others use a modified version over a network, you must offer them its source under the same licence.