---
title: "Canary"
description: "Canary is a dashboard card for Home Assistant. It has 132 GitHub stars and was last updated October 26, 2026."
canonical: "https://vulpo.app/integrations/cards/jcwillox-lovelace-canary"
url: "https://vulpo.app/integrations/cards/jcwillox-lovelace-canary.md"
last-updated: "2026-10-22"
version: "1.4"
---

# Canary

> Canary is a dashboard card for Home Assistant. It has 132 GitHub stars and was last updated October 26, 2026.

Canary is a dashboard card that adds extra configuration options to existing Lovelace cards. These options are called extensions, and they work on the default cards without defining a separate canary card. The description mentions templating secondary info and stacking elements within a card. The README lists style and theme among the available extensions. The project describes itself as a staging ground for features that could later reach core Lovelace, and its name is borrowed from Chrome Canary. It requires the Marketplace, or HACS on 2026.10 and older.

Automatic summary of the README of jcwillox/lovelace-canary. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact)

[Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=jcwillox&repository=lovelace-canary&category=plugin)

On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=jcwillox&repository=lovelace-canary&category=plugin)

## Supports

- **From the Marketplace**: Installed through the Marketplace, formerly HACS.
- **Actively maintained**: Its author released or pushed a change in the last six months.

## Setting it up

Install it from the Marketplace, then add a card of this type to a dashboard.

## From the README

> The idea behind Canary is to extend the functionality of Lovelace in a non-drastic way. This is done mainly, by adding extra configuration options (extensions) to pre-existing Lovelace elements.
>
> This plugin could be thought of as almost a staging ground for features that if suitable could end up in core Lovelace, hence the name borrowed from Chrome Canary. It's unclear how well that statement will hold, it could also be called "Extensions".

From the README of [jcwillox/lovelace-canary](https://github.com/jcwillox/lovelace-canary#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened.

## At a glance

- Kind: Dashboard card
- Number: 132 GitHub stars
- Connection: Connection not stated
- Upkeep: Updated in the last 6 months
- Needs: Needs the Marketplace (HACS on 2026.10 and older)
- Latest version: v0.5.0, last updated October 26, 2026
- Source: <https://github.com/jcwillox/lovelace-canary>
- Issues: <https://github.com/jcwillox/lovelace-canary/issues>

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about)

Last updated 2026-10-22. Source: https://vulpo.app/integrations/cards/jcwillox-lovelace-canary

---

- HTML version of this page: https://vulpo.app/integrations/cards/jcwillox-lovelace-canary
- Site index for agents: https://vulpo.app/llms.txt
- Everything in one document: https://vulpo.app/llms-full.txt
- All pages: https://vulpo.app/sitemap.xml