Schedule Card¶

The HomematicIP Local Schedule Card is a custom Lovelace card for displaying and editing event-based schedules for Homematic switches, lights, covers, and valves.

Features¶

Event-based scheduling: Manage individual schedule events with precise control
Multi-device support: Works with switches, lights, covers, and valves
Flexible timing: Fixed time or astronomical events (sunrise/sunset) with offset
8 condition types: Fixed time, astro, earliest/latest combinations
Category-specific UI: Adapted controls per device type (dimming, slat position, duration, etc.)
Visual configuration: Configure via the UI editor — no YAML required
Bilingual: English and German

Supported Device Types¶

Domain	Description	Special Fields
`switch`	On/Off devices	Level: 0.0 or 1.0 only
`light`	Lights with dimming support	Level + ramp time
`cover`	Blinds/shutters with position and slat control	Level + level_2 (slats)
`valve`	Heating valves	Level + duration

Installation¶

The card is automatically available when the HomematicIP Local integration is loaded — no manual installation required. It appears in the Lovelace card picker under HomematicIP Local Scheduler Card.

Migrating from HACS

If you previously installed this card via HACS, the integration-bundled version detects this and skips duplicate registration. You can remove the HACS card resource at your convenience: HACS → Frontend → remove the schedule card. Both versions coexist without conflicts during the transition.

Configuration¶

Basic¶

type: custom:homematicip-local-schedule-card
entity: switch.garden_lights

Multiple Entities¶

type: custom:homematicip-local-schedule-card
entities:
  - switch.garden_lights
  - light.hallway_dimmer
  - cover.living_room_blinds

When multiple entities are defined, a dropdown appears to switch between them.

All Options¶

Option	Type	Default	Description
`entity`	string	—	Single entity ID
`entities`	string[]	—	List of entity IDs
`name`	string	Entity name	Custom card header name
`editable`	boolean	`true`	Enable/disable editing
`hour_format`	string	`24`	Time format: `12` or `24` hour
`language`	string	Auto-detect	Force language: `en` or `de`
`time_step_minutes`	number	`15`	Time picker step size in minutes

Usage¶

Schedule Events¶

Each schedule event defines when and how a device should be controlled. A device supports up to 24 schedule events.

An event consists of:

Weekdays: Which days the event is active
Time: When the event triggers (fixed or astronomical)
Target channels: Which device channels to control
Level: Output level (0.0–1.0)
Duration: How long to keep the output active (optional)
Ramp time: Transition time for dimmers (optional, lights only)

Condition Types¶

Events can use different timing conditions:

Condition	Description
`fixed_time`	Trigger at the specified time
`astro`	Trigger at sunrise or sunset (with optional offset)
`fixed_if_before_astro`	Use fixed time if it is before the astro event
`astro_if_before_fixed`	Use astro event if it is before the fixed time
`fixed_if_after_astro`	Use fixed time if it is after the astro event
`astro_if_after_fixed`	Use astro event if it is after the fixed time
`earliest`	Use whichever comes first (fixed time or astro event)
`latest`	Use whichever comes last (fixed time or astro event)

Astronomical events support an offset of up to ± 720 minutes (12 hours) from sunrise or sunset.

Editing¶

Click Add Event to create a new schedule event
Select the weekdays for the event
Choose a condition type and set the trigger time
Select target channels for the device
Set the level and optional parameters (duration, ramp time)
Click Save to write the schedule to the device

Domain-Specific Controls¶

The card adapts its UI based on the device type:

Switch: Simple on/off toggle (level 0.0 or 1.0)
Light: Brightness slider (0–100%) with optional ramp time for smooth dimming
Cover: Position slider (0–100%) with optional slat position (level_2)
Valve: Opening slider (0–100%) with optional duration

Schedule Data Format¶

The schedule data follows the same format as the homematicip_local.set_schedule action. See Week Profiles — Non-Climate Schedule Actions for the complete field reference and examples.

Quick Example¶

schedule_data:
  "1":
    weekdays: [MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY]
    time: "06:30"
    condition: fixed_time
    target_channels: ["1_1"]
    level: 0.8
    duration: 1min
  "2":
    weekdays: [SATURDAY, SUNDAY]
    time: "08:00"
    condition: astro
    astro_type: sunrise
    astro_offset_minutes: 30
    target_channels: ["1_1"]
    level: 0.5
    duration: 30min

Permissions¶

By default, only admin users can edit schedules. To allow non-admin household members to edit schedules, enable this in the integration options under Schedule editing. See Schedule Editing for Non-Admin Users for details.

Troubleshooting¶

Card not appearing¶

Clear browser cache (Ctrl+F5)
Ensure the HomematicIP Local integration is loaded and running
Check Home Assistant logs for frontend registration errors

Entity not listed¶

Verify the entity has schedule support (check for a Week Profile sensor entity on the device)
Ensure the entity domain is supported (switch, light, cover, or valve)

Changes not saving¶

Check Home Assistant logs for WebSocket errors
Ensure the CCU and device are reachable
Wait for CONFIG_PENDING to clear on the device