Domus UI v1.5.0

v1.5.0 - Domus UI v1.5.0

This is a stable Domus UI release. Features explicitly marked Beta or
Coming later keep their documented limitations.

Added

• Domus Energy Core phase 1: a read-only, vendor-neutral Energy Profile with
  optional grid, solar, home, battery, and wallbox modules. Configured
  modules are distinguished from absent ones and stay visible while offline.

• Energy sensors are normalized to W and % without turning missing data into
  zero, accepting cumulative energy as power, or guessing signed flow
  direction. Derived home consumption is labelled and computed only from
  complete, coherent flows.

• Assisted discovery proposes energy sensors from Home Assistant metadata and
  the Energy dashboard configuration, and reports ambiguous matches for
  confirmation instead of configuring them.

• The Energy page in Consumi now shows the configured installation with real
  Home Assistant values: only the modules that exist, offline modules kept
  visible, and every value marked as measured or derived.

• Administrators can set up and change the energy installation with a guided
  four-step flow (detection, bindings, preview, save) directly on the Energy
  page, without reloading the integration.

• The Energy page is redesigned around a 3D render of the home that matches
  the configured hardware, with subtle live energy flows, a card per
  component, and prepared history and analysis sections that clearly state
  what is not available yet.

• An Impostazioni Energia page replaces the wizard after the first setup:
  it lists the configured modules with their sensors for inline editing and
  re-detection, and stores the electricity tariff (single, two-band or
  three-band ARERA prices, fixed monthly fee, VAT and export price). The
  Energy page shows the current band and its price. The first guided setup
  offers the same tariff fields as an optional step that can be skipped.

• The guided setup asks for the plant type on illustrated tiles (grid only,
  photovoltaic, battery, wallbox and their combinations, or Altro for
  manual setup) and then, on its own step, only for the sensors that type
  needs. A detected plant is summarised with its matched
  entities so it can be confirmed in one step.

• The Energy page lists self-consumption, self-sufficiency, costs, savings and
  the comparison with the previous period as coming soon; no period figure is
  computed on the page.

• Energy components open a details sheet with live figures, estimated power
  paths, the grid's current band and hourly cost and the sensors;
  administrators can jump from there to that module's settings.

• Domus Energy reads installations with several inverters, batteries,
  wallboxes or meters per module. Each device is normalized on its own and the
  module total is their sum, a configured total sensor, or for batteries a
  capacity-weighted charge level. A total missing some devices is reported as
  partial, with how many devices contribute, instead of being shown as
  complete; the live state also lists every device. Existing single-device
  installations read exactly as before.

• Energy meters declared in the energy installation (grid import and export,
  production, consumption, battery charge and discharge, wallbox) are checked
  against Home Assistant's long-term statistics: valid, waiting for their
  first statistics, unavailable, unknown or incompatible. A power or
  temperature sensor is refused as an energy meter, while a meter that is new
  or temporarily unavailable, or a stopped Recorder, never blocks a save.

• Energy detection also proposes installations with several inverters,
  batteries and wallboxes, each with its power sensors and energy meters,
  from the Energy dashboard, the Home Assistant devices and, with low
  confidence, names. Tariff-band meters, plant totals and sensors that could
  overlap are reported for confirmation instead of being summed, and a new
  detection on a configured installation only suggests additions, never
  replacing names, ids, sensors or conventions already chosen.

• The Energy page shows installations with several inverters, batteries or
  wallboxes: each component's details list its devices with their own
  values and states, the total sensor apart from them, and where each value
  comes from (measured, sum of devices, weighted average). A total missing
  some devices says how many report instead of showing their sum as the
  total. Single-device installations look as before.

• Impostazioni Energia edits multi-device installations: names, power
  sensors, sign conventions, energy meters with their verification and
  battery capacities, with a confirmation before removing a device. Every
  save sends the whole installation and keeps the tariff.

• The guided Energy setup configures installations with several inverters,
  batteries, wallboxes and meters, for a first setup or on an existing one:
  each detected device, new sensor, correction or total is added only on
  request, sensors are chosen from a searchable list that leaves out
  incompatible ones, and a summary lists every change and asks to confirm
  unverified meters, summed tariff-band meters and removals before saving.

• The guided Energy setup is now a step-by-step configurator in plain words:
  a welcome, the components of the home as illustrated cards, a detection
  summary per component (ready, to check, waiting, not found), one screen
  per component with device cards and their live readings, recommended
  sensors to accept or change, the sign of a signed meter asked as a simple
  question with a picture, a history step that explains energy meters and
  can be skipped, a visual final check and a confirmation screen. Technical
  names stay available under Dettagli tecnici and Configurazione
  avanzata, and the energy settings use the same device cards.

