Energy-monitoring smart plugs in Home Assistant: find your vampire loads

Whole-home monitoring tells you the house used 31 kWh yesterday. A $20–25 plug on the right outlet tells you what — the ancient fridge in the garage, the entertainment stack sipping 38 watts all night, the washer that finished an hour ago. This guide covers where plug-level monitoring earns its keep, which plugs report honestly, how to feed the results into the Energy dashboard, and where the safety lines are.

Published Nov 18, 2026 · Last updated Nov 18, 2026

Start with the jobs, not the gadgets

Plug-level monitoring pays off in three specific jobs. Everything else is dashboard decoration:

Already have whole-home monitoring? Plugs complement it, they don't duplicate it. The panel view (see our whole-home energy hardware guide) finds which circuit; plugs find which device on a shared circuit. If you have neither, start with two or three plugs on your suspects — it is the cheapest education in home energy there is.

Protocols, compared honestly

Wi-Fi with a local API (Shelly-style)

The benchmark plug reports power several times a second, exposes a local API and MQTT, and keeps working if the internet dies — Home Assistant's Shelly integration is local push, no cloud account needed. Downsides: each plug joins your Wi-Fi (fine at five plugs, a consideration at fifty), and per-plug cost is at the higher end. For measurement quality per dollar, this is the class to beat.

Zigbee plugs

Cheaper per unit, sips no Wi-Fi airtime, and most double as Zigbee routers that strengthen your mesh — a real bonus in a big house. Reporting is the variable part: some models report power changes eagerly, others on a lazy interval that smears short cycles, and accuracy at very low wattages is often optimistic. For vampire hunting and done-alerts they are usually fine; for precise per-load accounting, check the specific model's reporting behavior before buying a box of them.

What to ignore

Cloud-only plugs whose energy data lives in a vendor app with no local path into Home Assistant. If HA can't see the watts, the plug is a remote switch with a graph you can't use. Also ignore any plug that reports only cumulative kWh with no live power — done-alerts and vampire baselines both need the live number.

Accuracy: monitoring-grade, on purpose

Set expectations the same way we do for panel monitors in our Energy dashboard guide: plug data is monitoring-grade, not billing-grade. Good plugs land within a percent or two on straightforward loads and drift more on tiny or electrically ugly ones. That precision answers every question in this guide — find the vampire, price the fridge, catch the finished washer. It does not settle an argument with your utility, and a plug that disagrees with your panel monitor by a few percent is normal, not broken.

Feeding the Energy dashboard

  1. Add the plug's integration and confirm you have both a power sensor (W) and an energy sensor (kWh). Power alone cannot join the dashboard.
  2. If only power exists, create a helper: Settings → Devices & Services → Helpers → Integral sensor (Riemann sum, left method) over the power sensor, unit kWh. Give it an hour of runtime before judging the numbers.
  3. Open Settings → Dashboards → Energy → Individual devices and add the energy sensor. It now appears in the dashboard's per-device breakdown alongside anything your panel monitor reports.
  4. For daily/weekly views outside the dashboard, a utility_meter helper over the same energy sensor gives you clean today/this-month entities for automations and cards — and because long-term statistics are what the dashboard actually reads, leave the recorder defaults alone unless you have a reason; statistics survive even if raw history is purged.

The washer-done automation

Two small automations and one helper beat every clever single-automation attempt. A helper (input_boolean.washer_running) remembers "a cycle actually started," so the finish alert can't fire from a plug that was simply idle:

alias: Laundry — washer started
triggers:
  - trigger: numeric_state
    entity_id: sensor.washer_plug_power
    above: 10
    for: "00:01:00"
actions:
  - action: input_boolean.turn_on
    target:
      entity_id: input_boolean.washer_running
mode: single
alias: Laundry — washer finished
description: Power drops to idle for 3 minutes after a real wash cycle
triggers:
  - trigger: numeric_state
    entity_id: sensor.washer_plug_power
    below: 2
    for: "00:03:00"
conditions:
  # Only announce if it actually ran (avoid a ping every idle 3 minutes)
  - condition: numeric_state
    entity_id: sensor.washer_plug_energy_today
    above: 0.05
  - condition: state
    entity_id: input_boolean.washer_running
    state: "on"
actions:
  - action: input_boolean.turn_off
    target:
      entity_id: input_boolean.washer_running
  - action: notify.mobile_app_your_phone
    data:
      title: Washer done
      message: "The wash cycle finished — time to move it to the dryer."
mode: single

Tune the numbers to your machine: the below 2 W for 3 minutes finish test fits most modern washers; an older machine that idles at 4 W needs a threshold above its idle and below its spin draw. Watch the power graph for one real cycle and set both thresholds from the trace, not from a blog post — including this one.

Safety, without fine print

Plugs and monitoring we build on

Prices are editorial and change often; buttons show live prices. Some links may earn a commission at no cost to you — see the disclosure page.

The Shelly is the per-plug recommendation from this guide; the Emporia Vue is there for the other end of the same project — when plug data convinces you the panel view is worth having too, it is the monitor our whole-home hardware guide builds around.

Official documentation and references

Frequently asked questions

How accurate are energy-monitoring smart plugs?

Monitoring-grade, not billing-grade. A good plug (Shelly-class) is typically within a percent or two on resistive loads and a bit looser on small, weird loads like phone chargers — plenty to find a 40 W vampire or prove the old fridge costs $18 a month, not enough to dispute a utility bill. That is the same standard we hold whole-home monitors to elsewhere on this site.

Wi-Fi or Zigbee plugs for energy monitoring?

Wi-Fi plugs with a local API (Shelly is the benchmark) report fast, work without a coordinator, and each plug is its own little web server — great data, more devices on your Wi-Fi. Zigbee plugs keep the load off Wi-Fi, mesh-repeat for your Zigbee network, and are usually cheaper per plug, but reporting intervals and accuracy vary more by brand. Either is fine; pick per location, and don't mix so randomly that future-you can't remember what reports what.

Can I put a smart plug on my washer, dryer or space heater?

Washer: yes, on a plug rated for the load — most washers peak well under a plug's 15 A rating. Electric dryer: no — it is a 240 V appliance, no plug exists for it; monitor it at the panel instead. Space heaters and other resistive heating loads sit at a plug's maximum continuously, which is where cheap plugs fail — use a plug explicitly rated for it, or better, monitor at circuit level and skip the plug.

Why doesn't my plug show up in the Energy dashboard?

The Energy dashboard's individual-devices section needs an energy sensor (kWh) with the right device class and state class — a power sensor (W) alone won't appear. Most integrations provide a matching energy entity; if yours only gives power, create a Riemann-sum integral helper to convert it, wait for statistics to accumulate, then add it under Settings → Dashboards → Energy → Individual devices.

Will a smart plug save money by itself?

No — it measures; you save. The wins come from what the data triggers: finding the always-on load you didn't know about, proving which old appliance to replace, and automations like cutting a vampire strip when the TV is off. Expect the first month of measuring to find one or two loads worth more than the plug cost; after that it is maintenance, not magic.

Related guides