Home Assistant Energy Entity Eligibility Checker: find the failed picker rule

Choose the intended Home Assistant Energy field, then enter or paste the sensor's current attributes. The checker compares its domain, state, classes, and unit with pinned Energy and long-term-statistics rules. It runs in this browser, but it cannot inspect recorder health or guarantee that the entity will appear.

Intended Energy field

Inputs stay in this browser.

Choose the Energy field before judging the sensor

Accumulated energy fields describe a quantity collected over time. The optional power field describes the current rate instead. That distinction changes the accepted device class, state class, and unit family.

Start with the exact field where the entity is missing. Changing that choice changes only the Energy comparison. It does not rewrite the separate long-term-statistics conclusion.

Each Energy field accepts a specific attribute combination

Energy fieldDevice classState classUnit family
Grid import, grid export, solar production, battery charge, battery discharge, individual deviceenergytotal or total_increasingEnergy
Optional powerpowermeasurementPower
Gasgas or energytotal or total_increasingGas volume with gas; energy with energy
Waterwatertotal or total_increasingWater volume

Energy and statistics answer different questions

Energy applies the matrix for the field you selected. Long-term statistics checks the current numeric sensor against its own supported state-class boundary. It still cannot see recorder inclusion, stored metadata, or historical unit changes.

For example, power, measurement, and Wcan match the statistics attribute contract while failing grid import's accumulated-energy rules. Counter suitability also stays separate: an unknown or decreasing counter never becomes an automatic recommendation for total_increasing.

A matching result still needs Home Assistant

A local match means the current attributes cleared the pinned comparison. It cannot guarantee that the entity appears. The Home Assistant Energy FAQcovers missing entities, and the Home Assistant sensor documentationexplains state classes and counters. Entered attributes stay in this browser; the version127 privacy policy covers ordinary page requests and site analytics separately.

  1. Check Developer Tools > Statistics for issues and the stored unit.
  2. Confirm recorder inclusion for the entity and its integration.
  3. Return to Energy settings and validate the intended field in the live instance.