Short Answer: Check the Sensor Type, the Metadata, and the Statistics

Start with the field you are trying to fill, then inspect the sensor. Do not change its unit just to make it appear. If the field needs energy and your device already reports kWh, check that existing reading first. If you only have power in W or kW, the Integral helper can estimate energy over time.

Researched from Home Assistant documentation, checked September 15, 2026. The calculation below is a worked example, not a measured smart-plug test. Hardware reporting intervals and missing readings can affect the result.

Tara's energy rule: get one clean source working end to end before you build tariffs, summed templates, or a whole-house math project around it.

First Filter: Energy Dashboard Is Picky on Purpose

Open Settings > Tools > States and find the entity ID, such as sensor.desk_plug_energy. Older releases place States and Statistics under Developer Tools. The labels beside the reading are its metadata: they tell Home Assistant what the number means.

Compare those labels with the official Energy sensor checklist:

  • The entity must be in the sensor domain.
  • The device_class must match the kind of source you are adding.
  • The state_class must match whether the entity is power or accumulated usage.
  • The unit must be one the target field accepts, and units with exponents must match exactly.
  • The entity must not have statistics errors.

For electricity-related sources, the FAQ says device_class must be energy or power. It also says state_class must be measurement for power sensors and total or total_increasing for the rest. If any of that metadata is wrong, Energy Dashboard is doing the right thing by filtering the entity out.

What your source reports What it means Usual next step
W or kW Live power right now Use directly in a compatible power field; use Integral if you need accumulated energy and have no native energy sensor
Wh or kWh Accumulated energy usage or production Verify device class, state class, units, and statistics
A Electrical current, not power or energy Find a real-power reading in W or kW first; do not relabel amps or integrate them as kWh
An increasing energy counter that resets Usage accumulated since a restart or reset Check that its state class correctly represents the counter; a reset alone does not require another helper

The Most Common Problem: You Have Power, Not Energy

This is the trap that wastes the most time. A lot of hardware reports power in watts. Energy Dashboard often wants energy in watt-hours or kilowatt-hours. The official Energy FAQ leads with that distinction for a reason.

Home Assistant's Individual devices documentation says that if a device exposes a power sensor in watts, you can use the Integration (Riemann sum integral) helper to calculate energy usage and then use that resulting sensor in Energy Dashboard. The Integral documentation adds two details that matter in practice: the helper keeps its value across Home Assistant restarts, and a source with more frequent updates produces more accurate totals.

For a source in W and an energy field that needs kWh, use this setup:

  1. Confirm that the original power sensor has a numeric reading in W, not A, unknown, or unavailable.
  2. Open Settings > Devices & services > Helpers > Create helper > Integral. Select that power sensor.
  3. Set the metric prefix to k and time unit to h. If your source already reports kW, use no metric prefix with hours instead.
  4. For a steady on/off load, consider the left method. For smoothly varying, frequently reported power, compare the documented methods before choosing.
  5. Check the resulting energy sensor's unit and statistics, then select it in the accumulated-energy field. Leave the original watts sensor available for live-power uses.

Worked example: a constant 100 W load running for two hours uses 100 × 2 / 1000 = 0.2 kWh. Compare the helper's increase, not its lifetime total, over that interval. A factor-of-1,000 mismatch is a reason to recheck source units and prefix; do not alter historical statistics before finding the cause.

For a source that stays unchanged for long periods, Integral's maximum sub-interval can keep the estimate updating between state changes. It cannot reconstruct missing measurements. Prefer a trustworthy native energy counter when available.

Five Fix Paths That Solve Most Cases

1. Your device already reports kWh, but it still does not appear

Inspect its reading in States, then open Statistics under Settings > Tools (Developer Tools on older releases). Resolve any reported unit or statistics problem using the offered repair. A live number alone does not prove the historical data is usable. Do not delete statistics as a first troubleshooting step.

If the integration is the thing exposing wrong metadata, Home Assistant's FAQ says to open an issue against that integration. Practically, you can still unblock yourself with a template or helper in the meantime, but that workaround should not hide the underlying integration defect.

2. You have power, or only current in amps

For watts, follow the Integral setup above when you need energy. For amps, first look for a meter-reported real-power sensor in W or kW. Current alone does not establish real power for an AC appliance; do not assume a fixed voltage makes the conversion accurate for every load. Integrating amps produces amp-hours, not kilowatt-hours.

A different task may need the original watts reading: a washing-machine finished notification looks for a drop in live power, not the accumulated kWh total.

3. The source resets, goes negative, or only gives deltas

A correctly classified total_increasing energy counter can reset: Home Assistant's statistics account for a new counter cycle. A reset alone does not require Utility Meter. Check the sensor state-class rules; a net total that legitimately rises and falls is not the same as an increasing consumption counter.

If you need Utility Meter, match its settings to the actual source: delta values for increments since the previous reading, net consumption for signed consumption, and periodically resetting for a source counter that resets. Do not turn every option on as a general repair. The Utility Meter documentation explains these separate cases.

4. You need peak, off-peak, daily, or monthly numbers

