Skip to content

Releases

Scheduling Manager v2.0.5: centred one-off icons on iPad

Choose a tag to compare

@flatsheep flatsheep released this 02 Nov 18:51

v2.0.5 — centred one-off icons on iPad

Fix

The calendar-clock icon above a one-off time band could appear off-centre inside
its red circle in the Home Assistant iPad app. The previous badge placed an HTML
Home Assistant icon inside an SVG foreignObject, then applied CSS scaling.
This mixed HTML/SVG rendering is sensitive to browser-specific positioning.

The badge now draws the calendar-clock directly as a native SVG path. The circle
and icon share the same coordinate system, and alignment uses the artwork's
actual bounds rather than the slightly asymmetric 24px icon viewport. This
applies to both active one-off bands and preview bands.

This is a visual frontend fix; schedule execution, saved schedules and device
commands are unchanged. The integration, card and outer/inner loader versions
are all updated to 2.0.5, so the packaged update requests the new frontend.

Updating

  1. In HACS, open Scheduling Manager and update/download v2.0.5.
  2. Restart Home Assistant to load the integration's new versioned frontend URL.
  3. Refresh the dashboard or reopen the Home Assistant app on your iPad.
  4. If the old badge persists, open Settings → Companion App → Debugging →
    Reset frontend cache
    , then reopen the dashboard. Menu wording may vary with
    the app version.

For manual installations, use scheduling-manager-2.0.5.zip, replace the
custom_components/scheduling_manager directory, then follow steps 2–4. Existing
schedules are retained; do not remove/re-add the integration.

Verification

  • Production frontend build and all 26 frontend unit tests pass.
  • All 89 browser tests pass, including one-off creation/editing, preview styling
    and artwork alignment for active/preview badges at 768px and 1024px widths.
  • Both frontend registration/payload checks and the HACS-only installation test
    pass in an isolated Home Assistant 2026.10.1 container.
  • The locally served bundle was checked in the actual Home Assistant frontend
    using Chromium: zero horizontal/vertical artwork offset, with no foreignObject.
  • Direct iPad/WebKit visual confirmation remains a user-device check; WebKit
    automation is unavailable on the development host.

Scheduling Manager v2.0.4: trimmed normal and HiDPI icons

Choose a tag to compare

@flatsheep flatsheep released this 25 Oct 10:04

Improved normal and high-resolution icons

This branding-only patch ships the original calendar/timeline design in the
integration's own brand/ directory, following the supported custom-integration
branding route.

  • Trim unnecessary outer transparent padding while retaining the calendar and
    orange/blue schedule-band design.
  • Provide 256 × 256 icon.png and 512 × 512 icon@2x.png.
  • Encode both as transparent, losslessly compressed, Adam7-interlaced PNGs.
  • Generate both sizes reproducibly from the same geometry without adding build
    dependencies. File sizes are only 1,700 bytes and 4,217 bytes.

Scheduling behaviour and dashboard functionality are unchanged from v2.0.3.
Integration/card versions and loader cache keys are aligned at 2.0.4.

Icon availability

Home Assistant has supported locally shipped custom-integration brand assets since
2026.3. Update the integration to v2.0.4 to install these assets. A separate
entry in the legacy central custom-integration brands directory is not required
for this route.

Older HACS versions that still fetch icons directly from the legacy brands CDN
may continue to show a placeholder in their catalogue UI. Publishing local images
does not populate that legacy CDN; icon visibility depends on the consuming
HA/HACS frontend and its image cache.

Minimum Home Assistant version remains 2026.7.0. The attached ZIP is the
manual-install fallback. No new migration is required for existing 2.0 users.

Verification

  • Release-commit CI
    covers four supported HA versions, frontend, HACS and hassfest.
  • Independent Pillow decoding verifies image integrity, exact dimensions,
    transparency, full-canvas alpha bounds and matching normal/HiDPI artwork.
  • Repeated generation produces identical PNGs; focused generator lint passes.
  • Local production frontend build, 26 unit tests and both HA frontend
    registration/payload checks pass. All 88 browser tests pass locally and in CI.
  • The deterministic 68-file ZIP includes both icons and matches the sources;
    archive CRCs/paths and all 23 supplied screenshots were checked.

Full changelog: v2.0.3...v2.0.4

