Lovelace card for Daily Schedule Integration entities.
Note: The custom integration is a prerequisite and can be installed via HACS using this link.



Each range has from
and to
. If the to
is less than or equal from
it's treated as time in the following day. One interesting case is when from
equals to
. This type of range covers the whole day (always on).
There are 3 ways to specify time:
- A fixed time (e.g. 12:30).
- Sunrise with an optional negative / positive offset.
- Sunset with an optional negative / positive offset.
Name | Type | Required | Default | Description |
---|---|---|---|---|
type | string | True | - | Must be custom:daily-schedule-card |
title | string | False | - | Title of the card |
card | bool | False | True if title is supplied |
Whether to render an entire card or rows inside the entities card |
template | string | False | Null |
Template for rendering the value. Has access to entity_id |
Name | Type | Required | Default | Description |
---|---|---|---|---|
entity | string | True | - | The binary_sensor entity ID |
name | string | False | Friendly name of the entity | Name to display |
template | string | False | Null |
Per-entity template (overrides card's template) |
Note: you can also just give the entity ID (with no entity:
) if you don't need to specify the name explicitly.
type: entities
entities:
- type: custom:daily-schedule-card
entities:
- entity: binary_sensor.venta_schedule
name: Venta
type: custom:daily-schedule-card
title: Timers
entities:
- binary_sensor.swimming_pool_filter_schedule
type: custom:daily-schedule-card
card: true
template: >-
{{ state_attr(entity_id, 'effective_schedule') |
map(attribute='from') | map('truncate', 2, True, '')
| join(' | ') }}
entities:
- binary_sensor.let_the_dog_out
The custom card is properly registered when installing via HACS.
Otherwise, the JS file can be downloaded from latest releases. Follow these instructions to register the custom card.