Get energy prices

Use this action to fetch the hourly energy prices for your Tibber homes. You can fetch the prices for today, or set a date range to get prices for a specific period.

This action returns its result in a response variable, which you can use in later steps of the same automation or script, for example to find the cheapest time to run an appliance.

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 get energy prices 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 Tibber: Get energy prices.
  6. Optionally, set a Start and End to fetch prices for a specific period.
  7. Select Save.

This action does not support targets. In the UI, you are not prompted to choose an area, device, entity, or label.

Options in the UI

Start (Optional)

The date and time from which to retrieve prices. Defaults to today if omitted.

End (Optional)

The date and time until which to retrieve prices. Defaults to the end of today if omitted.

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.

In YAML, refer to this action as tibber.get_prices. Store the result in a response variable so you can use it in later steps:

ActionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*. [Learn more]
action: tibber.get_prices
data:
  start: "2024-01-01 00:00:00"
  end: "2024-01-01 23:00:00"
response_variable: energy_prices

This fetches the energy prices for the first of January 2024.

Options in YAML

start string

The date and time from which to retrieve prices, such as 2024-01-01 00:00:00. Defaults to today if omitted.

end string

The date and time until which to retrieve prices, such as 2024-01-01 23:00:00. Defaults to the end of today if omitted.

Response data

The response is a dictionary with a prices key, which holds an entry for each of your Tibber homes. Each home contains a list of price entries, and each entry includes the following fields:

  • start_time: The start time of the price, returned in local time.
  • price: The total energy price (energy and taxes) for that interval. A shortened example of the response looks like this:
prices:
  Nickname_Home:
    - start_time: "2023-12-09 03:00:00+02:00"
      price: 0.46914
    - start_time: "2023-12-09 03:15:00+02:00"
      price: 0.46914

Try it yourself

Ready to test this? Open Developer 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?

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.

Tip

AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.