Phase 3: Heating circuit time programs (weekly schedules)

[liudger]

Phase 3: Heating Circuit Time Programs

Priority: 🟡 Medium
Scope: Library + HA integration
Depends on: Phase 0 (#1372)
Parent: #1371

Goal

Expose heating circuit time programs (weekly schedules) similar to the existing DHW schedule support. Users can read and set when each heating circuit switches between comfort and reduced modes.

Background

The library already has a working pattern for time program handling via the DHW schedule (DaySchedule, TimeSlot models, set_hot_water_schedule()). This phase replicates that pattern for heating circuits.

New Parameters

HC1 Time Programs (params 500-506)

Param ID	Day	Name
500	Monday	heating_schedule_mon
501	Tuesday	heating_schedule_tue
502	Wednesday	heating_schedule_wed
503	Thursday	heating_schedule_thu
504	Friday	heating_schedule_fri
505	Saturday	heating_schedule_sat
506	Sunday	heating_schedule_sun

HC2 Time Programs (params 520-526)

Param ID	Day	Name
520-526	Mon-Sun	heating_schedule_hc2_mon … _sun

HC3 Time Programs (params 540-546)

Param ID	Day	Name
540-546	Mon-Sun	heating_schedule_hc3_mon … _sun

Tasks

Library (python-bsblan)

• Add time program param IDs to constants.py
  • HEATING_SCHEDULE_PARAMS for HC1
  • HEATING_SCHEDULE_HC2_PARAMS, HEATING_SCHEDULE_HC3_PARAMS
• Create HeatingSchedule model in models.py (reuse DaySchedule, TimeSlot)
• Add heating_schedule() method to bsblan.py with circuit parameter
• Add set_heating_schedule() method (mirror set_hot_water_schedule())
• Implement granular lazy loading for schedule params (like hot water groups)
• Add tests and fixtures
• Run uv run prek run --all-files

HA Integration

• Decide on entity representation:
  • Option A: Service calls for get/set schedule (like set_hot_water_schedule)
  • Option B: Custom calendar entity (HA calendar platform)
  • Option C: Expose via diagnostics + service calls
• Implement chosen approach
• Per-circuit schedule support (one schedule entity per active circuit)
• Add tests

Acceptance Criteria

• Users can read weekly schedules for all active heating circuits
• Users can modify schedules via service calls or entities
• Schedule format matches existing DHW schedule pattern (DaySchedule / TimeSlot)
• Multi-circuit: each circuit has its own independent schedule
• Reuses existing time program parsing/validation code

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!