Scheduling Manager v2.0.3: HACS installation and README presentation

Choose a tag to compare

@flatsheep flatsheep released this 25 Oct 09:32

Updated README for HACS

Scheduling Manager is now included in HACS's default catalogue. This documentation
patch packages the README changes so they are available when HACS reads a release,
rather than only appearing on GitHub's main branch.

  • Lead installation with searching for Scheduling Manager in HACS.
  • Keep custom-repository instructions as a fallback.
  • Make the coffee button 20% smaller and right-aligned.
  • Move the Open in HACS shortcut into the Install section.
  • Clarify that existing custom-repository installations do not need removing or
    re-adding after default-catalogue inclusion.

Scheduling behaviour and dashboard functionality are unchanged from v2.0.2.
Integration/card versions and loader cache keys are aligned at 2.0.3.

Seeing the changes in HACS

HACS may display documentation from the installed version. If it still shows the
old README, refresh repository information and update to v2.0.3 through HACS.
Publishing this release does not rewrite the README at the existing v2.0.2 tag.

The minimum Home Assistant version remains 2026.7.0. The attached ZIP is the
manual-install fallback. No new migration is required for existing 2.0 users.

Verification

  • Release-commit CI:
    four supported HA versions, frontend, HACS and hassfest.
  • Local production frontend build and all 26 unit tests passed.
  • Three focused HA checks passed: frontend registration/payload consistency and
    the isolated HACS-only installation/served-card check.
  • The deterministic 67-file ZIP matches the sources, includes the updated README,
    preserves the 23 supplied screenshots, and passes ZIP CRC/path checks.

Full changelog: v2.0.2...v2.0.3

Scheduling Manager v2.0.2: async timezone loading and timeout recovery

Choose a tag to compare

@flatsheep flatsheep released this 24 Oct 21:43

Async-safe scheduling and reliable timeout recovery

This patch addresses the Home Assistant event-loop blocking issue identified in
the HACS review and includes the dashboard recovery fixes already on main.

Backend fixes

  • Resolve the configured timezone with await dt_util.async_get_time_zone(...)
    and pass the resolved object through scheduling, one-offs, activity, solar and
    local-deadline helpers. No integration module constructs ZoneInfo directly.
  • Refresh the resolved timezone through the serialized environment cutover,
    discarding superseded resolutions and retaining consistent state if saving fails.
  • Preload Astral through Home Assistant's async import helper before synchronous
    solar calculations, avoiding conditional first-use imports on the event loop.
  • Treat exceptions with empty messages, including service timeouts, as failures.
    Failed one-off Stops remain pending across restart and complete on recovery
    without repeating Start. Empty-message storage failures remain visible too.

Dashboard fixes

  • Recover automatically after Home Assistant restarts, including when the browser
    reuses its connection object. Reads and subscriptions retry with backoff and
    show a friendly waiting status while the integration starts.
  • Avoid a synthetic touch click accidentally applying a newly opened time popup.
  • Version both the registered loader URL and its inner card import as 2.0.2
    so the release can replace a cached older loader.

Updating

For an existing 2.0 installation, update through HACS, restart Home Assistant once,
then refresh the dashboard. No integration re-add or domain migration is needed.

For upgrades from 1.x, follow the
one-time migration guide.
Do not delete the old integration entry before migration.

Integration and card versions are both 2.0.2. Minimum Home Assistant version
remains 2026.7.0. The attached ZIP is the manual-install fallback; HACS installs
the integration directory, including its bundled card.

Verification

  • Release-commit CI
    covers HA 2026.7.0, 2026.8.1, 2026.9.4 and 2026.10.1, frontend,
    HACS and hassfest.
  • 237 backend tests, 26 frontend unit tests and 88 Chromium tests.
  • Fresh-process native file-I/O audits cover cold timezone/Astral loading,
    Save, public/activity reads, local deadlines and timezone changes. The exercised
    paths have no integration loop file I/O, integration warnings/errors or HA
    blocking-call reports on all four supported versions.
  • Local combined line/branch coverage on HA 2026.8.1: 96.29%, above the
    unchanged 95.1% gate. Ruff, selected formatting, mypy and official hassfest pass.
  • Isolated HACS-only installation/served-card check passes. The deterministic
    release ZIP contains matching payloads, public documentation and license notices;
    all ZIP CRCs and paths were validated.
  • Verification uses temporary HA configurations and mocked services. This release
    has not been deployed to the maintainer's production HA instance.