• Domus Energy can read the energy history of the installation from Home
  Assistant's long-term statistics: production, home consumption (measured or
  computed from complete meters only), grid import and export, battery charge
  and discharge and wallbox, by hour, day, week or month in the Home Assistant
  time zone, also per device. Missing data stays missing instead of becoming
  zero, tariff-band meters are summed only when all of them report, and a
  total meter is never added to its devices. Nothing is stored by Domus.

• The Andamento section of the Energy page shows that history for the last
  24 hours, 7 or 30 days or 12 months: consumption, photovoltaics, grid import
  and export, battery charge and discharge and car charging, only for the
  hardware that has energy meters. Missing hours leave a gap instead of a
  zero, incomplete data and the hour, day or month still in progress are
  marked, a calculated consumption is labelled, and times follow the Home
  Assistant time zone. A plant without meters, meters without statistics yet
  and an unavailable Recorder each get their own message while the live view
  keeps working. The history is read when the page opens or the period
  changes, never on every power change.

• Waste collection can be configured from Settings > Home with fixed weekly
  or multi-week schedules, Home Assistant calendar sources, aliases, special
  dates, per-type icons and colors, and a seven-day preview. Collections are
  published as separate read-only rows in the Domus calendar, including when
  several types are collected on the same day.

• Optional waste reminders run inside Home Assistant at the chosen time on the
  evening before collection. One message aggregates every type due, can target
  one or more notification services, and is suppressed when a configured
  calendar source is unavailable rather than sending incomplete information.

• The public presentation site now includes dedicated Energy and project-update
  sections, derives its card totals from the product catalog, lazy-loads the
  interactive demos, and ships optimized local imagery with automated desktop,
  mobile and performance checks.

Changed

• The release check now budgets the real cost of each part of the app instead
  of mainly the total: startup, Home, each section opened from Home and each
  on-demand feature (Energy setup and settings, card catalog, sidebars, members
  map), raw and gzip, on the build's module graph. Limits are versioned and
  documented in docs/performance-budget.md; the total cap moves from 5.52 MB
  to 6.2 MB because the growth since then is code loaded only when needed.
  The check also rejects circular imports between chunks, and a smoke test
  now opens the distributed production build (Home, Consumi and Energia)
  before the end-to-end suite.
• The presentation website is no longer bundled into the dashboard: the
  internal /beta address of the Home Assistant panel is gone, and the site
  is built on its own with npm run build:site (now checked in CI). The
  dashboard bundle shrinks by about 100 KB.
• Energy values report whether their sensors are still updating: a value
  without a report for 30 minutes (3 hours for battery charge) keeps its
  reading and is shown as not updated since then, never as zero.
• Small negative solar readings at night (down to −50 W) and small balance
  deficits from sensor timing now read 0 W instead of making the
  photovoltaic invalid or the home consumption incoherent; larger values are
  still reported.
• Energy source splits and flows say when they are calculated from the
  meters and when they are only an estimate; the grid's hourly cost includes
  the tariff's VAT.
• The Energy house renders download as AVIF or WebP, about 97% smaller than
  the PNG originals, which remain as fallback.
• The Energy page no longer shows generated charts, sample metrics, or
  demonstration devices.
• Energy components are shown as compact tiles, two by two beside the house
  on desktop, instead of a full-height column of cards.
• Third-party license notices are kept once per bundle...

Domus UI v1.4.0

v1.4.0 - Domus UI v1.4.0

This is a stable Domus UI release. Features explicitly marked Beta or
Coming later keep their documented limitations.

Added

• A Domus Core runtime foundation inside the Home Assistant integration, with
  typed context providers, capabilities, decisions, action outcomes, an event
  bus, and durable audit primitives for future server-side features.
• Local development and preview automatically use the optional mkcert
  certificate pair in .cert/, while CI and developers without certificates
  continue to use HTTP.
• Lazy-loading failures now stay inside a localized recovery boundary instead
  of replacing the dashboard with a permanently incomplete screen.

Changed

• Onboarding, setup persistence tools, the dashboard catalog, and contextual
  device controls are loaded only when needed. MapLibre remains outside the
  Home critical path and is downloaded only when a member location map opens.
