Selection mode, the checkbox view you already know from the entities and devices pages, is coming to four more places in Home Assistant: dashboards, blueprints, labels and the Installed tab of the Marketplace, the built-in successor to HACS. Until now each of these had to be deleted one at a time. Daan Vervacke (DaanVervacke) wrote all four changes, and they were merged into the frontend's development branch on 18 October 2026: dashboards, the Marketplace and blueprints between 16:30 and 16:41 Polish time, labels at 21:49. They are set for Home Assistant 2026.11.

What each page leaves alone

Each page has its own rules for what it skips or removes along the way.

  • Dashboards. Built-in dashboards and dashboards defined in YAML are skipped, as they are on the devices and entities pages.
  • Blueprints. Blueprints still used by an automation or a script are skipped.
  • Labels. A deleted label disappears from every area, device and entity that carried it. The page now says "Delete" when a label is destroyed and keeps "Remove" for taking a label off an item.
  • Marketplace. Bulk uninstall works like the single uninstall. If a repository is still set up, its setups are deleted first, together with their devices and entities, and only then are its files removed.

The Marketplace case deserves the most care. Ticking ten repositories removes ten sets of devices and entities, and any automation that used them will point at entities that no longer exist.

Skipped updates stay skipped

Two smaller changes by Aidan Timson (timmo001), merged on 19 October at 14:12 and 15:14, deal with Marketplace updates you chose not to install. Until now a skipped update kept its repository at the top under "Update available" and counted in the Installed tab's badge.

Now a repository whose latest update is skipped shows as installed, with a muted mark on its icon, and no longer counts in the badge. Its page says "Update skipped" and "Version X installed, Y skipped". The muted Update button opens the update entity, where you can install that version anyway or clear the skip. As soon as a release newer than the skipped one comes out, the repository goes back to "Update available".

The frontend reads the skip from each repository's update entity, comparing skipped_version with latest_version. Nothing changes on the server side, and the list follows a skip or an unskip straight away.