ha-frontend-contexts
GitHub指导Home Assistant前端组件从全局hass对象迁移至细粒度Lit上下文,优化渲染性能、依赖可见性及测试可模拟性。
Trigger Scenarios
Install
npx skills add home-assistant/frontend --skill ha-frontend-contexts -g -y
SKILL.md
Frontmatter
{
"name": "ha-frontend-contexts",
"description": "Home Assistant frontend Lit context and hass migration guidance. Use when adding or changing component state access, replacing hass reads, consuming entity or registry contexts, or reviewing rerender behavior."
}
HA Frontend Contexts
Use this skill when a component reads Home Assistant state, registries, localization, services, config, UI data, connection state, or API helpers.
Goal
Move leaf components away from the broad hass: HomeAssistant object. Broad hass access rerenders components for unrelated changes, hides the data a component depends on, and makes tests harder to mock.
Container components may keep hass when they own it and feed providers. Leaf components should consume the narrowest context that covers their reads.
Core Files
- Context definitions:
src/data/context/index.ts - Entity-scoped consume helpers:
src/common/decorators/consume-context-entry.ts - Transform decorator:
src/common/decorators/transform.ts - Canonical migration example:
src/panels/lovelace/cards/hui-button-card.ts - Providers are wired by
contextMixinonHassBaseEl; consumers do not wire providers manually.
Context Selection
| Context | Replaces |
|---|---|
statesContext |
hass.states |
entitiesContext, devicesContext, areasContext, floorsContext |
hass.entities, hass.devices, hass.areas, hass.floors |
registriesContext |
all four registries together |
servicesContext |
hass.services |
internationalizationContext |
hass.localize, hass.locale, hass.language |
formattersContext |
entity and attribute formatters |
configContext |
hass.config, hass.user, hass.auth, hass.userData |
connectionContext |
hass.connection, hass.connected, hass.debugConnection, hass.hassUrl |
apiContext |
hass.callService, hass.callApi, hass.callApiRaw, hass.callWS, hass.sendWS, hass.fetchWithAuth |
uiContext |
themes, selected theme, panels, sidebar, and UI state |
narrowViewportContext |
narrow-layout boolean |
Lazy contexts subscribe on first consumer and tear down after the last consumer: labelsContext, fullEntitiesContext, configEntriesContext, manifestsContext, triggerDescriptionsContext, and conditionDescriptionsContext.
The single-field contexts such as localizeContext, themesContext, and userContext are deprecated. Use grouped contexts instead.
Consumption Patterns
Use entity-scoped helpers when the component watches an entity ID held on the host:
@state() @consumeEntityState({ entityIdPath: ["_config", "entity"] })
private _stateObj?: HassEntity;
@state() @consumeEntityRegistryEntry({ entityIdPath: ["_config", "entity"] })
private _entity?: EntityRegistryDisplayEntry;
@state() @consumeLocalize()
private _localize!: LocalizeFunc;
Use consumeEntityStates when the host property contains one or more entity IDs. It filters missing entities and preserves the previous record when none of the selected entities changed.
@state() @consumeEntityStates({ entityIdPath: ["_config", "entities"] })
private _stateObjs?: Record<string, HassEntity>;
For a single field from a grouped context, pair @consume with @transform:
@state()
@consume({ context: uiContext, subscribe: true })
@transform<HomeAssistantUI, Themes>({ transformer: ({ themes }) => themes })
private _themes!: Themes;
Use @transform with watch when the transformer depends on a host property, such as a computed entity ID. consumeEntityState and consumeEntityStates only watch the first path segment.
To consume a whole group untransformed, omit @transform and type the field as ContextType<typeof statesContext> or the matching context type.
Review Checklist
- The component consumes the narrowest context needed for the data it reads.
- A broad
hassproperty is kept only when the component is a container or external API requires it. - Entity-scoped reads use the consume helpers rather than ad hoc context transforms.
- Context fields are marked
@state()so updates trigger rendering. - Tests and mocks only provide the data the component actually consumes.
Version History
- 3c7560a Current 2026-08-20 08:57


