ha-graphs-visualization
Creates and configures Home Assistant graph visualizations using history-graph, statistics-graph, mini-graph-card, and apexcharts-card with time ranges, aggregations, and multi-sensor support. Use when displaying sensor data over time, creating trend charts, comparing historical data, or building energy/climate/air quality dashboards.
What this skill does
Works with Home Assistant native cards, HACS custom cards, and YAML configurations.
# Home Assistant Graphs and Visualization
Create informative graphs and charts for sensor data visualization in Home Assistant dashboards.
## When to Use This Skill
Use this skill when you need to:
- Display sensor data over time with history-graph for recent data (hours/days)
- Create long-term trend analysis with statistics-graph for weeks/months
- Build compact sparkline graphs with mini-graph-card for dashboard space efficiency
- Generate publication-quality charts with ApexCharts for multi-sensor comparisons
- Add dual Y-axis graphs for temperature + humidity or similar combinations
- Troubleshoot ApexCharts span.end errors with validated configurations
Do NOT use when:
- You only need current sensor values without history (use gauge or entity cards)
- Building real-time monitoring without historical context (use current state displays)
- You haven't installed required HACS cards (mini-graph-card or apexcharts-card)
## Quick Start
This skill covers four main graphing solutions:
- **History Graph** (native): Simple sensor history with automatic long-term statistics
- **Statistics Graph** (native): Long-term trend analysis with aggregations
- **Mini-Graph-Card** (HACS): Popular, lightweight graphs with customization
- **ApexCharts Card** (HACS): Advanced publication-quality charts with annotations
### Basic Examples
**History Graph (Native):**
```yaml
type: history-graph
entities:
- entity: sensor.temperature
name: Living Room
- entity: sensor.humidity
hours_to_show: 24
```
**ApexCharts (HACS) - VALIDATED CONFIG:**
**CRITICAL:** The `span.end` field must be one of: "minute", "hour", "day", "week", "month", "year", "isoWeek"
```yaml
type: custom:apexcharts-card
header:
show: true
title: 24 Hour History
show_states: true
graph_span: 24h
span:
end: hour # REQUIRED: minute/hour/day/week/month/year/isoWeek
yaxis:
- min: 0
max: 50
decimals: 1
apex_config:
chart:
height: 200
xaxis:
type: datetime
labels:
datetimeFormatter:
hour: "HH:mm"
legend:
show: true
series:
- entity: sensor.temperature
name: Temperature
color: "#e74c3c"
stroke_width: 2
```
**Common ApexCharts Errors:**
- ❌ WRONG: `"span": {"end": "now"}` → Causes parsing error
- ✅ CORRECT: `"span": {"end": "hour"}` → Valid value
## Usage
Follow these steps to create Home Assistant graphs:
1. **Select graph type** based on data (native vs HACS)
2. **Configure time ranges** appropriate for data frequency
3. **Add multiple entities** for comparisons
4. **Set y-axis bounds** for proper scaling
5. **Apply styling** for readability
## Graph Selection Decision Tree
```
START
│
├─ Need simple sensor history (last 24-48h)?
│ └─ YES → Use history-graph (native)
│
├─ Need long-term trends (weeks/months)?
│ └─ YES → Use statistics-graph (native)
│
├─ Need minimalist design with moderate customization?
│ └─ YES → Use mini-graph-card (HACS)
│
└─ Need advanced features (annotations, comparisons, multi-axis)?
└─ YES → Use apexcharts-card (HACS)
```
## Comparison Matrix
| Feature | History Graph | Statistics Graph | Mini-Graph-Card | ApexCharts |
|---------|---------------|------------------|-----------------|------------|
| **Type** | Native | Native | HACS | HACS |
| **UI Editor** | ✅ Full | ✅ Full | ❌ YAML only | ❌ YAML only |
| **Performance** | ⚡ Fast | ⚡ Fast | ⚡ Fast | ⚠️ Moderate |
| **Customization** | 🔹 Basic | 🔹 Basic | 🔸 Good | 🔶 Extensive |
| **Multiple Entities** | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
| **Chart Types** | Line | Line/Bar | Line/Bar | Line/Bar/Area/Column |
| **Time Range** | Hours | Calendar periods | Hours | Flexible spans |
| **Statistics** | Auto | Built-in | Manual | Manual |
| **Best For** | Quick history | Long-term trends | Clean design | Power users |
## History Graph Card (Native)
**Best for:** Simple sensor history visualization (recent data)
### Basic Configuration
```yaml
type: history-graph
entities:
- entity: sensor.temperature_living_room
name: Living Room
- entity: sensor.temperature_bedroom
name: Bedroom
hours_to_show: 24
refresh_interval: 0 # Default: auto-refresh
```
### Key Features
- Displays sensor history from recorder database
- Automatically switches to long-term statistics for older data
- Bold line = recorder data, thin line = statistics
- If `hours_to_show` > recorder retention: uses long-term statistics
**Performance Note:** History graphs are very fast because they use HA's built-in recorder data.
## Statistics Graph Card (Native)
**Best for:** Long-term trend analysis (weeks, months, years)
### Basic Configuration
```yaml
type: statistics-graph
entities:
- sensor.energy_daily
stat_types:
- mean
- min
- max
period:
calendar:
period: month
chart_type: line
```
See `references/reference.md` for stat types and period options.
## Mini-Graph-Card (HACS)
**Installation:** HACS → Frontend → Search "mini-graph-card"
**Best for:** Minimalist design, lightweight, moderate customization
### Basic Temperature Graph
```yaml
type: custom:mini-graph-card
entities:
- sensor.temperature_bedroom
- sensor.temperature_living_room
name: Temperature Comparison
hours_to_show: 24
points_per_hour: 2
line_width: 2
font_size: 75
```
### Multiple Entities with Colors
```yaml
type: custom:mini-graph-card
entities:
- entity: sensor.temperature
name: Temp
color: '#e74c3c'
- entity: sensor.humidity
name: Humidity
color: '#3498db'
y_axis: secondary
show:
labels: true
legend: true
name: true
state: true
```
See `references/reference.md` for complete configuration options and `examples/examples.md` for more patterns.
## ApexCharts Card (HACS) - VALIDATED CONFIGURATIONS
**Installation:** HACS → Frontend → Search "apexcharts-card"
**Best for:** Advanced visualizations, publication-quality charts, complex comparisons
### CRITICAL: Valid Span Configuration
**Always use one of these valid values for `span.end`:**
```yaml
span:
end: minute # Start of current minute
end: hour # Start of current hour (RECOMMENDED)
end: day # Start of current day
end: week # Start of current week
end: month # Start of current month
end: year # Start of current year
end: isoWeek # Start of ISO week (Monday)
```
**Never use:** `"now"` or other string values - these cause errors.
### Basic Time Series (VALIDATED)
```yaml
type: custom:apexcharts-card
header:
show: true
title: Temperature History
show_states: true
graph_span: 24h
span:
end: hour # REQUIRED
yaxis:
- min: 0
max: 50
decimals: 1
apex_config:
chart:
height: 200
xaxis:
type: datetime
labels:
datetimeFormatter:
hour: "HH:mm"
legend:
show: true
series:
- entity: sensor.temperature_living_room
name: Living Room
color: "#e74c3c"
stroke_width: 2
- entity: sensor.temperature_bedroom
name: Bedroom
color: "#3498db"
stroke_width: 2
```
### Multi-Sensor with Dual Y-Axis (VALIDATED)
```yaml
type: custom:apexcharts-card
header:
show: true
title: Temperature & Humidity
show_states: true
graph_span: 24h
span:
end: hour
yaxis:
- id: temp
min: 0
max: 50
decimals: 1
- id: humidity
opposite: true
min: 0
max: 100
apex_config:
chart:
height: 250
xaxis:
type: datetime
labels:
datetimeFormatter:
hour: "HH:mm"
series:
- entity: sensor.temperature
name: Temperature
yaxis_id: temp
color: '#e74c3c'
stroke_width: 2
- entity: sensor.humidity
name: Humidity
yaxis_id: humidity
color: '#3498db'
stroke_width: 2
```
## Supporting Files
- **examples/examples.md** - Comprehensive real-world examples (climate dashboards, air quality, energy usage, multi-room comparisons, annotations, area charts)
- **references/reference.md** - Technical depth (performance optimization, advanced ApexCharts configuraRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.