If a power sensor shows how consumption changes during a wash, Home Assistant can send a message after the reading drops and stays low. First check a full cycle: a short pause and a finished programme can look alike.
Detecting the end of a wash
A washing machine changes its power use as it heats water, turns the drum, drains, and pauses between stages. One brief drop does not prove the programme has finished.
A useful pattern watches for two changes:
- Power rises above a chosen threshold, indicating that a cycle has started.
- Later, power falls below a second threshold and stays there for a set duration; Home Assistant can then send a notification.
Home Assistant can start an automation when a numeric value crosses a threshold and wait for it to remain within a range. The thresholds and durations in the YAML below are syntax examples; choose values from your machine's history. See the official documentation for numeric state triggers and the Power integration.
What the power sensor needs to provide
Use a sensor that reports current power in W or kW to Home Assistant. A cumulative energy reading in kWh does not by itself show whether the machine is running; an instantaneous power reading is more useful for that.
Open the sensor history and record one full cycle, from start to finish. Note the reading at idle, during active washing, through the longest pauses, and after the programme ends. Different programmes, water temperature, and load can change the graph.
Check that the sensor state is numeric and updates. If it often becomes unknown or unavailable, fix the integration or connection first. The automation cannot reliably interpret a missing reading as low power. History also depends on how often the device reports measurements.
An automation example with a duration
Create an automation under Settings → Automations & scenes. The visual editor lets you select the sensor, threshold, duration, and notification action without writing YAML. If you prefer YAML, adapt this example:
alias: Washing machine finished notification
description: Example only. Choose thresholds and duration from your machine's history.
triggers:
- trigger: numeric_state
entity_id: sensor.washer_power
above: 10
for: "00:01:00"
conditions: []
actions:
- wait_for_trigger:
- trigger: numeric_state
entity_id: sensor.washer_power
below: 4
for: "00:10:00"
timeout: "06:00:00"
continue_on_timeout: false
- action: notify.mobile_app_your_phone
data:
title: Washing is done
message: Check the washing machine.
mode: single
Replace sensor.washer_power with your entity ID and notify.mobile_app_your_phone with the mobile app action available in your system. The above: 10 and below: 4 values only show the direction of the thresholds; do not copy them without checking your readings. The one-minute and ten-minute durations are examples too.
The first trigger fires when power crosses above the upper threshold and stays there. The wait action starts after that. When the reading later falls below the lower threshold and remains there, Home Assistant sends the message. The timeout ends an unusually long wait without sending a notification.
If you enable the automation while the washer is already above the upper threshold, no crossing occurs; it will wait for the next one. Enable it before starting the first test cycle. After changing thresholds, inspect the automation trace to see which trigger and action ran.
Avoid treating a pause as the end
Set the low-power duration longer than the pauses you observed on the graph. If the drum can stop for several minutes, a shorter duration can send a false message. Check more than one programme or increase the duration when pauses vary.
There is no universal duration. A longer wait filters longer pauses but delays the notification. If a pause can exceed your chosen duration, power alone may not tell a pause from a finished cycle. If the appliance exposes a programme-status sensor, use it as a more direct end signal and keep power as a cross-check.
Do not pick the upper threshold from one isolated peak. It should distinguish a running cycle from standby while still detecting the programme you use. If power does not fall below your chosen level after the cycle, adjust the lower threshold using the graph instead of guessing a longer wait.
Avoid repeated messages
The sequence “power rises → wait for a sustained drop → send a message” usually sends one notification per start. single mode does not start another copy of the same automation while the current one is waiting. See automation modes.
If messages repeat, inspect the trace and make sure only one path can send them. Avoid adding a second “power below threshold” trigger alongside the sequence: each crossing could create another run. Also check that you do not have a duplicate automation.
A Home Assistant restart interrupts a running automation and clears an unfinished wait. This simple example can miss the notification if the server restarts near the end of a cycle. A restart-resilient design needs to save the cycle state and check it after Home Assistant starts; that is a separate design to test on the specific installation.
Is a smart plug suitable for a washing machine?
Measuring power and switching a plug on or off are separate functions. This notification only needs readings. Do not use it to cut power to the washing machine during a programme.
Before connecting a plug, check all of the following:
- The maximum current and power on the washing machine and the plug.
- The plug manufacturer's limits for motors and sustained loads.
- Grounding, contact quality, and allowed installation conditions.
- Whether the washer manufacturer permits use of an external smart plug.
The printed rating is not the only criterion; follow the manufacturer's load conditions for motor-driven equipment. Do not put the plug in series with an extension lead or adapter, and keep the washer's normal controls available. If the documentation does not confirm that the plug is suitable for this load, choose another measurement method or consult a qualified professional. This article does not report a physical test of any plug or washing machine.
Check and troubleshoot the automation
Observe several full cycles and compare the notifications with the end time before relying on the message. Keep automatic switching off.
| Symptom | What to check |
|---|---|
| The automation does not start | The sensor is numeric; the automation is enabled; the washer crossed the upper threshold after it was enabled |
| The message arrives during a wash | How long the pause lasted and whether the duration is longer than that pause |
| No message arrives after a cycle | Whether power fell below the lower threshold; timeout, unknown, or unavailable; action in the trace |
| Several messages arrive | A second trigger or duplicate automation; selected run mode |
| The wait disappears after a restart | Home Assistant interrupted the unfinished run; inspect the cycle and make a new controlled check |
This scenario uses readings from one appliance; it is separate from general energy monitoring. For consumption in kWh, see our guide to energy monitoring in Home Assistant. More practical articles are in the home automation guide. Habab Home is our Home Assistant build with a Russian-language interface; see Habab Home.
If you want this notification in your own system, message us about Habab Home and describe the result you want. We will first outline the sensor, threshold, and duration; equipment and automation setup are scoped separately.
Home Assistant and Companion App documentation was checked on October 26, 2026. The text and illustration were prepared with AI assistance; the technical details were checked against official sources. The YAML describes an example, not a tested installation: no washing machine, sensor, plug, or phone delivery was physically tested.
Frequently asked questions
Do I need to buy a smart plug?
No. You need a compatible source of current power readings in Home Assistant. It may be a separate meter or a smart plug, if it is suitable for the load and actually reports readings to your system.
How do I choose the finished threshold?
Check the power graph after a completed programme and during long pauses. The low threshold should be below active readings, while the duration should be longer than pauses that should not count as the end.
Why did the wait not finish after a restart?
Home Assistant stops running automation actions during a restart, including unfinished waits. A restart-resilient design needs to save the cycle state separately.
Can I turn the plug off automatically after the notification?
This example does not. Cutting power during a programme could interrupt it. Keep the washer's normal controls and use the automation to send a message.
Sources
About the service "Home Assistant washing machine finished notification by power usage"
Set up a washing machine finished notification from power readings in Home Assistant. Account for pauses, choose a duration, and check smart plug load limits.