Get prices for date
The integration entities provide price information only for the current date. The Get prices for date action retrieves prices for any date within the last two months or for tomorrow.
This action returns its result in a response variable, which you can use in later steps of the same automation or script, for example in a trigger-based template sensor.
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 prices for a date from an automation or a script:
- Go to Settings > Automations & scenes.
- Open an existing automation or script, or select Create automation > Create new automation.
- 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.
- In the Then do section, select Add action.
- From the search box, search for and select Nord Pool: Get prices for date.
- Select the Config entry and the Date. Optionally, set the Areas and Currency.
- In the Response variable field, enter a name to store the data in, such as
price_for_date. - 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
The date to get prices for. Only dates from two months in the past to one day in the future are allowed.
One or multiple market areas to get prices for. If left empty, the areas from the configuration entry are used.
The public API only provides past pricing information for up to two months. Although Nord Pool operates in the CET/CEST timezone, all data is returned in UTC. Tomorrow’s prices are typically released around 13:00 CET/CEST. Requesting them earlier returns an error.
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 nordpool.get_prices_for_date. Store the result in a response variable so you can use it in later steps:
action: nordpool.get_prices_for_date
data:
config_entry: 1234567890a
date: "2024-11-10"
areas:
- "SE3"
- "SE4"
currency: "SEK"
response_variable: price_for_date
This fetches the prices for the given date in the SE3 and SE4 areas, in Swedish krona.
Options in YAML
The date to get prices for. Only dates from two months in the past to one day in the future are allowed.
One or multiple market areas to get prices for. If left empty, the areas from the configuration entry are used.
Response data
The response contains one entry per requested area. Each area holds a list of price intervals with the following fields:
-
start: The start date and time of the interval, in UTC. -
end: The end date and time of the interval, in UTC. -
price: The price for the interval, in the requested currency per MWh.
A shortened example of the response looks like this:
SE3:
- start: "2024-11-10T00:00:00+00:00"
end: "2024-11-10T01:00:00+00:00"
price: 320.5
- start: "2024-11-10T01:00:00+00:00"
end: "2024-11-10T02:00:00+00:00"
price: 298.1
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.
AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.
Related actions
These actions work well alongside this one:
- Get price indices for date: Retrieves the price indices for a specific date.