ha-energylisted

Answer energy questions with numbers, not guesses: **find the sensors → learn what HA actually tracks (Energy dashboard) → measure over a period → rank the consumers.** Set the Supervisor-proxied Core API shorthand (the token is always present, no HA Token needed): ```bash API=http://supervisor/core/api AUTH="Authorization: Bearer $SUPERVISOR_TOKEN" ``` ## 1. Find the energy & power sensors Two device classes matter: `power` (instantaneous, **W**/**kW**) and `energy` (cumulative, **Wh**/**kWh**). Energy meters you can subtract over time usually have `state_class: total_increasing`. ```bash # Cumulative energy meters (kWh) — usable for consumption over a period curl -sS -H "$AUTH" "$API/states" | jq -r ' .[] | select(.attributes.device_class=="energy") | "\(.entity_id)\t\(.state) \(.attributes.unit_of_measurement)\t\(.attributes.state_class)\t\(.attributes.friendly_name)"' # Instantaneous power sensors (W/kW) curl -sS -H "$AUTH" "$API/states" | jq -r ' .[] | select(.attributes.device_class=="power") | "\(.entity_id)\t\(.state) \(.attributes.unit_of_measurement)\t\(.attributes.friendly_name)"' ``` Catch anything mislabelled by unit alone: ```bash curl -sS -H "$AUTH" "$API/states" | jq -r ' .[] | select((.attributes.unit_of_measurement // "") | test("^(k?Wh|k?W)$")) | "\(.entity_id)\t\(.state) \(.attributes.unit_of_measurement)"' ``` ## 2. Read the Energy dashboard config (what HA really tracks) The Energy dashboard preferences are **not exposed on the REST