跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

energy

Use when analyzing Home Assistant energy data — consumption, solar production, battery, grid costs, per-device usage — or safely editing Energy dashboard sources and tracked devices through HA NOVA Relay.

markusleben · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add markusleben/ha-nova --skill energy

技能说明


name: energy description: Use when analyzing Home Assistant energy data — consumption, solar production, battery, grid costs, per-device usage — or safely editing Energy dashboard sources and tracked devices through HA NOVA Relay. license: MIT compatibility: Requires the ha-nova CLI (run 'ha-nova setup' first) and the HA NOVA Relay in Home Assistant (App, or standalone container on Container/Core).

HA NOVA Energy

Scope

Analysis (read-only):

  • energy config overview + misconfiguration triage (energy/validate)
  • consumption/production/cost reports over bounded periods
  • per-device ranking and cost (fixed or dynamic prices)
  • solar/battery/grid KPIs: self-sufficiency, self-consumption, battery round-trip
  • period comparisons (previous period, same period last year)

Config (gated writes):

  • add/update/remove energy sources and tracked devices via energy/save_prefs

Not in scope:

  • dashboard cards/views (ha-nova:dashboard)
  • generic entity history/logbook (ha-nova:history)
  • statistics repair (sum spikes, orphaned statistics): ha-nova:maintenance
  • creating sensors or integrations that produce new energy data (energy sensor from a power sensor → ha-nova:helper, type integration)

Bootstrap (once per session)

Read and follow ../ha-nova/session-bootstrap.md. Verify relay CLI: ha-nova relay health If this fails: ha-nova setup

Relay Contract

File-based requests: ha-nova relay ws --data-file <payload-file>; --out <result-file> for large responses. WS body: .data (skills/ha-nova/relay-api.md → Standard Envelope). Schemas, KPI formulas, and analysis recipes: skills/energy/energy-reference.md — read it before any config write or KPI computation.

Flow

Overview

WS {"type":"energy/get_prefs"} → sources + tracked devices. Error ERR_NOT_FOUND ("No prefs") means the dashboard was never configured — offer initial setup instead of failing. Report grouped: sources first (grid/solar/battery/gas/water), then devices (count + notable entries). Run WS {"type":"energy/validate"} in the same pass; its issue lists are parallel to config order — map every issue to its source/device and name the concrete fix (issue table in the reference).

Analysis

Resolve statistic IDs from prefs, then query recorder/statistics_during_period with types:["change"] and units:{"energy":"kWh"} over a bounded window (default: last 30 days). Follow the statistics contract in the reference exactly: HA-local day boundaries (weeks start Monday), ms-epoch timestamps, missing buckets count as 0, negative change is legal, 5minute period only reaches back ~10 days. Compute KPIs with the formulas in the reference so numbers match the HA UI; label documented approximations as such. Present cost figures as estimates — HA cost math never equals the utility bill (standing charges, VAT, official metering). Never: diff raw total_increasing states (use statistics change), report peak watts from energy-only statistics (only hourly averages exist — say so), present a partial day/month as a complete period (label it and compare like-for-like), or rebuild an EV manager's session history (evcc and similar expose their own statistics entities — read those).

Config edit (read → merge → save)

  1. Fresh energy/get_prefs immediately before composing the save — never reuse an earlier read.
  2. Detect the grid schema generation from the data (flow_from present = legacy nested; flat keys = HA 2026.3+). Emit the same generation; never mix. With no existing grid source to detect from, pick by HA version (GET /api/config → version; 2026.3+ = flat, else legacy). Preserve every field you do not edit verbatim, including unknown keys (power_config, stat_soc, name).
  3. Mutate the returned list. save_prefs replaces the entire list for every key present — send only the top-level keys you touched, each as its complete list (canonical payload in the reference).
  4. Preview the planned change: the exact entries added/changed/removed plus the count invariant (count before ± changes = count after). Say explicitly: removing a device stops tracking only — its recorded statistics stay.
  5. Confirmation bound to this exact preview (context skill → Active Preview Confirmation): natural for a single add/change/remove; a save that empties or wholesale-replaces a list on a configured instance is destructive — typed confirmation code (context skill → Confirmation Tiers). Before any save that REMOVES entries (a single source/device removal included) or empties/wholesale-replaces a list, capture the auto config snapshot of the fresh pre-save get_prefs read (category energy, fixed name auto-prefs — the prefs are one document without item ids; skills/ha-nova/config-snapshots.md; on capture failure follow its capture-failure stop). Then run the drift check before applying (skills/ha-nova/write-safety.md → Drift check before apply): re-read get_prefs immediately before the save and compare it against the basis this preview was composed from. On first-time setup the basis is absence: a second ERR_NOT_FOUND means nothing changed and the save proceeds, while prefs that exist now expire the confirmation. On any other foreign change STOP — the confirmation expired, recompose and preview again. save_prefs replaces whole lists with no locking, so a source another client added in the meantime would vanish without a trace. Then WS energy/save_prefs (fails unless the App's configured HA token has admin rights).
  6. Verify: re-read get_prefs (the save response echoes the new prefs — still re-read), confirm the invariant and that every untouched entry is deep-equal to the fresh pre-save read, then run energy/validate — a successful save does NOT prove the config works (dangling statistic IDs are accepted silently). Mention that other open dashboard tabs need a reload.

Initial setup after ERR_NOT_FOUND: treat every list as empty — compose only the keys being populated (count before

阅读完整来源 ↗