Skip to content

LCARdS 2026.06.01.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Jun 00:30
2026.06.01.1
eded22c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A bit of a smaller release with respect to new features - only a couple new items.
However, the release has large and important updates for HA 2026.5+ to keep in line with HA UI deprecated elements and changes.

New Features

State-Based Colour Config Enhancements

Attribute Support (state_attribute)

Button, Elbow, and Slider cards now support a top-level state_attribute config field.
When set, the resolved string value of that attribute becomes the highest-priority key for all exact-match state-based colour lookups across the card.

Useful for for entities such as climate where the desired signal is an attribute like hvac_action rather than the top-level state (heat/cool)

type: custom:lcards-button
preset: lozenge
entity: climate.living_room
state_attribute: hvac_action   # "heating", "cooling", "idle", "off"
icon_style:
  color:
    heating: "var(--lcards-orange)"
    cooling: "var(--lcards-blue)"
    idle: "var(--lcards-gray)"
    "off": "var(--lcards-gray-dark)"
icon_area_background:
  heating: "alpha(var(--lcards-orange), 0.15)"
  cooling: "alpha(var(--lcards-blue), 0.15)"
  idle: transparent

state_attribute applies to every state-based colour config on the card like backgrounds, icons, borders, etc.
Attribute values are serialized to strings so boolean attributes can be matched with "true" / "false", which you write as-is in your YAML keys.

state_attribute does not replace ranges_attribute. The two work independently:

Config field What it controls
state_attribute Which attribute value is matched against exact string keys (heating, true, fade, …)
ranges_attribute Which attribute's numeric value is used for range keys (above:50, between:10:90, …)

Colour Config Object as a Template

Instead of defining per-state colours, the .color config fields (ie. icon_style.color, icon_area_background, background, border color, etc.) can now be set to a single template string for the whole object. The template must evaluate to a single colour value (in any supported format.) This allows for specific advanced logic where needed.

Previously, using a template at the field level was broken — the raw template string was passed through unresolved. It is now evaluated via the card's pre-evaluated style cache before the colour is applied.

type: custom:lcards-button
preset: lozenge
entity: climate.living_room
icon_style:
  color: "{{ state_attr('climate.living_room', 'hvac_action') | default('off') }}"
icon_area_background: "{{ '#ff6600' if is_state('climate.living_room', 'heat') else '#444444' }}"

Enhancements & Fixes

HA 2026.5 / 2026.6 Component Compatibility

This release has a large backend update for full HA 2026.5-6+ compatibility.
All deprecated components have been removed and use current HA elements (ha-input, ha-icon-button-size variables) across the board. It brings improved UI consistency and a comprehensive standardization of all component styles to use HA's native CSS variable system. This ensures that LCARdS looks and behaves correctly across all HA themes in both light and dark modes.

Card Suggestion Supoort in the Card Picker (HA 2026.6+)

LCARdS cards now participate in Home Assistant's "Add card by entity" flow in the card picker when adding a card to a dashboard.

image
Card Suggested for
Button Any entity
Chart sensor, input_number, number, weather
Slider light, fan, cover, input_number, number, climate, media_player, humidifier, water_heater, valve
Select Menu input_select, select

Full Changelog: 2026.05.24.1...2026.06.01.1

Assets 3
Loading