Get schedule

The Eurotronic Comet Blue: Get schedule action retrieves the current schedule from a Eurotronic Comet Blue thermostat.

During the times when the schedule is active, the device will automatically try to reach the Comfort preset. When inactive, the Eco preset is used.

You can use this action in automations and scripts, or use it in Settings > Tools > Actions to inspect the current schedule.

Using this action from the user interface

If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.

To retrieve the device schedule from an automation or a script:

1. Go to Settings > Automations & scenes.
2. Open an existing automation or script, or select Create automation > Create new automation.
3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
4. In the Then do section, select Add action.
5. From the search box, search for and select Eurotronic Comet Blue: Get schedule.
6. Select what you want to control. Under By target (see Targets), pick one or more thermostats.
7. Enter the name of a response variable to use the schedule in following steps.
8. Select Save.

Using this action in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required. For how an automation or a script is built in YAML, refer to Automations in YAML and Scripts.

In YAML, refer to this action as eurotronic_cometblue.get_schedule. A basic example looks like this:

action: eurotronic_cometblue.get_schedule
target:
  entity_id: climate.kitchen
response_variable: my_schedule

This loads the current schedule from climate.kitchen and stores it in the response variable my_schedule.

Targets of the action

This action requires a target. The target is the object of the action. You can point the action at a single entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], a device, an area, a floor, or a label, and Home Assistant will run the action on every matching Eurotronic Comet Blue thermostat behind that target.

• Entity: one specific Eurotronic Comet Blue thermostat, such as climate.kitchen.
• Device: every Eurotronic Comet Blue thermostat that belongs to a device.
• Area: every Eurotronic Comet Blue thermostat in a room or area.
• Floor: every Eurotronic Comet Blue thermostat on a floor.
• Label: every Eurotronic Comet Blue thermostat that shares a label.

You can also select different target types in one action. For example, you can add a specific entity and an area as targets in the same action to run the action on both of them at once.

Good to know

The response data contains one top-level field for each targeted climate entity.

Each entity contains seven fields, one for each day of the week in lowercase. Each day contains a list of time ranges. Days without any configured heating schedules return an empty list.

climate.kitchen:
  monday:
    - from: "07:00:00"
      to: "09:00:00"
    - from: "17:00:00"
      to: "22:00:00"
  tuesday: []
  wednesday: []
  thursday:
    - from: "07:00:00"
      to: "09:00:00"
  friday:
    - from: "07:00:00"
      to: "09:00:00"
  saturday:
    - from: "09:00:00"
      to: "12:00:00"
  sunday: []

Try it yourself

Ready to test this? Open Settings > Tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.

Still stuck?

To test the action on its own, run it in the automation editor with Run action, and check the message that it shows. To see what the action did when the automation ran, open the trace of that run. For details, refer to Testing automations. For common problems and their solutions, refer to Troubleshooting automations.

If that doesn’t help, the Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.

Related actions

Explore related actions:

• Set schedule: Push a schedule to a thermostat.