Full changelog: v2.0.1...v2.0.2

Scheduling Manager v2.0.1: activity and Away device visibility

Choose a tag to compare

@flatsheep flatsheep released this 24 Oct 08:28

Activity and Away are now visible on integration devices

This patch fixes device grouping that previously left schedule activity sensors
and the Away switch unassigned, making device pages appear to contain only
Disabled controls.

  • Each schedule device now groups its read-only Active binary sensor
    alongside its Disabled switch.
  • A separate Scheduling Manager service device contains the global Away
    switch (switch.scheduling_manager_away).
  • Activity sensors use the clearer Active label while retaining their
    existing entity IDs and unique IDs.
  • Existing entity names, icons, areas, labels and disabled preferences are
    preserved. This changes grouping, not scheduling behaviour.

Find the entities under Settings → Devices & services → Scheduling Manager,
then open a schedule device or the manager device. They remain available in HA's
Entities list and work independently of the dashboard card.

Updating

Already on 2.0: update through HACS, restart Home Assistant once, and
refresh the HA page. The associations are updated automatically; no migration
or integration re-add is needed.

Upgrading from 1.x: follow the
one-time migration guide.
The domain rename and interface changes introduced in 2.0 still apply. Do not
delete the old integration entry before migration.

Integration and card versions are both 2.0.1. The attached ZIP is the
manual-install fallback. Minimum Home Assistant version remains 2026.7.0.

Verification

  • GitHub CI passed
    on all four supported HA versions, plus frontend, HACS and hassfest jobs:
    231 backend tests, 26 frontend unit tests and 84 Chromium tests.
  • Focused HA checks cover existing-entity attachment, stable identities and
    customisations, Active/Away state, hierarchy cleanup, migration and HA 2026.7
    compatibility.
  • Local deployment preserved the saved model and all 43 entity-registry
    identities/customisations. All eight activity sensors were correctly grouped;
    Away appeared on the new manager device, for 19 devices total. Native states
    matched the scheduler, with no scheduler errors or physical-device tests.
  • Packaging includes the matching bundled card, public documentation and notices.

Full changelog: v2.0.0...v2.0.1

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

Scheduling Manager v1.12.0: one-offs and sub-schedule controls

Choose a tag to compare

@flatsheep flatsheep released this 23 Oct 21:22

What's new

One-off time bands

  • Tick One-off when creating a time band for a single Start/Stop cycle.
  • Red marker borders and a calendar-clock badge distinguish temporary bands.
  • Completion permanently removes the shared band from every associated weekday.
  • Creating a band during an eligible interval starts it immediately; creating it
    after Stop waits for the next selected day.
  • Running bands remain editable and deletable. Time edits keep the same cycle
    without repeating Start; deletion cancels remaining work without device commands.
  • Durable recovery handles downtime and failed Stops without starting another cycle.
  • No individual Disabled switch or automation path is created for a one-off.

Sub-schedule controls

  • Pause a named day group permanently or until a chosen date and time.
  • Disabled weekdays have black backgrounds, white names and red crosses.
  • Native Disabled switches cover schedules, sub-schedules and recurring bands.
  • HA 2026.9+ groups sub-schedules as native child devices; earlier supported
    releases retain flat service-device compatibility.
  • UUID-stable control paths survive renames/time edits; legacy On/Off paths remain supported.

Shorter, illustrated documentation

The README is about 72% shorter,
with seven updated maintainer-supplied images. Detailed user guidance, one-off
behaviour and development instructions now have dedicated guides.

Installation and upgrading

Update Scheduling Manager in HACS, restart Home Assistant, then refresh
your dashboard or reopen the companion app. The integration and card are both
1.12.0; existing schedules, identities and user customisations are retained.

For manual installation, extract the attached ZIP's
custom_components/heating_schedule_manager/ folder into your HA configuration.
The bundled card loads automatically; no separate dashboard resource is needed.

Minimum HA version: 2026.7.0. The compatibility matrix covers 2026.7.0,
2026.8.1, 2026.9.4 and 2026.10.1
. HACS default-catalogue submission is unchanged.

