Troubleshooting and FAQ

Troubleshooting and FAQ

Quick checks

1. Confirm the card is installed and the browser was hard-refreshed. See Installation.
2. Start from the minimal configuration.
3. Check that the entity or statistic exists and returns the kind of data the selected chart expects.
4. Open the browser console for warnings from the card or Home Assistant.

The card does not appear

• Confirm the resource is loaded as a JavaScript module.
• For a manual installation, verify the file path and resource URL match exactly.
• Hard-refresh the browser after installing or replacing the JavaScript bundle.
• Confirm the YAML type is custom:statistics-graph-chart-card.

See Installation and Quick Start.

The chart appears but contains no data

• Confirm the entity has recorded history in Home Assistant.
• Numeric chart modes require numeric states unless you configure a State Map.
• If plotting an attribute, verify the attribute name and nested path. See Attribute Reading.
• For statistics without a normal entity, use statistic_id. See External Statistics.
• For forecast or array data, configure the attribute's time and value fields. See Attribute Data Source.

Short ranges work, but long ranges are empty

Long views can use Home Assistant's long-term statistics. The entity should normally declare a suitable state_class. Imported statistics may require an explicit statistic_id.

• Long-Range Views
• External Statistics
• Auto Scale Points

Lines bridge outages or contain unexpected gaps

Home Assistant reports sensor outages as unavailable or unknown.

• Enable break_on_null when long outages should create visible breaks.
• Leave it disabled when the last known value should carry forward.
• Use carry_forward_ms only when you need an explicit threshold.

See Break on Gaps.

The chart is slow or too dense

• Enable auto_scale_points.
• Increase the grouping interval with group_by.
• Reduce points_per_hour.
• Avoid drawing labels or points for an extremely dense series.
• Use a visible scrolling window for large history ranges.

See Auto Scale Points, On-Card Resolution Pickers, and Scrollable Graph.

Forecast or future data is missing

• Use Attribute Data Source when the entity exposes an array of future points.
• Use Forecast Horizon when recorded values predict a future time.
• Use graph_start: tomorrow for next-day price or forecast views.
• Verify whether timestamps are ISO text, epoch seconds, epoch milliseconds, or categorical units.

Synced cards do not move together

• Group names must match exactly.
• The cards must be present on the same loaded dashboard view.
• A date-picker receiver can specify only date_picker_group; one controller needs the visible picker.
• Tooltip, zoom, scroll, interval, points/hour, group-by, and date-picker groups are independent.

See Multi-Card Sync and Date Picker Group Sync.

An option disappeared from the visual editor

The editor hides controls that do not apply to the current chart mode or parent-toggle state. Hidden controls remain in the configuration and return when they become relevant.

Since v3.32 that hiding is per field, not per section: a heading disappears once every field under it is hidden, a tab once all of its sections are, and if the tab you were on is the one that went away you are moved to the first surviving tab. Nothing is dropped — a hidden control keeps its YAML value and reappears when you switch back to a mode that uses it.

See Dynamic Editor Behavior.

Two features conflict

Known intentional interactions include:

• Date Picker and Energy Date Sync cannot be enabled together.
• Rise/Fall Colors and Color Thresholds cannot be combined on the same entity.
• Auto Scale keeps the configured scale when an entity uses offset, forecast_horizon, or data_attribute.
• Sparkline mode removes card chrome and ignores controls that cannot be rendered compactly.

See Option Interactions.

card-mod styles disappear after a reload

Fixed in 3.32 (#268). The card used to rebuild its insides on the first history fetch and drop anything card-mod had already injected, so styling survived only until the next page refresh. It now carries elements injected by other tools across that first build, and it only writes the individual style properties its own card_* options set instead of rewriting the whole style attribute of ha-card.

If the same property is set both ways — card_background_color: in the config and ha-card { background: ... } via card-mod — the built-in option wins, because the card writes it as an inline style. Use one or the other, or add !important to the card-mod rule.

I found a bug or need a feature

The distributed bundle is minified and readable source is not published. Report reproducible problems or feature requests in project Issues, including the card YAML, Home Assistant version, card version, browser console errors, and a screenshot where useful.

---

Related pages

• Installation and Quick Start
• Configuration
• Option Index
• Example Finder
• ↑ Back to top