• Bundle validation now measures the complete Home critical path and the full
  members-map lazy path, including required shared chunks, instead of checking
  individual files only.
• Release packaging builds with a neutral CSP environment and verifies that
  standalone and HACS artifacts contain the same distribution policy.

Fixed

• The Members card and People panel preserve people that have trackers but no
  current coordinates, while loading the map only when a usable location is
  available.
• The members map no longer remains in an opening loop when MapLibre reports
  recoverable tile or style activity. Blocking initialization errors still
  produce an explicit retry state.
• CARTO map resources are allowed by default in production and HACS CSP only
  through img-src and connect-src; no personal Home Assistant origin,
  wildcard, media permission, or CARTO WebSocket permission is embedded.
• Playwright follows the local HTTPS origin when mkcert certificates are
  present, keeping OAuth callbacks and absolute navigation URLs aligned with
  the test server.

Validation

• The release gate passes TypeScript, 946 unit tests, the production build,
  dependency audit, bundle budgets, and 75 Chromium end-to-end scenarios.
• The complete Home critical path is 1.94 MB raw / 0.55 MB gzip. The separate
  members-map lazy path is 3.82 MB raw / 1.07 MB gzip.

Full Changelog: v1.3.0...v1.4.0

Domus UI v1.3.0

v1.3.0 - Domus UI v1.3.0

This is a stable Domus UI release. Features explicitly marked Beta or
Coming later keep their documented limitations.

Added

• Manage Home Assistant people from Settings > People and access > Members
  (administrators only):
  • link a Home Assistant login to a person, or unlink it. The link dialog
    only offers people without an account and highlights the one with the
    same name. Unlinking never deletes the Home Assistant user;
  • create a person, optionally linked to a login without a person, or
    straight from an account row with its name prefilled. Duplicate names are
    blocked;
  • rename a person and add, change, or remove its photo. Photos are cropped
    to a centered square, resized to 512 px, and stored in Home Assistant like
    the Home Assistant frontend does. The entity id never changes, so
    automations keep working.
• The updated panel bridge (protocol 5) adds the person_links,
  person_create, and person_picture capabilities. It allows person/update
  and person/create for administrators, and photo uploads of JPEG, PNG, or
  WebP images up to 5 MB. With an older bridge the corresponding actions are
  simply hidden.

Changed

• Members, Guest access, and Sharing are now pages of their own under
  /settings/access, with the same header as the other settings pages: one
  title and a single back button, instead of a second title and back link
  inside the page.
• Link, unlink, create, and edit actions use compact icon buttons with
  tooltips.
• The installation guide and README explain the most common reason Domus UI
  does not appear under Add integration: the repository was added to HACS as
  Dashboard instead of Integration, or Home Assistant was not restarted.

Fixed

• The Members card and Settings > Access now list house members from Home
  Assistant people. A person and their login are shown once, and system or
  disabled accounts are hidden. Logins without a person appear in a separate
  "Accounts without a person" section.
• In Edit Mode on desktop, cards can be dragged with the mouse again while
  previewing the tablet or mobile breakpoint.
• Developer mode is now off by default for everyone and can only be turned on
  from Settings. It is stored on the device only, is no longer synchronized or
  included in backups, and requires the developer permission. Users who had it
  on need to enable it again once.
• Option lists in the person dialogs no longer overflow the dialog on long
  labels.

Validation

• Added unit coverage for house member selection, linking, creating, renaming
  people and their photos, the panel bridge allowlist and image upload
  checks, the house access routes, and the developer mode default, plus an
  end-to-end test for mouse dragging in compact previews.
• The total bundle budget grows by 50 KB for Home Assistant people management.

Full Changelog: v1.2.1...v1.3.0

Domus UI v1.2.1

v1.2.1 - Domus UI v1.2.1

This is a stable Domus UI release. Features explicitly marked Beta or
Coming later keep their documented limitations.

Fixed

• Domus UI now falls back to English when neither Home Assistant nor the
  browser uses a language it ships (for example German, Spanish, or Dutch).
  These installations previously opened the first-run setup and the whole
  interface in Italian. Italian and French keep their own translations, and a
  language chosen in Profile still takes precedence.

Project

• New presentation website, in Italian and English, built from the real
  Domus UI cards with demo-only data. It ships as a separate static build
  (npm run build:site) and is not part of the Home Assistant package.
• Added a "Support Domus UI" section to the README and a Sponsor button on the
  repository.

Validation