Validation

  • GitHub CI passed
    on all four supported HA versions, plus frontend, HACS and hassfest jobs.
  • 214 backend tests, including 32 one-off cases; local combined coverage 96.47%.
  • 26 frontend unit tests and 82 Chromium tests.
  • Ruff, selected formatting, mypy and official hassfest.
  • Deterministic manual-install ZIP with documentation, original screenshots,
    bundled frontend and notices; no local HA data or caches.

See test results
and one-off behaviour
for recovery semantics and delivery limitations.

Full changelog: v1.11.0...v1.12.0

Scheduling Manager v1.11.0: programmatic schedule controls

Choose a tag to compare

@flatsheep flatsheep released this 22 Oct 21:58

Programmatic schedule and time-band controls

Control schedules and bands from Home Assistant automations, scripts and API clients.

  • Every schedule and band has a native Disabled switch: on = disabled,
    off = enabled. Sub-schedules do not have enable/disable controls.
  • heating_schedule_manager.get_disabled reads a boolean state. Omit path
    to discover the current schedule and band paths.
  • heating_schedule_manager.set_disabled accepts a path and disabled: true
    or false. True disables permanently; false cancels any timed band disable.
  • Enabling an active band applies its start settings. Schedule-level disable
    and applicable Away still take precedence.
  • A disabled parent makes its bands report disabled without changing their own
    preferences. Re-enabling the parent preserves individually disabled bands.
  • Readable paths follow names and configured times. Native switch identities
    remain tied to UUIDs across renames; duplicate names receive distinguishing suffixes.
  • User-context writes require an administrator. Internal HA automation calls
    are supported, and path reads respect the requesting user's entity access.

Example band control:

action: heating_schedule_manager.set_disabled
data:
  path: schedule_manager.schedule1.weekdays.band-on-0700-off-1000.disabled
  disabled: false

The README includes native-switch, discovery, read and write examples, plus
parent-state behaviour, naming rules and solar/unnamed-band conventions.

Included versions

  • Dashboard card: 1.11.0
  • Home Assistant integration: 1.11.0
  • Minimum Home Assistant version: 2026.7.0

Update or install

Download/update Scheduling Manager through HACS, restart Home Assistant, then
refresh your dashboard or reopen the companion app. Existing schedules are retained;
the new Disabled switches are created for your saved schedules and bands.

Without HACS, extract the attached ZIP's custom_components/heating_schedule_manager/
folder into your HA configuration's custom_components/ directory and restart HA.
For an existing installation, keep the integration entry and saved schedules.
The card is bundled and loads automatically.

HACS default-catalogue inclusion remains a separate submission. Until accepted,
use the custom repository instructions or Add to HACS badge in the README.

Verification

All seven CI jobs passed on the release commit:
GitHub Actions results.

  • Nine backend suites across HA 2026.7.0, 2026.8.1, 2026.9.4 and 2026.10.1.
  • Frontend build, 23 unit tests and 72 Chromium browser tests.
  • Ruff, configured formatting, gradual mypy, official hassfest and HACS validation.
  • 12 focused path/control cases and four real HA lifecycle cases cover
    parent inheritance, timers, active starts, persistence failures, identities,
    permissions, filtered reads, deletion, reloads and control-target exclusion.
  • Local combined backend line/branch coverage on HA 2026.8.1: 96.33%.

Write behaviour was tested with mocked devices in isolated HA configurations.
Local deployment checks confirmed startup, preserved saved schedules and matching
native/boolean API states, without toggling production devices. See TEST_RESULTS.md
for test scope and limitations.

Manual-install ZIP SHA256

33b561b3940642cb76eb0c57ab57ccf7f82fbc2c9f0b3aed92f8d59b02c63f82  scheduling-manager-1.11.0.zip

Licensed under GPL-3.0-only; bundled third-party notices are included.

Scheduling Manager v1.10.0: individual time-band controls

Choose a tag to compare

@flatsheep flatsheep released this 22 Oct 20:59

Individual time-band controls

Pause one time band without disabling the whole schedule.

  • Choose Disabled in the time-band popup, then Permanent or Until….
  • Disabled bands stay visible in dark grey with a Disabled label. Their start
    and end transitions are ignored while disabled.
  • To restore a band, select Enabled, then Apply → Save. If the band is
    active when saved, its start settings are applied. Outside its active time,
    enabling restores future transitions without sending a start command.
  • Timed expiry also applies the start settings if the band is active, including
    restart recovery. Schedule-level disable and applicable Away still take precedence.
  • Disabling an active band leaves device settings unchanged.

