2.2.6

The Apollo mmWave dashboard is created once, when you add the integration,
and is no longer recreated or rewritten at every start. Startup no longer does
disk work on Home Assistant's event loop, and old zone locations no longer
bring a deprecation warning. Nothing needs changing by hand unless your
Lovelace resources are managed in YAML (replace both ?v= URLs; see
Lovelace resources).

• The dashboard is created once. Adding Apollo mmWave creates the
  dashboard right then, if you leave its box ticked, and Home Assistant no
  longer recreates, rewrites or deletes it at restart or when the integration
  reloads. New dashboards are for administrators only unless you untick
  Only administrators can see it; change that later in the dashboard's
  settings under Settings → Dashboards. A dashboard you already have is left
  as it is, including who can see it. With the dashboard turned off, setup
  no longer deletes a dashboard you made yourself on /apollo-mmwave. To add
  or remove the dashboard, or choose its devices, open the integration's
  options (Settings → Devices & services → Apollo mmWave → Configure); see
  The Apollo mmWave dashboard.
• Only administrators can change zones. The apollo_mmwave.update_zone
  action, which the zone map card uses to save, now refuses users who are not
  administrators, so they can no longer change zones or create and remove zone
  entities. They still see the zones and their presence sensors, and the card
  answers a change with "Could not save". Automations are not affected.
• Startup stays off the event loop. The startup check for the bundled
  card files no longer touches the disk on Home Assistant's event loop, and
  the integration now loads all of its own code when Home Assistant imports
  it, instead of importing modules on the event loop partway through setup.
• No deprecation warning for old zone locations. Matching a 1.x zone
  location to its radar by name no longer uses a device registry call that
  Home Assistant is retiring (2026.10 warns about it in the log). It also
  matches only ESPHome devices, so a router integration's device with the
  same name cannot take the zones.

If HACS shows Apollo mmWave installed as 4263323, 5299868 or 96245a2, open it
in HACS, choose Redownload, pick 2.2.6, then restart. Those commit codes
read as very high version numbers, so HACS would not offer releases
otherwise.

New to Apollo mmWave? Install it with HACS by following the README. Full changes: CHANGELOG.md.