• Added unit coverage for browser-language detection and the English fallback.
• The release workflow verifies TypeScript, unit tests, production build,
  bundle budgets, dependency audit, Chromium end-to-end tests, HACS packaging,
  checksums, and generated English release notes.

Full Changelog: v1.2.0...v1.2.1

Domus UI v1.2.0

v1.2.0 - Domus UI v1.2.0

This is a stable Domus UI release. Features explicitly marked Beta or
Coming later keep their documented limitations.

Added

• A native editable calendar.domus_ui entity backed by versioned Home
  Assistant storage, so users can create calendar events without installing an
  external calendar provider.
• A responsive Calendar Card with Mini, Standard, and Expanded presets. It
  shows the nearest event in compact layouts, a localized week strip, and
  progressively more events when additional rows are available.
• Direct support for existing Home Assistant calendar.* entities, including
  live agenda subscriptions and create, update, or delete actions whenever the
  selected integration exposes the corresponding Home Assistant features.
• Read-only irrigation schedule events in Calendar. Their source of truth stays
  in Domus Core Irrigation, preventing duplicate or conflicting schedules.
• Italian, English, and French Calendar labels, empty states, editor controls,
  validation messages, and Demo data.
• Adaptive Mini, Standard, and Expanded sizing for Cover, Fan, and Humidifier
  cards, alongside the existing Light Card implementation.

Improved

• Light, Cover, Fan, and Humidifier cards now use deterministic responsive
  matrices across mobile, tablet, and desktop while their content adapts to the
  actual card container.
• Compact controls, sliders, mode selectors, padding, corner radii, and
  theme-aware selection accents are visually consistent across adaptive device
  cards.
• Fan and Humidifier Standard cards expose one useful control in narrow
  layouts; Expanded cards reveal the additional supported controls without
  relying on viewport-only breakpoints.
• The Calendar Card grows its visible agenda progressively when the user adds
  rows, instead of leaving the additional space empty.
• Home Assistant panel navigation validates and forwards Calendar
  subscriptions and event commands through the existing authenticated bridge.

Fixed

• Return to Home Assistant now resolves the native Overview path reliably
  without changing the user's Domus UI startup preference.
• Saved dashboards created by a newer local development build continue to load
  safely on an older installed frontend when a card capability is not yet
  available.
• Intermediate segmented slider steps no longer round the internal edge, which
  keeps Fan and Humidifier controls visually continuous.

Validation

• Added frontend coverage for Calendar queries, subscriptions, adaptive
  variants, progressive event capacity, panel bridge validation, and device
  card sizing contracts.
• Added Home Assistant tests for the Domus UI Calendar store, entity lifecycle,
  editing, irrigation projection, and persistence.
• The release workflow verifies TypeScript, unit tests, production build,
  bundle budgets, dependency audit, Chromium end-to-end tests, HACS packaging,
  checksums, and generated English release notes.

Known limitations

• Recurring-event authoring, multi-calendar aggregation, and the advanced
  month interaction remain planned for a future Calendar iteration.
• Irrigation entries shown in Calendar are intentionally read-only and must be
  changed from Domus Core Irrigation.

Full Changelog: v1.1.0...v1.2.0

Domus UI v1.1.0

v1.1.0 - Domus UI v1.1.0

This is a stable Domus UI release. Features explicitly marked Beta or
Coming later keep their documented limitations.

Added

• Developer-only Adaptive card sizing option in Advanced settings. The
  preference is stored locally per device, defaults to Adaptive, and can switch
  supported cards back to the Legacy sizing engine without changing shared
  Home Assistant layout data.

Improved

• Light Card preset sizing now uses the selected runtime engine only when the
  user explicitly applies Mini, Standard, or Expanded. Existing cards, manual
  resize values, stacks, and saved dashboards are left untouched.
• Unsupported card types remain on the Legacy sizing path even when Adaptive is
  enabled, preparing a conservative one-card-at-a-time rollout.

Fixed

• Domus UI now survives shared layouts saved by a newer local development build
  when an older Home Assistant installation does not yet know a widget kind or
  card capability. Unknown card kinds fall back to safe Sensor sizing instead
  of crashing with resolveDisplayVariant errors.
• Invalid local card-sizing preferences are repaired safely to Adaptive.

Validation

• Added unit coverage for local card-sizing preferences, Developer Mode
  visibility, runtime engine selection, unsupported-card fallback, missing-grid
  fallback, and future widget-kind compatibility.
• Verified targeted unit tests, TypeScript check, and production build.

Full Changelog: v0.1.0...v1.1.0