The README documents this workflow and now includes a visible Install without
HACS
section linked to the attached manual-install ZIP.

Included versions

  • Dashboard card: 1.10.0
  • Home Assistant integration: 1.10.0
  • Minimum Home Assistant version: 2026.7.0

Update or install

Download/update Scheduling Manager through HACS, restart Home Assistant, and
refresh your dashboard or reopen the companion app. Existing schedules are retained.
The card is included and loads automatically.

Without HACS, extract the ZIP's custom_components/heating_schedule_manager/
folder into your HA configuration's custom_components/ directory, restart HA,
then add the integration and card. For an existing installation, replace the
integration folder while keeping the existing integration and saved schedules.

HACS default-catalogue inclusion remains a separate submission. Until accepted,
use the custom repository instructions or Add to HACS badge in the README.

Verification

All seven CI jobs passed on the release commit:
GitHub Actions results.

  • Backend suites on HA 2026.7.0, 2026.8.1, 2026.9.4 and 2026.10.1.
  • Frontend production build, 23 unit tests and 72 Chromium browser tests.
  • Ruff, configured formatting, gradual mypy, official hassfest and HACS validation.
  • 33 focused band tests, including active-only resumption, timed expiry,
    persistence failures, DST/solar handling, restart recovery and duplicate-start guards.
  • Local combined backend line/branch coverage on HA 2026.8.1: 96.33%.

Automated checks use mocked devices and a synthetic browser dashboard. Installation
startup was checked in the maintainer's HA instance; these checks do not measure
physical-device outcomes. See TEST_RESULTS.md for scope and limitations.

Manual-install ZIP SHA256

9575f7fcd6bd69eeb738f576cac98367bdfd288332e4fece1cd620e2c3be447c  scheduling-manager-1.10.0.zip

Licensed under GPL-3.0-only; bundled third-party notices are included.

Scheduling Manager v1.9.19

Choose a tag to compare

@flatsheep flatsheep released this 20 Oct 22:07

First public release

A clearer way to manage your Home Assistant schedules.

Scheduling Manager brings heating, hot water, lighting and other supported
devices into one visual timetable, with aligned timelines and a shared
current-time marker.

Included versions

  • Dashboard card: 1.9.19
  • Home Assistant integration: 1.9.4
  • Minimum Home Assistant version: 2026.7.0

Features

  • Multiple devices per schedule, with individual start/end settings.
  • Named sub-schedules for individual days or groups of days, with multiple bands.
  • Fixed and solar endpoints, offsets, draggable time markers and exact-time editing.
  • Category grouping and area, floor and activity filters.
  • Day previews, schedule enable/disable controls, and selective timed Away mode.
  • Backend scheduling with persisted configuration and device/restart recovery.
  • Single-download HACS packaging with automatic card loading and card-picker discovery.
  • Startup loader fix for HA's scoped custom-element registry.

Install

  1. Add https://github.com/flatsheep/scheduling-manager to HACS as a custom
    repository, category Integration, then download Scheduling Manager.
  2. Restart Home Assistant and add the Scheduling Manager integration.
  3. Create a Panel (single card) dashboard view and add the Scheduling Manager card.

HACS default-catalogue inclusion is a separate submission. Until accepted,
install using the custom repository or the Add to HACS button in the README.

The attached ZIP is a manual-install fallback. Extract its
custom_components/ directory into your HA configuration directory, restart
HA, and add the integration. The card is included and loads automatically.

Verification

All checks passed on the release commit: HACS validation, official hassfest,
backend suites on HA 2026.7.0 / 2026.8.1 / 2026.9.4, frontend build, 20 unit
tests and 66 browser tests. The card-picker bootstrap fix was also reproduced
and checked against HA 2026.10.1's actual frontend.

This project was developed with substantial AI assistance using OpenCode.
See the README's development-transparency section and TEST_RESULTS.md.

Manual-install ZIP SHA256

e629687a4446d4e701e8ff0cebc8177d8d42f680ca12218e56cb2a08c6d0c559  scheduling-manager-1.9.19.zip

Licensed under GPL-3.0; bundled third-party notices are included.