Skip to content

Installation

Jump to bottom
Andrew Blackburn edited this page Oct 5, 2026 · 3 revisions

Installation

Requirements

  • Home Assistant with supported Wiser entities
  • A current browser with JavaScript modules enabled
  • A Home Assistant version that provides native Tile-card features for the visual feature editor

Bundled with the Wiser integration

The Wiser integration can register the card automatically for storage-mode dashboards. After updating the integration:

  1. Restart Home Assistant.
  2. Perform a hard refresh in the browser.
  3. Add Wiser Controls from the dashboard card picker.

On Home Assistant 2026.6 or newer, selecting a supported Wiser heating, shutter, light or smart-plug entity also suggests Wiser Controls in the Community cards section. The suggested card is initially limited to the selected entity.

HACS or standalone installation

When the card is installed as a standalone frontend repository, install or update it through HACS, restart Home Assistant if requested and refresh the browser. Add this repository as a custom Dashboard repository if it is not yet listed in HACS.

Manual resource

For YAML-managed resources, register this URL as a JavaScript module:

/wiser/wiser-controls-card.js

Then add the card:

type: custom:wiser-controls-card

Updating

After every update, reload the browser so Home Assistant loads the new JavaScript bundle. If the displayed version is still old, clear the frontend cache or open the dashboard in a private browser window.

When bundled with a compatible Wiser integration, frontend definitions and card bundles have separate Home Assistant update entities:

  • Wiser Frontend Panel Config updates the card registry used by the integration, including repository, filename, component and panel changes.
  • Each installed card has its own update entity, such as Wiser Controls Card.

Install a pending Frontend Panel Config update first. Home Assistant then checks the updated registry and exposes any newly discovered or renamed card update. The registry update writes the new definitions to the integration's frontend/cards.json and keeps a runtime copy in Home Assistant storage.

Development versions such as 0.5.1-beta.1-dev.1 are local test builds. Published beta releases omit the trailing -dev.N component. Stable releases use versions such as 0.5.0.

Migrating from Wiser Rooms Card

Existing custom:wiser-rooms-card configurations continue to load through the legacy alias. Opening and saving a dashboard card in the visual editor changes its type to custom:wiser-controls-card and renames the generic configuration keys. YAML dashboards must change the card type manually; legacy keys are still accepted and normalised when loaded.

The bundled updater recognises wiser-rooms-card.js as the previous Controls asset, so an installed Rooms beta can update directly to the renamed Controls release.

Upgrading to 0.5.0

Version 0.5.0 introduces independent hub_configs for multi-hub cards and moves Secondary status out of the normal Tile features list. Open and save existing cards in the visual editor to apply these migrations. If YAML is maintained manually, review the generated configuration in the code editor before copying it back to the dashboard.

After upgrading, hard-refresh the browser. For manually versioned resources, use:

/wiser/wiser-controls-card.js?v=0.5.0

Source · Issues · Releases

Wiser Controls Card

Clone this wiki locally