Skip to content

Scheduling Manager v2.0.0: canonical naming and migration

Choose a tag to compare

@flatsheep flatsheep released this 23 Oct 23:34

Breaking change: one-time 1.x migration required

Scheduling Manager now uses scheduling_manager consistently for its
integration folder, HA domain, actions, WebSocket commands and saved-data ownership.
The old heating-specific runtime names and card aliases have been removed.

Read the migration guide
before updating. Do not delete the old integration entry first.

Upgrading from 1.x

  1. Update in HACS or install the attached ZIP, then restart Home Assistant.
  2. Open Settings → Devices & services → Add integration → Scheduling Manager
    and confirm setup. The new integration detects and transfers the existing data.
  3. Refresh the dashboard and update old card/action/entity references as needed.
  4. Restart HA once more when the migration notice appears. This verification
    restart commits HA's registry changes before the stopped old entry and Store
    are safely retired. The notice clears automatically.
  5. Once migration has completed, remove the obsolete
    custom_components/heating_schedule_manager/ folder if it remains, including
    after a HACS update. Keep custom_components/scheduling_manager/ and leave
    unrelated integrations alone.

If the old entry appears unavailable after the package-folder rename, continue by
adding the new integration as above. Keep the old entry until migration completes.

If HACS reports a missing manifest or still uses the old folder, reload HACS under
Settings → Devices & services, then select/download 2.0 again to refresh its
cached repository path. The attached ZIP is available as a manual-install fallback.

Renamed interfaces

1.x 2.0
Integration/action domain heating_schedule_manager scheduling_manager
WebSocket prefix heating_schedule_manager/ scheduling_manager/
Default Away entity switch.heating_schedule_away switch.scheduling_manager_away
custom:heating-schedule-manager-card custom:scheduling-manager-card

Update automation/script calls, templates, YAML dashboards and external clients
that use those old names. The existing schedule_manager.… boolean control paths
and UUID references retain their format.

What migration preserves

  • Saved schedules, weekday groups, bands and their UUIDs.
  • Away/timed-disable settings, pending commands and acknowledgement progress.
  • Selected one-off cycles, without replaying Start or rearming a completed cycle.
  • HA entity-registry identities and user customisations.

Device IDs change: HA cannot move native parent/child devices between
integration domains. The migration recreates that hierarchy and transfers its
names, areas, labels, disabled preferences and entity associations. Update any
device-based automation targets. Migration does not rewrite arbitrary user YAML
or external dependencies.

The handover is resumable after interrupted Store or registry operations. It uses
supported HA APIs and never overwrites unrelated new-domain schedules.

Visual improvement

Bands now grey out when their parent sub-schedule is disabled, including day
previews. Re-enabling the group or reaching its timed expiry restores each band's
own visual state without changing its individual enable preference. One-offs keep
their red marker borders and calendar-clock badge.

Installation

Fresh installations use the single canonical folder
custom_components/scheduling_manager/. The matching 2.0.0 dashboard card is
bundled and loads automatically. HACS custom-repository installation remains
supported; default-catalogue submission is unchanged.

The attached ZIP is the manual-install fallback and includes public guides,
screenshots and license notices. Minimum HA version remains 2026.7.0.

Validation

  • GitHub CI passed
    for all four HA versions, frontend, HACS validation and hassfest.
  • 230 backend tests across 12 suites passed on HA 2026.7.0, 2026.8.1,
    2026.9.4 and 2026.10.1, including 16 migration cases.
  • 26 frontend unit tests and 84 Chromium tests passed.
  • Combined local line/branch coverage: 96.26%; the 95.1% gate is unchanged.
  • Ruff, selected formatting, mypy, official hassfest, documentation-link and
    deterministic-package checks passed.
  • Local production migration verified the saved model, 43 entity-registry
    identities, 18-device customisations and 34 Disabled controls after two authorised
    restarts, with no scheduler errors. No physical-device tests were performed.

README ·
Migration guide ·
Test results

Full changelog: v1.12.0...v2.0.0