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

If a sensor will not appear in Home Assistant Energy Dashboard, the practical checklist is short: make sure it is a sensor entity, make sure it has the right device_class, state_class, and unit, make sure it has no statistics errors, and make sure you are feeding Energy Dashboard energy where it expects energy instead of just instantaneous power.

If you only have a watts sensor, the usual fix is to create a kWh sensor with the Integral helper. If the source resets, reports deltas, or needs billing periods or tariffs, the next layer is usually Utility Meter. Most failed Energy Dashboard setups are really one of those two problems.

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.

Why This Question Keeps Coming Up

The demand signal is not hypothetical. Home Assistant Community threads in July 2023, April 2024, and December 2025 all revolve around the same pain: a sensor looks valid in Developer Tools but still does not appear in Energy Dashboard. A Reddit thread from the last year answered the same question by telling the owner to inspect device_class first, which is a clue that the failure pattern is still repeating in the wild.

Official Home Assistant changes also keep drawing more people into the feature. On February 4, 2026, the 2026.2 release added support for more power-sensor formats in Energy Dashboard, including inverted single sensors and paired positive sensors for import/export or charge/discharge. On June 3, 2026, the 2026.6 release added battery state-of-charge support and custom source names. More capability is good. It also means more people are setting up Energy Dashboard for the first time and hitting the same eligibility rules.

Local Home Assistant hub collecting stable device and meter data for energy tracking
Energy tracking works best when the input data is boring: one clear meaning per sensor, stable units, and statistics Home Assistant can trust.

First Filter: Energy Dashboard Is Picky on Purpose

Home Assistant's own Energy FAQ makes this explicit. If a sensor is missing from the selection list, the first thing to check is not the card, not the dashboard, and not your optimism. It is the entity itself.

The official checklist is stricter than many people expect:

  • 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 Create an energy sensor with the Integral helper unless the specific grid or battery field now accepts your power format directly
Wh or kWh Accumulated energy usage or production Verify device class, state class, units, and statistics
Per-sample increments or a counter that resets Not a stable always-rising total Use Utility Meter settings such as delta values, periodically resetting, or net consumption when appropriate

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.

That means the right repair is usually:

  1. Start with the original power sensor.
  2. Create an Integral helper that outputs energy in kWh.
  3. Check the new helper in Developer Tools and Statistics.
  4. Add the new energy sensor, not the original watts sensor, to the relevant Energy Dashboard field.

If the device is mostly a clean on/off load, the Integral docs note that the left method can fit rectangular power behavior better than the default trapezoidal approach. That is not mandatory, but it is a useful detail when you are trying to keep per-device tracking sane for heaters, kettles, or other steady loads.

Five Fix Paths That Solve Most Cases

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

In that case, stop building extra helpers until you inspect the entity itself. Go to Developer Tools and confirm the attributes match the FAQ. Then go to Developer Tools > Statistics and see whether Home Assistant is flagging the entity. A sensor can look alive in States and still be rejected because its statistics are bad.

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 only have watts, amps, or live power

This is the classic smart-plug, CT clamp, or inverter problem. Use the Integral helper. The official docs are explicit: a power sensor can be turned into an energy sensor, and the generated unit can become kWh when the source is W with the right prefix and time base.

Do not assume the original live-power entity should appear everywhere just because the graph looks useful elsewhere in Home Assistant. Energy Dashboard is not a generic dashboard card; it expects specific semantics.

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

This is where Utility Meter matters. Its docs say it can handle utility-style cycles, tariffs, net consumption, delta values, and periodically resetting sources. Those options exist because many real devices do not behave like a perfectly monotonic lifetime counter.

If your source reports increments since the last reading, the Utility Meter docs say to enable delta values. If your source should be allowed to move both positive and negative, use net consumption. If a smart plug resets to zero after a reboot, periodically resetting is the relevant switch.

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.

One operational detail matters here: the Utility Meter docs say the first cycle is incomplete. A new daily sensor becomes accurate the next day, and a monthly one becomes accurate on the next full month boundary. So do not panic because a fresh utility meter looks odd on day one.

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 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. If the source resets or needs billing logic, add Utility Meter after that.
  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 this Energy Dashboard question is really a hardware, update, or installation question underneath, these guides are the next practical step.

FAQ

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

Because many Energy Dashboard fields expect accumulated energy, not just live power. If your entity reports W or kW, create an energy sensor with the Integral helper unless you are in one of the newer grid or battery cases that 2026.2 added direct support for.

Should my energy sensor use total or total_increasing?

For energy sensors, Home Assistant's FAQ says both total and total_increasing are valid. For power sensors, the state class should be measurement.

Can I use manual readings or sensors that reset?

Usually yes. The Utility Meter helper is specifically built for cycles, tariffs, delta values, net meters, and periodically resetting sources.

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?

Because the first cycle is incomplete. Home Assistant's Utility Meter docs say a new daily sensor is accurate the next day, and a monthly one is accurate on the next full monthly cycle.