* Ally: Add aria labels to ha-icon-button and hui-root
* use aria-hidden
* Add hidden content for label to satisfy ally review
* Make fix in button instead (probably should update upstream)
* Aria label (pending wa update)
* Add descriptions to Jinja2 tags, filters, expressions, tests and variables
All standard Jinja2 tags, filters, and expression completions now carry
info and detail strings so the autocomplete info popover shows meaningful
documentation when users browse them — not just HA-specific functions.
* Add keyboard shortcut tip to the template developer tool
A ha-tip below the editor card now shows users that Ctrl+Space triggers
autocomplete, Ctrl+F opens the search panel, and F11 toggles fullscreen,
making the editor's built-in features more discoverable.
* Add hover tooltips for Jinja2 functions, filters and expressions
Hovering over a function, filter, tag, test, or variable name inside a
Jinja2 template shows a tooltip with its signature and description.
Non-tag completions also get a help-circle icon linking to the
corresponding Home Assistant template-functions documentation page.
The tooltip is rendered as a custom Lit element (ha-code-editor-jinja-hover)
that takes the Completion object and an optional docUrl as properties.
The tooltip source (haJinjaHoverSource) is wired into ha-code-editor
via CodeMirror's hoverTooltip extension. The documentationUrl() helper
is used so the link points to the correct subdomain (www / rc / next)
based on the running HA version.
* Add hover tooltips for Jinja2 hover + arg value tooltips for entity/device/area
Wire haJinjaHoverSource into ha-code-editor via CodeMirror hoverTooltip.
Two types of hover are now shown in jinja2/yaml mode:
- Hovering a function/filter/tag/expression name shows its signature,
description, and a doc-link icon (non-tags only).
- Hovering a string-literal argument of a known HA Jinja function (e.g.
states(), device_name(), area_entities()) shows the friendly name,
current state, device, and area for entity_id arguments; the device
name and area for device_id arguments; and the area name for area_id
arguments. The same applies to states["entity_id"] subscripts.
The arg-value tooltip reuses CompletionItem / ha-code-editor-completion-items
(the same component used for autocomplete info popovers) via a new
ha-code-editor-jinja-arg-hover element. HA registry data is passed from
ha-code-editor via a HassArgHoverContext interface to keep jinja_ha_completions.ts
free of HomeAssistant type imports.
* only add tip for autocomplete
* review
* Expose Z-Wave exclusion instructions when removing device
* text tweaks
* Apply suggestion from @MindFreeze
* Apply suggestions from code review
Co-authored-by: Petar Petrov <MindFreeze@users.noreply.github.com>
* bring back comment
---------
Co-authored-by: Petar Petrov <MindFreeze@users.noreply.github.com>
* Only show events output when there are any, types and margin
* Refactor to use pagination
* Fix
* Simplify, remove pinning and auto-follow, stay on event 1 and allow the user to move around manually
* Show info why only 30 events are keps
* Increase bufffer limit to 100, add explainer and tip when rolls over
* Update disclaimer
* Use buffer position and total instead of event id + total in counter
* Use fixed height and constrain editor
* Cleanup
* Cleanup
* Fix narrow layouts
The old heading "Device created" was a past-tense status message that didn't
communicate what the user needs to do next. The dialog contains a name field
and an area picker, so "Name and assign" better reflects the user's actual
task at this step.
Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
* Check for unknown value every render if value is unknown
* fix race in pickers that add items from the picker
* fix: use value imports for LitElement, html, nothing from lit
* feat: Split legend interaction (click vs label) with icons and hover effects
* Address review feedback on chart legend split
- Rename `externalHiddenState` to `clickLabelForMoreInfo` and the event
`chart-legend-click` to `legend-label-click` (the `chart-` prefix is
reserved for echarts-proxy events).
- Use proper translation keys
`ui.components.history_charts.{toggle_visibility,show_more_info}`
instead of `ui.common.*` which don't exist.
- Drop the redundant tooltip on the label when it would duplicate the
icon's "Toggle visibility" tooltip.
- Resolve the legend dataset id back to a real `entity_id` before
opening more-info: strip known climate-attribute suffixes for history
charts (`-current_temperature`, `-target_temperature*`, `-heating`/
`-cooling`/`-drying`/`-fan`), and skip `isExternalStatistic` ids for
statistics charts. Only fire `hass-more-info` if `hass.states[id]`
resolves.
* Address followup review feedback on chart legend
- Restore stat-type suffix stripping in statistics chart. When the chart
has a single entity, ha-chart-base falls back to raw series ids
(`${statistic_id}-${type}`) for the legend, so clicking
"sensor.foo (max)" otherwise tries to open `sensor.foo-max`.
- Cover humidifier multi-attribute datasets in the entity-id resolver
alongside climate / water_heater (`-current_humidity`,
`-target_humidity`, `-humidifying`, `-on`; `-drying` is already
contributed by CLIMATE_MODE_CONFIGS). Rename the constant to
ENTITY_DATASET_SUFFIXES to reflect the broader scope.
- Convert the two legend click targets to `<button type="button">` so
Tab navigation, Enter/Space activation, and screen-reader semantics
work. Add `aria-pressed` to the visibility toggle and a
`:focus-visible` outline. Read the dataset id from `data-id` instead
of `parentElement.id` so the handlers don't depend on DOM nesting.
- Scope the label hover underline to `.label-clickable` so charts that
don't opt into more-info (network, sankey, sunburst, energy) keep the
legacy non-underlined toggle behavior. Render the "Show more info"
tooltip only when the click will actually fire.
- Drop the redundant physical `margin-right: 0` on the legend toggle;
`margin-inline-end: 0` alone preserves the click-area extension on
the start side in RTL.
---------
Co-authored-by: Petar Petrov <MindFreeze@users.noreply.github.com>
* Modified the chart legend for climate temperature data sets to display the temperature value, not the overall entity state (previously hvac_mode).
* Use the helper computeAttributeValueDisplay in src/common/entity/compute_attribute_display.ts to format the temperature attribute values.
Co-authored-by: Copilot <copilot@github.com>
* Update src/components/chart/state-history-chart-line.ts
---------
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Petar Petrov <MindFreeze@users.noreply.github.com>
* fix: rebuild ha-panel-custom on reconnect after suspendWhenHidden
Why:
HA's PartialPanelResolver._onHidden() starts a 5-minute timer when a tab
is backgrounded. When it fires, non-iframe / non-app custom panels
(component_name="custom" without embed_iframe) are removed from the DOM,
which triggers ha-panel-custom.disconnectedCallback() -> _cleanupPanel().
That nulls _setProperties and destroys the child custom-panel element.
When the user returns, _onVisible() re-appends the same <ha-panel-custom>
element. ReactiveElement's base connectedCallback schedules an update,
but update() only calls _createPanel(this.panel) when
changedProps.has("panel") && !deepEqual(oldPanel, this.panel) -- the
panel reference hasn't changed, so nothing happens. _setProperties is
also undefined, so the property-forwarding branch exits early too.
Result: <ha-panel-custom> is present in the DOM but empty -- the user
sees a blank panel until they hard-reload.
Add a connectedCallback() override that rebuilds when the element was
previously cleaned up. Three guards keep it scoped to the recovery path:
- !this._setProperties: sentinel for "_cleanupPanel ran".
_setProperties is set inside _createPanel's success paths and only
nulled in _cleanupPanel.
- !this.hasChildNodes(): defends against the async window inside
loadCustomPanel(config).then(...) for non-iframe panels, where a
rapid detach->attach cycle could otherwise call _createPanel twice
and append duplicate elements.
- this.panel: skips first-mount, when the router hasn't assigned a
panel yet. The existing update() path handles initial _createPanel
via the changedProps.has("panel") branch.
Mirrors the existing disconnectedCallback override for symmetry.
10 lines + comment, no other file changes.
Affects every non-iframe sidebar custom panel in the HACS ecosystem
(Alarmo, Browser Mod, Homematic(IP) Local, MeshCore, others -- ~60k
combined HA-analytics installs). Reopens dormant home-assistant/frontend
issue #14510 (filed 2022-12-02, stale-bot closed without a fix).
Tests:
- yarn build succeeds locally; the affected chunk is captured for the
pre-PR local-test on a real HA host.
- Manual repro on user's HA host (10.10.21.221) with the MeshCore
custom panel: baseline (no patch) reproduces the blank-panel symptom
after a 6-minute backgrounded tab. Patched chunk: panel rebuilds
within ~2 seconds of returning. Exemption paths (iframe panel, app
panel, custom panel with embed_iframe=true) verified to remain
unaffected. Original chunk restored after testing.
- yarn lint and yarn test pass before PR submission (run before
Phase 9).
* chore: trigger CLA recheck after author-email link
* increase an active "enlarge" area
Added a class to make the title span enlargeable.
* increase an active "enlarge" area
* increase an active "enlarge" area
* Add entity context to media browser player picker
Show area and device as a secondary line in both the active player pill
and the player picker dropdown, so users can identify speakers when
multiple players share similar names.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Update src/panels/media-browser/ha-bar-media-player.ts
Co-authored-by: Paul Bottein <paul.bottein@gmail.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Petar Petrov <MindFreeze@users.noreply.github.com>
Co-authored-by: Paul Bottein <paul.bottein@gmail.com>
Remove the unmaintained eslint-config-airbnb-base dependency (last
updated Nov 2021, no flat config support) along with its FlatCompat
shim infrastructure.
Replace with js.configs.recommended as the base config and explicitly
cherry-pick ~40 high-value safety and style rules from airbnb-base
that aren't already covered by other configs.
Remove 27 rule disables that only existed to suppress airbnb opinions,
and 5 dead TypeScript rule disables for rules no longer in the config.
Fix 4 real bugs caught by the newly added no-constant-binary-expression
rule where template literals were always truthy, making fallback values
unreachable.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
If the app config contains a schema field like this one:
```
privileges:
- "list(ALTER|CREATE|...|UPDATE)?"
```
it was rendered incorrectly as a drop-down where only one item can be
selected - but this is wrong because of the preceding `-` denoting it
should be a list containing the listed values. Supervisor translated
this to an entry of type `select` with `multiple: true`. The `multiple`
flag wasn't passed along, with the flag set the field renders as
expected.
Fixes#51533
* Fix history/sensor cards stuck loading after backend restart
- Add { resubscribe: false } to history subscriptions to prevent
corrupt HistoryStream state on auto-resubscription
- Add connection-status handlers to re-subscribe on reconnect
- Add sentinel pattern to prevent re-entrant async subscriptions
- Add shouldUpdate/updated retry when components become available
- Clear sensor device classes cache on WS error
- Clear _error on reconnect so cards can retry
- Add .catch() on unsubscribe to handle dead subscriptions
* Fix type annotation for callWS in getSensorNumericDeviceClasses
* Address review: type connection-status handlers, add reconnect to history panel
- Use HASSDomEvent<ConnectionStatus> instead of (ev as CustomEvent).detail
for proper type safety on all connection-status handlers
- Add connection-status handler to ha-panel-history so it re-subscribes
after backend restart (addresses concern about resubscribe: false)
* Address review: sentinel pattern, reconnect handling, stale data reset
- Add sentinel pattern to ha-more-info-history, ha-panel-history,
hui-history-graph-card to prevent re-entrant subscription races
- Refactor hui-trend-graph-card-feature from SubscribeMixin to manual
subscription management with connection-status reconnect support
- Reset stale history/statistics data on reconnect in
hui-history-graph-card and hui-map-card before re-subscribing
- Wrap fetchStatistics and getSensorNumericDeviceClasses calls in
ha-panel-history with try/catch to handle errors gracefully
- Chain .catch directly on subscribeHistoryStatesTimeWindow in
hui-trend-graph-card-feature to avoid detached-promise race condition
* Centralize history stream reconnect handling in data layer
Move the reconnect logic from every consumer into `subscribeHistoryStream`
in data/history.ts. The helper listens to the connection's `ready` event
itself, and on reconnect creates a fresh `HistoryStream` and rebuilds
params (so `start_time` for the time-window variant is re-anchored to
"now"). `resubscribe: false` stays as an internal implementation detail.
Removes the duplicated `_handleConnectionStatus` boilerplate and
`connection-status` window listeners from all six history consumers.
* Render subscription errors and make _error reactive
`_error` was declared as a plain string field in hui-graph-header-footer
and ha-more-info-history (non-reactive) and typed as Error/string while
being assigned the WS error object. hui-trend-graph-card-feature had it
reactive but never rendered it.
Align all three with the hui-history-graph-card pattern: reactive
`{ code, message }` and a user-visible error branch in render(). Without
this, a failed subscription would leave the component stuck on a spinner
forever.
---------
Co-authored-by: Petar Petrov <MindFreeze@users.noreply.github.com>
* Allow showing/hiding welcome message on home overview
Add a toggle in the edit overview dialog to show or hide the
"Welcome, [user]" greeting header on the home overview page,
following the same pattern as the existing summary enable/disable.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Move welcome message toggle into its own section in home editor
The welcome message is a greeting header, not a summary card, so it
now lives in a separate "Greeting" section above the "Summaries" section.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* rename hidden_welcome_message to hide_welcome_message
* Use ha-form boolean selector for welcome message toggle
Replace manual label/ha-switch markup with ha-form using a boolean
selector for better accessibility and consistency with the rest of
the codebase.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Add helper text to welcome message toggle in home editor
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Remove greeting section header
* Allow enabling/disabling suggested entities on home overview
Add a toggle in the Overview edit dialog to show or hide the
usage-predicted entities that fill remaining slots alongside favorites.
When disabled, the usage prediction fetch is skipped entirely.
The favorites entities helper text is updated to no longer reference
suggestions, which now have their own dedicated toggle and description.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Use ha-input-helper-text for suggested entities description
Replace the raw <p class="section-description"> with ha-input-helper-text
for the suggested entities toggle description, using the proper HA
component for helper text styling instead of custom CSS.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Rename show_suggested_entities to hide_suggested_entities
Aligns with the hidden_summaries naming convention used elsewhere.
Logic is inverted accordingly: undefined means shown (default),
true means hidden.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Use ha-form boolean selector for suggested entities toggle
Replace the manual label+switch+helper-text with ha-form using a boolean
selector.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Refine suggested entities toggle label and callback signatures
Drop unused schema parameter from computeLabel/computeHelper callbacks
and shorten the label from "Show suggested entities" to "Suggested entities"
since the boolean checkbox already conveys the enabled/disabled intent.
* Group favorite entities picker and suggested toggle in expandable panel
Wrap ha-entities-picker and the suggested entities boolean in an outlined
ha-expansion-panel with a star-outline icon. Move the welcome message
toggle above the panel. Use "Favorite entities" as the panel header and
remove the redundant picker label.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Update entities description to use "include" instead of "show"
* Fix expansion panel content leaking when collapsed
Move inner padding from --expansion-panel-content-padding to a wrapper
div, matching the ha-form-expandable pattern, so no content is visible
when the panel is collapsed.
* Add spacing between alert and expansion panel in home editor dialog
* Move favorites description above picker, update helper text
- Add description paragraph above ha-entities-picker explaining the feature
- Update helper text to concise behavioral note: "Entities in your favorites always appear first."
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* Add daily forecast card feature
* Address review feedback: validate forecast type, refresh on state change
* Use statesContext for current temp state
* Use internationalizationContext for localize
* Narrow support/resolve helpers to accept stateObj
* Use connection instead of hass for subscribeForecast
* Reduce opacity of current temp line
* Type states context consumer
* Use consumeEntityState decorator
* Update dependency @rspack/dev-server to v2
* Upgrade @rspack/core to 2.0.0
Pairs with the @rspack/dev-server 2.0.0 bump in #51666 — dev-server v2
declares @rspack/core ^2.0.0-0 as a peer, so the two must move together.
Patches webpackbar to defend against non-string info in Rspack 2's
ProgressPlugin handler (otherwise `parseRequest` throws `split is not a
function` during compilation).
Verified locally: yarn lint:types, yarn test, yarn lint, script/build_frontend,
and all three rspack-dev-server-{demo,cast,gallery} tasks.
* Wrap webpackbar instead of patching it
Replace the yarn patch with a small SafeWebpackBar subclass that sanitizes
the progress `details` array before the upstream parseRequest sees it.
Keeps the fix local to the Rspack config where it belongs.
* Pass moduleIdentifier to webpackbar progress
Rspack 2's progress info is `{ builtModules, moduleIdentifier? }`.
moduleIdentifier is what v1 passed as a plain string, so extract it to
keep the "active module" line in the progress bar instead of blanking it.
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* Add activity log sidebar to security dashboard
Add a sidebar with a logbook card to the security domain dashboard,
filtered by security entities (cameras, locks, alarm panels, covers,
binary sensors) and person entities. The sidebar uses the sections view
sidebar layout with mobile tab support for switching between devices
and activity views on narrow screens.
https://claude.ai/code/session_01MCjuARQfuyowAbJ9fwiEnH
* Update src/panels/security/strategies/security-view-strategy.ts
* remove import
* Set max column to 3 and fix title margin
* Type fix
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Petar Petrov <MindFreeze@users.noreply.github.com>
Co-authored-by: Paul Bottein <paul.bottein@gmail.com>
* Auto-refresh serial ports every 5s in serial selector
Schedules the next fetch via setTimeout once the previous response
resolves, so slow responses don't stack requests. Refreshing is
stopped when the element is disconnected and restarted on reconnect.
* Refresh serial ports only while picker dropdown is open
Emit a picker-opened event from ha-generic-picker and use it in the
serial selector to drive a 5s refresh loop that only runs while the
dropdown is open. The initial load still happens on firstUpdated so
the dropdown has data when the user opens it.
* Allow refreshing picker items while dropdown is open
ha-picker-combo-box caches its items on first update, so the serial
selector's auto-refresh had no effect while the dropdown was open.
Add a public refreshItems() method to re-run getItems and update the
visible list, expose it through ha-generic-picker, and call it from
the serial selector after each refresh.
* Format with prettier
* Categorize serial ports and improve item display
Group ports by type in the serial selector dropdown — integration-provided
(URI-schemed like esphome://), USB (vid/pid), built-in, and unnamed local
ports — with a section header and filter chip for each. Within each section
items are sorted by product name, and unnamed ports (no description or
manufacturer) fall to the last section so they only appear when they
actually exist, which is mostly in dev environments.
Item display now leads with the product description and manufacturer; the
device path, vid:pid, and serial number move to a less prominent secondary
line. ESPHome entries show the ESPHome logo, other integration-provided
ports get a generic connection icon, USB ports a USB icon, and embedded
ports a memory chip icon.
* Rename Unnamed serial port category to Other
* Rename serial selector to serial_port selector
Updated the selector key from `serial` to `serial_port`, renamed the
class to HaSerialPortSelector / SerialPortSelector and the custom
element to `ha-selector-serial_port`, moved translations under
`ui.components.selectors.serial_port`, and renamed the file to
`ha-selector-serial-port.ts`.
---------
Co-authored-by: Claude <noreply@anthropic.com>
* Add use_entity_picture option to picture-entity card
Allow picture-entity cards to display the entity's entity_picture attribute instead of requiring a manually configured image URL. This is particularly useful for entities that dynamically set their entity_picture (e.g., update entities showing component logos, custom integrations, etc.).
The static image configuration remains as a fallback when the entity_picture attribute is not present or when use_entity_picture is not enabled.
Changes:
- Add use_entity_picture boolean option to PictureEntityCardConfig
- Implement logic to check entity_picture attribute when enabled
- Update validation to accept use_entity_picture as valid image source
- Add editor toggle with helper text
- Add translation strings for the new option
* Rename use_entity_picture to show_entity_picture and add entity_picture_local support
Address review feedback:
- Rename use_entity_picture to show_entity_picture to match tile card and badge naming
- Check entity_picture_local first before entity_picture, following tile card pattern
- Update all references in types, card implementation, editor, and translations
* Fix TypeScript error for entity_picture_local access
* Address review feedback - less technical formulation
* Drop unnecessary cast in picture-entity card
Widen stateObj to HassEntity so entity_picture_local is accessible
without an inline cast, matching the tile-card pattern.
---------
Co-authored-by: Petar Petrov <MindFreeze@users.noreply.github.com>
The supervisor_* My redirects (supervisor_store, supervisor_addons,
supervisor_app, supervisor_addon, supervisor_add_addon_repository) had
no component gate, so on Container installations they silently
navigated to broken pages. Gate them on the hassio component and route
the missing-hassio case through the existing no_supervisor error
message, which now links directly to the installation docs.
Also remove the unreachable /hassio/_my_redirect/ fallback that was
left behind by the standalone hassio panel removal (#29132), and
update the no_supervisor string: Home Assistant Supervised is no
longer a supported installation method (see architecture discussion
home-assistant/architecture#1198), only Home Assistant OS.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The standalone hassio panel at /hassio was removed in #29132 and
replaced by the apps panel under /config/apps in #28245. A couple of
references to the old URL path were missed: a dead branch in the
quick-bar My-link builder and a /hassio/ startsWith check that kept
the configuration sidebar item highlighted.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Clean
* Scrollable option
* Refactor
* Remove wrap
* Restore
* Show grab cursor when dragging
* Overflow handling
* Remove extra space on start and end item
* Shrink title
Co-authored-by: Paul Bottein <paul.bottein@gmail.com>
* Increase min width of title, set var
* More specific
* Use 120px min on small layouts
* Try to fix sizing
* No unnessasary vars
* Format
---------
Co-authored-by: Paul Bottein <paul.bottein@gmail.com>
* Add apps navigation group with ingress add-on panels
Add an "Apps" section to the navigation picker that shows all add-ons
with ingress support. Uses the /ingress/panels supervisor endpoint via
a cached collection to fetch add-on titles and icons in a single call.
https://claude.ai/code/session_01F8dUzfSWj8ZwDByVZ45BNj
* Fix no-shadow lint error for panels variable
Rename subscribe callback parameter from `panels` to `data` to avoid
shadowing the outer `panels` variable in _loadNavigationItems.
https://claude.ai/code/session_01F8dUzfSWj8ZwDByVZ45BNj
* Use subscribeOne helper for ingress panels collection
Replace hand-rolled Promise/subscribe/unsub pattern with the existing
subscribeOne utility for cleaner one-shot collection consumption.
https://claude.ai/code/session_01F8dUzfSWj8ZwDByVZ45BNj
* Add explicit type parameter to subscribeOne call
TypeScript cannot infer the generic type through the collection
subscribe chain, resulting in unknown type for panel entries.
https://claude.ai/code/session_01F8dUzfSWj8ZwDByVZ45BNj
* Add subscribeOneCollection helper for collection one-shot reads
Add a new subscribeOneCollection utility that takes a collection
directly instead of requiring the (conn, onChange) function pattern.
Use it in the navigation picker for cleaner ingress panel fetching.
https://claude.ai/code/session_01F8dUzfSWj8ZwDByVZ45BNj
* Use Collection type instead of custom Subscribable interface
https://claude.ai/code/session_01F8dUzfSWj8ZwDByVZ45BNj
* Add ingress panel support to subscribeNavigationPathInfo
* Use app panel variable
* Add tests
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Paul Bottein <paul.bottein@gmail.com>
The PR template includes a checklist item linking to the development
checklist page, but that page only covers core/Python-specific items
(pypi, requirements_all.txt, CODEOWNERS, .strict-typing, Ruff). None
of these apply to the frontend repository.
No frontend-specific development checklist exists, so remove the item
entirely rather than link to irrelevant documentation. The "perfect PR
recommendations" checklist item already covers general PR best practices.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add Automations, Scenes, Scripts, Developer Tools, Integrations,
Devices, and Entities to the "Other routes" section of the navigation
picker. Also resolve these paths with proper labels and icons in
computeNavigationPathInfo so they display correctly everywhere
(shortcut cards, edit overview, etc.).
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* Add per-section theme support
* Fix linting errors: rename property parameter and use dot notation
* Fix TypeScript error: cast to any for __themes property
* Refactor theme application logic for race condition on first load, missing reconnect handling, and the fragile _applyTheme internals https://github.com/home-assistant/frontend/pull/29745
* correct formatting with prettier --write
* Fix theme application logic on reconnect by checking for theme configuration
* Pass section theme to background component for theme variable access
Section backgrounds now receive the section's theme and hass properties,
allowing them to apply the theme via applyThemesOnElement(). This enables
background components to access CSS variables from the section's theme,
particularly --ha-section-background-color when using the 'Default' color option.
Previously, the background component was rendered as a sibling to the section
element and couldn't access theme variables from the section's applied theme.
Now the theme is explicitly passed from hui-sections-view and applied to the
background component itself, making theme cascading work correctly.
* Reorder section settings: theme before background
* Add helper text support to theme selector
Theme selectors can now display helper text below the dropdown. Added helper property to ha-selector-theme and ha-theme-picker components, which is passed through to ha-select. Updated section theme label and added helper text to explain its purpose.
* Address PR review feedback: move theme to end and simplify label
- Move theme selector to end of form (after background section)
- Change label from 'Section theme' to 'Theme' as context is already clear
* Handle theme removal for background
---------
Co-authored-by: Paul Bottein <paul.bottein@gmail.com>
* Alllow setting of toast position
* Switch to use offset
* Create wrapper for toast to offset with automation editor
* Use wrapper
* Add for clipboard pastes
* Make automation toasts dismissable
* Apply for script editor
* Rename
* Resolve add-on name and icon for shortcut card /app/ navigation paths
When a shortcut card or badge navigates to /app/{slug}, fetch the add-on's
panel info (title and icon) from the supervisor ingress panels endpoint and
display it instead of the generic "app" panel fallback.
Adds a cached collection for ingress panel data (title and icon per add-on)
using getCollection, so the data is fetched once per connection.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Simplify
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
If the app config contains a schema field like this one:
```
privileges:
- "list(ALTER|CREATE|...|UPDATE)?"
```
it was rendered incorrectly as a drop-down where only one item can be
selected - but this is wrong because of the preceding `-` denoting it
should be a list containing the listed values. Supervisor translated
this to an entry of type `select` with `multiple: true`. The `multiple`
flag wasn't passed along, with the flag set the field renders as
expected.
Fixes#51533
* Add Music Assistant fallback domain icon
Add mdiMusic as the fallback icon for the music_assistant domain
in FALLBACK_DOMAIN_ICONS, so the integration has a proper icon
when dynamic icons are unavailable.
https://claude.ai/code/session_01GfNQCZL3dF1GXLRfhNRt25
* Revert "Add Music Assistant fallback domain icon"
This reverts commit 130d6eddee.
* Add Music Assistant logo as injectable mdi icon
Add the Music Assistant logo SVG as a special named icon, following
the same pattern as the Home Assistant logo (mdi:home-assistant).
This allows referencing mdi:music-assistant anywhere in the frontend
(e.g., add-on sidebar icon) and it resolves to the Music Assistant
logo SVG path.
https://claude.ai/code/session_01GfNQCZL3dF1GXLRfhNRt25
* Simplify logic to add more in future
---------
Co-authored-by: Claude <noreply@anthropic.com>
* Fix history/sensor cards stuck loading after backend restart
- Add { resubscribe: false } to history subscriptions to prevent
corrupt HistoryStream state on auto-resubscription
- Add connection-status handlers to re-subscribe on reconnect
- Add sentinel pattern to prevent re-entrant async subscriptions
- Add shouldUpdate/updated retry when components become available
- Clear sensor device classes cache on WS error
- Clear _error on reconnect so cards can retry
- Add .catch() on unsubscribe to handle dead subscriptions
* Fix type annotation for callWS in getSensorNumericDeviceClasses
* Address review: type connection-status handlers, add reconnect to history panel
- Use HASSDomEvent<ConnectionStatus> instead of (ev as CustomEvent).detail
for proper type safety on all connection-status handlers
- Add connection-status handler to ha-panel-history so it re-subscribes
after backend restart (addresses concern about resubscribe: false)
* Address review: sentinel pattern, reconnect handling, stale data reset
- Add sentinel pattern to ha-more-info-history, ha-panel-history,
hui-history-graph-card to prevent re-entrant subscription races
- Refactor hui-trend-graph-card-feature from SubscribeMixin to manual
subscription management with connection-status reconnect support
- Reset stale history/statistics data on reconnect in
hui-history-graph-card and hui-map-card before re-subscribing
- Wrap fetchStatistics and getSensorNumericDeviceClasses calls in
ha-panel-history with try/catch to handle errors gracefully
- Chain .catch directly on subscribeHistoryStatesTimeWindow in
hui-trend-graph-card-feature to avoid detached-promise race condition
* Centralize history stream reconnect handling in data layer
Move the reconnect logic from every consumer into `subscribeHistoryStream`
in data/history.ts. The helper listens to the connection's `ready` event
itself, and on reconnect creates a fresh `HistoryStream` and rebuilds
params (so `start_time` for the time-window variant is re-anchored to
"now"). `resubscribe: false` stays as an internal implementation detail.
Removes the duplicated `_handleConnectionStatus` boilerplate and
`connection-status` window listeners from all six history consumers.
* Render subscription errors and make _error reactive
`_error` was declared as a plain string field in hui-graph-header-footer
and ha-more-info-history (non-reactive) and typed as Error/string while
being assigned the WS error object. hui-trend-graph-card-feature had it
reactive but never rendered it.
Align all three with the hui-history-graph-card pattern: reactive
`{ code, message }` and a user-visible error branch in render(). Without
this, a failed subscription would leave the component stuck on a spinner
forever.
---------
Co-authored-by: Petar Petrov <MindFreeze@users.noreply.github.com>
* Add stacked mode to statistics-chart
Allows displaying the entries as stacked lines or stacked bars. This means we can create charts similar to the energy graph cards but with alternate entities.
* Move fillDataGapsAndRoundCaps to components/chart
Now used in statistics-chart too, so move to common chart location.
Re-export in energy-chart-options.ts to minimise changes throughout energy cards.
* Correct order of line/bar in statistics graph card editor
Line and Bar options were unintentionally reversed in the displayed list.
* Support unstacked bar charts in fillDataGapsAndRoundCaps
* Add controls option to media player playback card feature
Allow users to configure which playback controls are shown and in what
order. When controls are explicitly configured, each selected control
is rendered as its own button in the specified order. When no controls
are configured, the original default behavior is preserved.
Also adds a configuration editor for the feature and fixes inline
feature padding in the tile card container.
* Revert padding changes to ha-tile-container
* Use computeMediaControls for default playback buttons
Reuse the shared computeMediaControls function for the default (no
explicit controls) path instead of duplicating the logic. Apply the
narrow filter to both paths via a shared _filterNarrow method.
* Update YAML and Jinja code editor support, support Jinja in YAML
* add autocomplete for ha jinja functions
* Use snippets and better autocomplete for jinja
* Add autocomplete for devices
* Add area, floor, label autocomplete
* Add yaml scalar type highlighter
* Add autocomplete for `states` var
* Add autocomplete for attributes
* Make autocomplete work on id and name
* Add missing functions that can also be used as filter
* Make dialog title a semantic heading element
* Move away from inheriting everything from modal title parent
* Update src/dialogs/generic/dialog-box.ts
---------
Co-authored-by: Paul Bottein <paul.bottein@gmail.com>
* Allow custom dashboard strategies to register for the add dashboard dialog
Adds a window.customDashboardStrategies registration mechanism (mirroring
window.customCards) so third-party strategies can appear in the new dashboard
picker. Only dashboard-level strategies are surfaced; view and section
strategies are excluded. Custom strategies appear in their own section and
are included in search results.
https://claude.ai/code/session_019MXBdWUQrFQfH54QVjbq8y
* Rename custom dashboards heading to community dashboards
https://claude.ai/code/session_019MXBdWUQrFQfH54QVjbq8y
* Consolidate into a single customStrategies registry for all strategy types
The window.customStrategies array now accepts entries with a strategyType
field (dashboard, view, or section). The dialog filters for dashboard
strategies. This allows future use of the same registry for view and
section strategy registration.
https://claude.ai/code/session_019MXBdWUQrFQfH54QVjbq8y
* Space tokens
* Space tokens
* Add support for images
* Allow single image from custom strategy
* Load needed resources for new dashboard dialog
* Preload custom strategies
* Catch potential error
* Reset if error
* Improve typing
* Cache module resources to avoid duplicate loads
* Revert "Cache module resources to avoid duplicate loads"
This reverts commit 87bbcc0451.
* Set a max height for dashboard images (match max height of current core images)
* Remove image support
---------
Co-authored-by: Claude <noreply@anthropic.com>
* Fix base time inputs reportValidity() function
The queryAll selector returns a NodeList not not an array. Need to spread it to an array before we can use every().
* Validate the date range picker time inputs
Enable auto validation to get the nice red underline on invalid values, and then check validity before accepting the input.
* Fix automatic 24hr value conversion in AM/PM format
When using AM/PM, entering a 24 hour value will automatically convert the first time. For example 15 will become 3. However if you then enter 15 again it will stay as 15 and not update.
To fix this, make sure we trigger an update of the input field once the current update cycle is complete.
* Validate time inputs on save not value update
In the value changed callback, the update 24->12hr input correction will not have been updated and therefore they will report invalid.
Add `white-space: pre-line` to the event description style so that
newlines in the calendar event description are rendered correctly
instead of being collapsed into a single line.
2026-03-26 17:07:32 +01:00
864 changed files with 24613 additions and 9484 deletions
A toggle switch can represent two states: on and off.
A toggle switch representing two states: on and off.
## Examples
## Implementation
Switch in on state
### Example usage
<div class="wrapper">
<ha-switch checked></ha-switch>
<ha-switch></ha-switch>
<ha-switch disabled></ha-switch>
<ha-switch disabled checked></ha-switch>
</div>
```html
<ha-switchchecked></ha-switch>
Switch in off state
<ha-switch></ha-switch>
Disabled switch
<ha-switchdisabled></ha-switch>
## CSS variables
<ha-switchdisabledchecked></ha-switch>
```
For the switch / toggle there are always two variables, one for the on / checked state and one for the off / unchecked state.
### API
The track element (background rounded rectangle that the round circular handle travels on) is set to being half transparent, so the final color will also be impacted by the color behind the track.
This component is based on the webawesome switch component.
Check the [webawesome documentation](https://webawesome.com/docs/components/switch/) for more details.
`switch-checked-color` / `switch-unchecked-color`
Set both the color of the round handle and the track behind it. If you want to control them separately, use the variables below instead.
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
