Menu
Home Assistant energy monitoring and optimization patterns.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | energy-management |
| description | Home Assistant energy monitoring and optimization patterns. |
Home Assistant energy monitoring and optimization patterns.
# configuration.yaml
energy:
# The Energy dashboard is configured via UI
# Settings > Dashboards > Energy
# Whole home power
sensor:
- platform: template
sensors:
home_power:
friendly_name: "Home Power"
unit_of_measurement: "W"
device_class: power
value_template: >
{{ states('sensor.main_meter_power') | float(0) }}
home_energy_daily:
friendly_name: "Daily Energy"
unit_of_measurement: "kWh"
device_class: energy
value_template: >
{{ states('sensor.main_meter_energy') | float(0) }}
# Solar production template
template:
- sensor:
- name: "Solar Power"
unit_of_measurement: "W"
device_class: power
state_class: measurement
state: "{{ states('sensor.inverter_power') | float(0) }}"
- name: "Solar Energy Today"
unit_of_measurement: "kWh"
device_class: energy
state_class: total_increasing
state: "{{ states('sensor.inverter_energy_today') | float(0) }}"
- name: "Solar Self Consumption"
unit_of_measurement: "kWh"
state: >
{% set solar = states('sensor.solar_energy_today') | float(0) %}
{% set export = states('sensor.grid_export_daily') | float(0) %}
{{ (solar - export) | round(2) }}
template:
- sensor:
- name: "Battery Mode"
state: >
{% set power = states('sensor.battery_power') | float(0) %}
{% if power > 100 %}
Charging
{% elif power < -100 %}
Discharging
{% else %}
Idle
{% endif %}
- name: "Battery Runtime"
unit_of_measurement: "hours"
state: >
{% set soc = states('sensor.battery_soc') | float(0) %}
{% set capacity = 13.5 %}
{% set load = states('sensor.home_power') | float(1000) / 1000 %}
{{ ((soc / 100) * capacity / load) | round(1) }}
# Rate input helpers
input_number:
electricity_rate_peak:
name: Peak Rate
min: 0
max: 1
step: 0.01
unit_of_measurement: "$/kWh"
initial: 0.35
electricity_rate_offpeak:
name: Off-Peak Rate
min: 0
max: 1
step: 0.01
unit_of_measurement: "$/kWh"
initial: 0.12
# Binary sensor for rate period
binary_sensor:
- platform: tod
name: Peak Rate Period
after: "16:00"
before: "21:00"
# Cost calculation
template:
- sensor:
- name: "Current Rate"
unit_of_measurement: "$/kWh"
state: >
{% if is_state('binary_sensor.peak_rate_period', 'on') %}
{{ states('input_number.electricity_rate_peak') }}
{% else %}
{{ states('input_number.electricity_rate_offpeak') }}
{% endif %}
- name: "Daily Cost"
unit_of_measurement: "$"
state: >
{% set import = states('sensor.grid_import_daily') | float(0) %}
{% set export = states('sensor.grid_export_daily') | float(0) %}
{% set rate = states('sensor.current_rate') | float(0.25) %}
{{ ((import * rate) - (export * rate * 0.8)) | round(2) }}
# Smart EV charging automation
automation:
- alias: "EV - Solar Surplus Charging"
trigger:
- platform: numeric_state
entity_id: sensor.grid_export
above: 2000
for: "00:05:00"
condition:
- condition: state
entity_id: binary_sensor.ev_connected
state: "on"
action:
- service: switch.turn_on
entity_id: switch.ev_charger
- service: number.set_value
target:
entity_id: number.ev_charge_current
data:
value: >
{{ (states('sensor.grid_export') | float / 240) | round | min(32) }}
type: custom:power-flow-card-plus
entities:
battery:
entity: sensor.battery_power
state_of_charge: sensor.battery_soc
grid:
entity: sensor.grid_power
home:
entity: sensor.home_power
solar:
entity: sensor.solar_power
type: entities
title: Energy Costs
entities:
- entity: sensor.daily_cost
name: Today
- entity: sensor.monthly_cost
name: This Month
- entity: sensor.solar_savings
name: Solar Savings
| Device | Purpose | Protocol |
|---|---|---|
| Emporia Vue | Whole home | WiFi |
| Shelly EM | Circuit monitor | WiFi |
| IoTaWatt | Multi-circuit | WiFi |
| Sense | AI detection | WiFi |
| Coral TPU | Object detection | USB |
Select and coordinate multi-agent teams (topology kits, role-based squads, lifecycle, worktree isolation). Use this skill whenever launching parallel agents, designing a review board, running a debug council, scheduling an orchestrator-workers team, configuring agent tool restrictions, or deciding between solo and team execution. Triggers on: "launch a team", "parallel agents", "review board", "debug council", "architect-implementer-reviewer", "swarm", "multi-agent", "subagents for X", "team topology", "agent lifecycle".
Select and wire an agentic design pattern (reflection, prompt chaining, routing, parallelization, orchestrator-workers, evaluator-optimizer, ReAct, blackboard) into the 5-layer Claude Code stack. Use this skill whenever deciding how to structure a multi-step task, whether to spawn subagents, how to run parallel review, or when to use which pattern. Triggers on: "which pattern", "orchestrate", "parallel review", "self-review", "chain of thought", "eval-optimizer loop", "blackboard", "ReAct", "how to decompose this task".
Auto mode permission handling — classifier-based approvals, PermissionDenied hook, defer permissionDecision, and autonomy profiles for hands-off Claude Code usage
Configure Claude Code's autonomous operating mode — profile selection (conservative, balanced, aggressive, unattended-review), permission blocks, and the three gate agents (planner, verifier, reviewer). Use this skill whenever enabling autonomous mode, switching profiles, tightening permissions for production branches, or setting up unattended execution. Triggers on: "autonomy", "unattended mode", "auto-approve", "permission mode", "autonomy profile", "gates", "/cc-autonomy", "planner verifier reviewer", "let claude run on its own".
Manage Claude Code's context window — token arithmetic, /compact strategy, anchor preservation, progressive loading, session analytics. Use this skill whenever a session gets long, context approaches limits, after /compact, when deciding what to load into CLAUDE.md vs leave in references, or when analyzing session cost/token usage. Triggers on: "context full", "compact", "too many tokens", "budget", "session analytics", "save tokens", "context window", "/compact strategy".
Evidence-driven deep analysis for hard coding problems — architecture decisions, root-cause investigation, high-stakes refactor planning, performance bottleneck isolation. Use this skill whenever the user asks for "the best approach", a "deep analysis", "root cause", "principal engineer review", or runs /cc-intel. Also triggers on hard debugging questions, major architectural choices, tricky performance problems, or any task where a hypothesis tree and evidence table matter more than a fast answer.