Domus UI v0.1.0-beta.15

v0.1.0-beta.15 - Domus UI v0.1.0-beta.15

Domus UI is currently in public beta. Back up important Home Assistant
configuration before installing an update.

Added

• Domus Core Irrigation, an authoritative server-side irrigation engine
  built directly into the Domus UI Home Assistant integration. Schedules,
  safety timers, queues, and active sessions now continue to run when every
  browser and Domus UI screen is closed.
• A versioned Home Assistant Store for irrigation configuration and runtime
  state, with optimistic revisions and idempotent command identifiers.
• Authenticated WebSocket commands and native Home Assistant actions for
  starting or stopping a zone, stopping the complete system, and pausing or
  resuming irrigation. Action descriptions are available in Italian, English,
  and French.
• A server-owned scheduler using Home Assistant local time, duplicate-run
  protection across daylight-saving transitions, configurable concurrency,
  and a FIFO queue when all available slots are occupied.
• A compact activity card on the Irrigation overview and a dedicated Activity
  page for completed, stopped, skipped, interrupted, and failed sessions.
• A guided migration for configurations created by earlier Domus UI betas. Only
  recognizable legacy irrigation automations are disabled and presented for
  review and manual removal.
• A localized end-of-onboarding choice between keeping the prepared starter
  dashboard and beginning with an intentionally empty canvas, plus an explicit
  starter-template restore action in Settings.
• A redesigned contextual Weather experience with hourly or daily temperature,
  animated humidity, pressure, UV, wind, sunrise/sunset, localized conditions,
  and capability-based modules that disappear when data is unavailable.

Safety and reliability

• Real irrigation zones accept only valve.* and switch.* actuators;
  input_boolean.* remains isolated to Demo mode.
• Manual and scheduled sessions have a server-side deadline and watchdog, with
  configurable durations from 5 to 60 minutes.
• Parallel operation defaults to one zone and requires an explicit hydraulic
  capacity acknowledgement before a higher limit can be saved.
• Rain protection is fail-closed when enabled: an unavailable rain sensor blocks
  new starts and closes active zones. Rain during a cycle can either stop it
  immediately or allow the active cycle to finish.
• Pause closes active actuators while preserving remaining time for an explicit
  resume. Stop closes everything, clears queued work, and blocks schedules until
  the system is enabled again.
• Failed actuator confirmation is retried; an unconfirmed close moves the engine
  to fault and creates a persistent Home Assistant Repair issue.
• Integration reloads and Home Assistant restarts never resume old cycles:
  previously active actuators are closed and their sessions are recorded as
  interrupted.
• Owner/Admin permissions protect configuration changes, while every operational
  command re-checks the Home Assistant user's permission for its actuator.

Improved

• Irrigation configuration, rain-protection changes, sessions, countdowns,
  queue state, and anomalies synchronize between open clients through push
  updates instead of browser polling.
• New zones can be prepared while other zones are running; changes that would
  affect an active actuator or live safety policy are rejected with a clear,
  localized explanation.
• Manual zone controls now expose queued, opening, running, closing, and paused
  states consistently with the server, including remaining-time countdowns.
• Consumption history is loaded on the overview as well as the detailed page.
  Its chart now has stable dimensions and uses a per-user, per-server session
  cache so known data renders immediately while stale values refresh in the
  background.
• Irrigation overview spacing, warning banners, configuration access, calendar,
  zone cards, activity history, and responsive mobile/desktop layouts have been
  refined.

Fixed

• Opening Irrigation now always starts from the Overview instead of reusing a
  stale nested route such as Consumption.
• Rain-protection changes now propagate live to other open Domus UI clients.
• Paused sessions retain their backend remaining time instead of resetting the
  zone timer in the interface.
• Safe zone additions are no longer blocked merely because another zone is
  currently irrigating.
• Irrigation command failures now surface the reason returned by Home Assistant
  instead of a generic API error.
• The overview consumption bars no longer collapse inside an auto-sized card.

Validation performed

• Real Home Assistant checks completed with a switch.* actuator and a binary
  rain sensor: configuration persistence, reload, manual start/stop, rain block,
  rain interruption, single-slot FIFO queue, parallel capacity, global
  pause/resume, and live multi-client rain-setting synchronization.
• Automated backend coverage includes Store normalization, revisions,
  idempotency, WebSocket and action routing, permissions, scheduling, queueing,
  rain policies, actuator timeouts, close retries, fault recovery, reload, and
  restart safety.