The Utility Meter helper is also the official answer for tariff and billing-cycle logic. Its docs explain that it tracks a source sensor and resets on a configured cycle, while tariffs let you split consumption across time-of-use schedules. If you are trying to force all of that into one heroic template sensor, you are usually skipping the helper that Home Assistant already built for the job.

The first cycle is incomplete because it starts when you create the helper. The next cycle can cover a full period, but it is not automatically accurate: missing readings and incorrect configuration still matter.

5. You built a template or summed sensor

Template and summed sensors can work, but they need the same metadata discipline as native entities. A 2023 forum thread about ESP-based template sensors and the Utility Meter docs themselves both reinforce the point: give the new sensor the correct device class and units, and make sure the template returns a real numeric value instead of occasional junk.

The Utility Meter docs even show summed template examples that first verify values with is_number() before adding them together. That is the right instinct. A mathematically elegant template is not useful if it occasionally emits a non-numeric state and poisons the statistics stream.

Do not simply sum counters that reset independently into one increasing counter. A single device resetting can look like the combined counter reset. The Energy FAQ recommends adding those individual energy sources separately instead.

Do not stack helpers blindly. First decide whether you are fixing power vs energy, resets vs totals, or billing-cycle splits. Each problem points to a different helper.

What Changed in 2026, and What Did Not

The 2026.2 release is worth knowing because it removed some old workaround patterns. Home Assistant says that release can now use more power-sensor formats directly in Energy Dashboard for grid or battery scenarios, including a single inverted sensor or two separate positive sensors for import/export or charge/discharge. If your setup matches that exact case, you may not need a template sensor anymore.

But that improvement did not erase the base rules from the Energy FAQ. You still need the right entity type, the right metadata, and clean statistics.

The 2026.6 release added two more Energy Dashboard quality-of-life features: battery state-of-charge sensors and custom source names. Those make multi-source homes easier to read, but again, they do not change the selection rules.

There is one more practical reason not to overreact when something looks strange after an update: sometimes the problem is version-specific UI behavior, not your data model. For example, a GitHub issue opened on April 4, 2026 reported missing Home load configuration fields in 2026.4.1. That is not proof that Energy Dashboard is broadly unreliable. It is a reminder that when an entire configuration area disappears after a release, you should search current issues before rebuilding all your sensors from scratch.

One Weird Picker: Upstream Devices Want a Device, Not Just an Entity

This is more niche, but it catches people. A December 7, 2025 Home Assistant Community thread described a template power sensor that worked in Developer Tools but could not be selected as an upstream device in Energy Dashboard. The answer there was that the upstream selector works at the device level, not just the entity level.

So if your helper sensor is valid for Energy tracking but still fails in an upstream-device picker, that does not automatically mean the energy math is wrong. It may mean that specific view expects the entity to be attached to a device in a way your loose helper is not.

A Simple Start That Works for Most Homes

The calmest path is usually much less ambitious than people imagine.

  1. Get one main meter source or one trustworthy plug working first.
  2. Verify the entity metadata in Developer Tools.
  3. Fix any statistics issues before adding more layers.
  4. If the source is only power, create an Integral helper.
  5. Add Utility Meter only if you need periods, tariffs, or a supported source conversion.
  6. Only then add tariffs, solar, battery, and per-device summaries.

That order matters. The people who get stuck hardest are usually the ones trying to solve import/export polarity, peak/off-peak billing, custom templates, and device hierarchies before they have one clean sensor showing up reliably.

Tara's Take

For a real house, the goal of Energy Dashboard is not to win a YAML contest. It is to answer useful questions reliably: what the house uses, what a few expensive devices cost, whether solar is actually offsetting the load, and whether the data stays understandable when someone revisits it six months later.

The Tara version is to keep the stack local, stable, and legible: supported hardware, one or two clean helpers where they actually matter, and no mystery templates that only one person in the household can debug.

If the sensor now appears but its totals do not match your statement, continue with why Home Assistant energy totals differ from a utility bill. That is a different diagnosis from a missing sensor.

FAQ

Why does my watts sensor not show up in Energy Dashboard?

Match the field you are configuring. A power field accepts a suitable W or kW power sensor; an accumulated-energy field needs energy such as kWh. Use Integral only when you need energy and have no suitable energy sensor. Amps measure current, not power, and cannot be converted to kWh with Integral alone.

Should my energy sensor use total or total_increasing?

Energy supports total or total_increasing, but the choice must describe the meter. An increasing usage counter that can reset is a total_increasing case; a net total that can legitimately fall needs different handling. Do not change the class simply to make a sensor appear. Power uses measurement.

Can I use manual readings or sensors that reset?

A correctly classified total_increasing energy sensor can already handle counter resets in statistics; a reset alone does not require Utility Meter. Use Utility Meter for configured periods, tariffs or supported source conversions. A manual input_number is not itself a sensor entity and does not qualify directly.

Why does a helper entity work in one Energy screen but not as an upstream device?

Because the upstream selector is device-oriented. A valid helper sensor can still fail there if it is not attached to a device in the way that picker expects.

Why does my new Utility Meter sensor look wrong today?

The first cycle starts partway through the period, so it is incomplete. The next cycle can cover a full period, but accuracy still depends on the source readings and configuration.