Skip to content

v1.5.0

Choose a tag to compare

@loryanstrant loryanstrant released this 30 May 00:06
9ee68ab

What's New in v1.5.0

This release adds HACS update visibility, makes the Custom Component Monitor card more compact and accessible, and refreshes the docs.

✨ New

  • HACS updates sensor — a new sensor.hacs_updates reports how many HACS-installed components have a pending update. Its updates attribute lists each one with name, type, repository, current_version, and available_version. Because the state is a simple count, you can now show a card or trigger an automation only when updates exist (e.g. a conditional card on sensor.hacs_updates being above 0) — just like you can with the unused-component sensors. (#64)

  • Collapse sections by default — the Custom Component Monitor card gains a collapsed_by_default option (also in the visual editor as "Start collapsed"). When enabled, every section starts collapsed and can be expanded on demand, keeping long lists compact. Defaults to false, so existing dashboards are unchanged. (#62)

🎨 Improved

  • Icon-based sort control — the card's sort toggle is now a compact icon in the header (A→Z for name, calendar for days installed) sitting next to the status badge, instead of a text label in the toolbar. This keeps the card width stable when switching sort modes and lets the Installed/Used/Unused summary stay on a single line. (#63)

  • Accessibility — the sort control is a proper keyboard-focusable button with an accessible label, and shows a focus outline.

  • Accurate update versions — the updates sensor always reports the current/available pair from the comparison that actually detected the update (release versions for release-tracked repos, commit hashes for branch-tracked repos).

📖 Documentation

  • Documented the new sensor (entities table, attributes, and detection logic) and the new card option / sort behaviour.
  • Refreshed the Custom Component Monitor card screenshots to reflect the new header layout.

⬆️ Upgrade notes

  • After updating, restart Home Assistant so the new sensor is created and the updated card is staged and re-registered. A browser hard-refresh helps the card update immediately.
  • No breaking changes — existing card configurations and entities continue to work as before.

Closes: #62, #63, #64

Full Changelog: v1.4.0...v1.5.0