• Frontend coverage includes migration, unavailable backend, configuration
  conflicts, active-session editing, countdown behavior, activity history,
  consumption caching, and Italian/English/French interface contracts.

Known limitations

• This first Core release does not yet include pump control, flow monitoring,
  weather- or soil-based automatic adjustment, Cycle & Soak, or robot lawn
  mower support.
• A host power outage cannot close a powered valve while Home Assistant is
  offline. Critical installations still require a hardware auto-off or local
  watchdog and should not rely solely on beta software.

Full Changelog: v0.1.0-beta.14...v0.1.0-beta.15

Domus UI v0.1.0

v0.1.0 - Domus UI v0.1.0

This is a stable Domus UI release. Features explicitly marked Beta or
Coming later keep their documented limitations.

Stable scope

• Domus UI reaches its first stable release for the Home dashboard and visual
  builder, Rooms, Security, Consumption, Profile, Settings, shared layouts,
  backups, revision history, and the HACS installation lifecycle.
• Italian, English, and French remain supported across the stable routes,
  onboarding, dialogs, contextual controls, errors, and accessible labels.
• Incomplete workspaces remain unavailable behind an explicit Coming later
  screen instead of exposing partial controls.

Added

• A per-user Home Assistant startup preference in Profile. Users can choose to
  open Domus UI after signing in without changing other frontend preferences;
  disabling it restores the previous available panel or the Home Assistant
  system default.
• A separate Return to Home Assistant action in the desktop/tablet sidebar
  and mobile drawer. It opens the native Home Assistant Overview without
  disabling the Domus UI startup preference or disconnecting the account.
• The same return action is available during local development when Domus UI is
  connected to a real Home Assistant instance.

Improved

• The panel bridge now exposes an explicit, allowlisted host-navigation
  capability and keeps iframe navigation separate from WebSocket commands and
  stored frontend preferences.
• Public documentation, installation guidance, release notes, and feature
  status now distinguish the stable Domus UI surface from features that are
  still in Beta or planned.

Validation

• TypeScript, unit tests, production build, bundle budget, dependency audit,
  release packaging, and Chromium end-to-end tests are required by the release
  workflow before GitHub and HACS assets are published.
• The Home Assistant panel bridge distribution contract verifies that the
  navigation action is present in the generated HACS frontend bundle.

Known limitations

• Domus Core Irrigation remains explicitly in Beta while additional real-world
  actuator and failure-path validation continues. It is not part of the stable
  unattended-operation guarantee.
• Automations, Utility Room, Pool & Spa, Calendar, Map, Lists, QR sharing,
  device profiles, and Domus Core Security remain planned or Coming later.
• Domus UI is not a certified alarm, security, irrigation, or safety system.

Full Changelog: v0.1.0-beta.15...v0.1.0

Domus UI v0.1.0-beta.14

v0.1.0-beta.14 - Domus UI v0.1.0-beta.14

Domus UI is currently in public beta. Back up important Home Assistant
configuration before installing an update.

Added

• Essential multilingual experience in Italian, English, and French, with the
  initial language detected from Home Assistant or the browser and an explicit
  per-device language selector in Profile.
• Complete translations for onboarding and reconnection, Home, Rooms,
  Settings, App Library, and the Irrigation workspace, including their nested
  pages, dialogs, empty states, errors, and accessible labels.
• Localized Coming soon protection for routes that are not ready to offer a
  consistent translated experience yet.
• English release notes generated automatically for GitHub and the HACS update
  preview, plus a French Home Assistant Config Flow translation.

Improved

• Home Assistant entity states, dates, times, and numbers now follow the active
  language without changing user-defined entity, device, area, or person names.
• Apple devices now use the native system font stack consistently with Windows
  and Android.
• App Library and Irrigation navigation, configuration, calendar, consumption,
  zone management, and demo previews now share the same localization contract.
• Release checks now audit untranslated strings and test a deterministic Italian
  browser locale while retaining explicit English and French coverage.

Fixed

• Compatibility with Home Assistant versions that do not expose
  frontend.async_panel_exists through the same API.
• Tablet navigation no longer maps the App Library icon to the Home route when
  the sidebar switches to its compact layout.
• Legacy test selectors and accessibility contracts now follow the localized
  navigation and control labels.

Full Changelog: v0.1.0-beta.13...v0.1.0-beta.14

v0.1.0-beta.13

Full Changelog: v0.1.0-beta.12...v0.1.0-beta.13