Generated YAML card catalog¶

This catalog contains standalone YAML cards that demonstrate the Flexible Horseshoe Card from a small sensor tile to a complete interactive dashboard. The files are intended to be copied into Lovelace and adapted to the entity names in your Home Assistant installation.

The examples use realistic Home Assistant entities such as Awair sensors, DSMR power readings and FHS local input entities. A card only needs the entities used by that example; the larger examples combine several of these patterns.

Start small¶

Use the basic state card when you only need one formatted value. The icon, name and state card adds the common sensor presentation, while the fixed horseshoe introduces a gauge without dynamic colors.

The color behavior is demonstrated separately by color stops, a continuous color-stop gradient, a bidirectional horseshoe, and ticks with an explicit scale.

Build the layout¶

The shapes example combines rectangles, circles and lines. The multipart text example combines name, area and state parts in one TextTool. The overflow example shows wrapping and fitting text inside a defined area.

The animation example shows how an entity update can animate a layout item. Use the actions and local controls guide when a rectangle or text item should act as a dashboard control.

Reuse and interaction¶

The action button is the smallest local-control example. The duration selector expands the idea into several buttons that update one FHS input entity.

The template card uses the reusable definition in generated-templates.yaml. Named slots keep entity references readable when a card contains several entity families. The optional room list demonstrates config-time removal with disabled.

The compound button keeps a rectangle and its label together. The visibility example uses groups as runtime tabs without removing their configuration.

Sparkline examples¶

Rolling-window history is the normal starting point. Calendar history compares a complete period. The real-time bar and equalizer show compact live-value displays.

The specialized sparkline uses a radial barcode, while the multiple-sparkline card places two independent history graphs in one card. For a video-friendly interactive tour, the radial barcode showcase switches variants and visualizations with FHS input-select entities and segmented select controls.

Larger compositions¶

The mask and clip example provides a starting point for shaped compositions. The complete Awair-style dashboard remains the reference for combining templates, slots, optional rooms, compounds, local controls, dynamic entity selection, color-stop templates and synchronized history controls.

The catalog demo view contains representative cards that can be loaded together for visual testing. The individual YAML files are the canonical versions and are easier to copy into a dashboard.

Generation rules¶

When creating another card, start with the smallest matching example and extend it only where the requested behavior needs more structure:

• Keep a single sensor card direct and readable; introduce a template when the structure will be reused.
• Use named entity slots when optional or dynamic entity lists would make numeric indices hard to maintain.
• Use disabled for configuration-time optional content and visibility for runtime switching.
• Use same_as for repeated geometry and compounds for a reusable group of related layout items.
• Use an FHS local entity for dashboard controls so buttons, text, state and sparklines use the same update path.
• Select the horseshoe or sparkline color style explicitly instead of relying on an accidental default.