Home Assistant

Hold appliances until off-peak power hours

A power-monitoring plug pauses a dishwasher, dehumidifier, or trickle charger that starts outside cheap hours, restores power when the window opens, and flags a cycle that ends too soon or never starts.

Difficulty · IntermediateSetup · 30–60 minutesHA · 2024.10 or newer
Get the pack · from $19Have us set it up

Some hardware links on this page are affiliate links. As an Amazon Associate I earn from qualifying purchases. We may earn a commission if you buy through them, at no extra cost to you. See the affiliate disclosure.

A dishwasher started at 6 pm runs on the expensive rate even when the cheap window starts at 11. This blueprint watches the plug’s watts. If a cycle tries to start outside the window, it turns the plug off, remembers that it is waiting, and sends a notification with a Run now button. When the window opens, it turns the plug back on. When the watts stay low again, the cycle is done. If the cycle dies too quickly, or the watts never come back after power is restored, the phase goes to error so you know to check the appliance.

The phase lives in an input_select: idle, waiting_for_window, running, error.

Washer and dryer done alerts, which are a different job, are laundry handoff reminders. A machine that should turn off because it was left on, rather than because of the tariff, is coffee machine left-on reminder. The Run now button uses the same Companion action pattern as actionable notification reply.

What problem it solves

You want a plug-in appliance to wait for cheap power, to finish the cycle once it has started, and to tell you when the restart after a power cut did not work.

How it works

  1. Start. Power crossing the start threshold (default 15 W) while the phase is idle or error means something is trying to run. Inside the window, the phase becomes running and the plug stays on. Outside the window, the plug turns off, the phase becomes waiting_for_window, and the notification offers Run now.
  2. The window. Turn on “Use a schedule entity” and pick a schedule that is on during cheap hours. Leave that switch off to use a start time and an end time instead (default 23:00 to 07:00, through midnight). A clock window and a schedule are not combined. The one you did not pick is ignored.
  3. Restore. When the window opens, or you tap Run now, or Home Assistant starts and the window is already open, a waiting_for_window phase turns the plug on, sets running, stamps the start time, and starts the grace timer (default 5 minutes).
  4. It actually started. If power crosses the start threshold while running, the grace timer is cancelled. If the timer finishes and power is still under the start threshold, the phase becomes error. The plug stays on so you can press the button on the appliance.
  5. Done. Power under the finish threshold (default 5 W) for N minutes (default 3), while running, ends the cycle. If that happened sooner than the minimum runtime (default 10 minutes, 0 disables the check), the phase is error. Otherwise it returns to idle. The plug is left on. The next start is another power rise.
  6. Reset. The input button sets idle, cancels the grace timer, and turns the plug on. A later power rise is treated as a new start, including another wait if you are still outside the window.

A cycle already running is not cut off when the window ends. The window only gates the start.

Safety note

Cutting power is how the wait works. Many dishwashers, washers, and dehumidifiers do not resume when power returns. They sit there until someone presses start. Read the grace error before you trust this on an appliance you cannot see. This is not a safety disconnect. The plug can fail closed. Do not use it in place of a listed shutoff, and do not put it on medical equipment or on a load past the plug’s rating.

Snippet

The phase helper and the two power triggers are the core. Window, thresholds, and the notification are inputs.

triggers:
  - trigger: numeric_state
    entity_id: !input power_sensor
    above: !input start_watts
    id: power_up
  - trigger: numeric_state
    entity_id: !input power_sensor
    below: !input finish_watts
    for:
      minutes: !input finish_minutes
    id: finished

Run now is an actionable notification. The action name defaults to APPLIANCE_RUN_NOW. Change it if you import the blueprint for a second appliance.

Setup outline

  1. Copy helpers/appliance_off_peak.yaml into config/packages/ and restart. Confirm the select, the datetime, the timer, and the reset button.
  2. Copy blueprints/automation/appliance_off_peak_guard.yaml into config/blueprints/automation/edotdev/ and reload blueprints.
  3. Create the automation. Pick the plug switch and the watt sensor. Leave the helper inputs on the defaults unless you renamed them.
  4. Either create a schedule that is on during cheap hours and enable “Use a schedule entity”, or set the start and end times and leave the schedule switch off.
  5. Set the start threshold above the appliance’s idle watts and below a real running draw. Set the finish threshold between idle and running. If idle is already 8 W, both defaults are wrong for that plug.
  6. With the phase at idle, start the appliance outside the window. The plug should turn off and the notification should appear. Tap Run now, or wait for the window. The plug should come back. If the appliance needs a button press, press it before the grace timer ends. When the cycle finishes, the phase should return to idle.

Troubleshooting

  • The plug never turns off. The start threshold is above what the appliance draws, the phase is already running or waiting_for_window, or you are inside the window. Read the watt sensor and the select. Reset to idle and try again outside the window.
  • It turns off and never restores. The schedule is off when you think it is on, or the clock window is backwards. A start of 07:00 and an end of 23:00 is daytime, not overnight. Overnight is a start later than the end. Run now should still restore. If the button does nothing, the phone notify service is not the Companion app, or the action name on the notification does not match the blueprint input.
  • Error as soon as power returns. The appliance did not resume, so watts stayed under the start threshold until the grace timer finished. Press start on the appliance, then press the reset button (or let a later power rise inside the window move error back to running).
  • Error on a normal short cycle. The minimum runtime is longer than this appliance runs. Set it to 0 to disable that check, or lower it.
  • The cycle never reaches idle. Finish threshold is below the idle watts, so “below for N minutes” never happens. Raise the finish threshold, or check that the plug reports something near 0 W when the appliance is done.
  • A second appliance steals Run now. Both automations listen for the same action name. Give each one its own action name.
  • Reset starts another wait immediately. Reset turns the plug on. If the appliance resumes and you are outside the window, a new start is supposed to wait again.

Credits

The four phases and the failed-start checks follow Appliance Orchestrator Pro. This pack is a single blueprint and a helper file for one plug.

Changelog

v1.0 · Nov 1, 2026: First publish.