{"id":4418,"date":"2025-09-12T14:20:25","date_gmt":"2025-09-12T14:20:25","guid":{"rendered":"https:\/\/www.creatingsmarthome.com\/?p=4418"},"modified":"2025-10-16T16:06:59","modified_gmt":"2025-10-16T16:06:59","slug":"home-assistant-migrating-to-the-official-nord-pool-integration","status":"publish","type":"post","link":"https:\/\/www.creatingsmarthome.com\/index.php\/2025\/09\/12\/home-assistant-migrating-to-the-official-nord-pool-integration\/","title":{"rendered":"Home Assistant: Migrating to the Official Nord Pool Integration"},"content":{"rendered":"\n

I’ve been a happy user of the Nord Pool custom component for a long time, and it has served me well! However, with Home Assistant recently introducing its own official Nord Pool integration, and a significant market change on the horizon, it’s time to make the switch.<\/p>\n\n\n\n

On October 1st, 2025, the Nord Pool market is transitioning to a 15-minute Market Time Unit (MTU). While the future of the custom component is uncertain after this change, the official Home Assistant integration has confirmed it will support the 15-minute MTU right out of the box. There might be a few hiccups during the transition, but having official support is a major advantage.<\/p>\n\n\n\n

In this post, I’ll walk you through the exact steps I took to migrate my system from the custom component to the official integration, ensuring my smart home stays ahead of the curve.<\/p>\n\n\n\n

Note: If you are here for the AIO Energy Management, you can still use it with Nord Pool Custom integration – you don’t have to migrate to Official Nord Pool integration unless you want to<\/strong><\/em><\/p>\n\n\n\n

Key Technical Differences<\/h2>\n\n\n\n

The biggest change between the two integrations is how they handle data. The official Nord Pool integration is built around services<\/strong>, while the custom component exposed everything as attributes<\/strong> on a sensor. This means that to get price data with the new integration, we need to actively call a service.<\/p>\n\n\n\n

Another major difference is that the official integration provides only the raw price data from Nord Pool (e.g., in \u20ac\/MWh for Finland) without taxes. The custom component, on the other hand, allowed you to include VAT and other additional costs directly in the sensor’s output. We’ll need to replicate this functionality using template sensors.<\/p>\n\n\n\n

Step 1: Away With the Old, In With the New<\/h2>\n\n\n\n

Because the custom and official components share the same name (nordpool<\/code>), we can’t have both installed simultaneously. This means the migration needs to be done in one go\u2014a “big bang” approach.<\/p>\n\n\n\n

Let’s get straight to it.<\/p>\n\n\n\n

    \n
  1. Uninstall the Custom Component:<\/strong> Navigate to Settings > Devices & Services<\/strong> in Home Assistant, find your existing Nord Pool integration, and click the three dots to uninstall it.<\/li>\n\n\n\n
  2. Remove from HACS (if applicable):<\/strong> If you installed the custom component via HACS, you must also uninstall it from the HACS interface. This will properly remove the files from your custom_components<\/code> folder. If you installed it manually, you’ll need to delete the nordpool<\/code> directory from your config\/custom_components<\/code> folder yourself.<\/li>\n\n\n\n
  3. Reboot Home Assistant:<\/strong> A full reboot is essential to ensure the old component is completely unloaded.<\/li>\n<\/ol>\n\n\n\n

    Once your Home Assistant has rebooted, it’s time to install the official integration.<\/p>\n\n\n\n

      \n
    1. Install the Official Integration:<\/strong> Go to Settings > Devices & Services<\/strong>, click + Add Integration<\/strong>, search for “Nord Pool,” and follow the prompts to configure it with your preferred settings.<\/li>\n<\/ol>\n\n\n\n

      Step 2: Find Your Configuration ID<\/h2>\n\n\n\n

      With the new service-based approach, you’ll need a config_entry<\/code> ID to tell Home Assistant which Nord Pool instance you want to get data from. Think of it as a replacement for the entity_id<\/code> you might have used before.<\/p>\n\n\n\n

      The easiest way to find this ID is:<\/p>\n\n\n\n

        \n
      1. Go to Developer Tools > Actions<\/strong>.<\/li>\n\n\n\n
      2. In the “Service” dropdown, select Nord Pool: Get prices<\/code>.<\/li>\n\n\n\n
      3. Choose your newly created config entry from the UI.<\/li>\n\n\n\n
      4. Switch to YAML mode<\/strong>.<\/li>\n\n\n\n
      5. Voila! The config_entry<\/code> ID will be displayed. Copy this value for the next steps.<\/li>\n<\/ol>\n\n\n\n
        \"\"<\/figure>\n\n\n\n

        Step 3: Rebuilding the ApexCharts Price Graph<\/h2>\n\n\n\n

        Since ApexCharts can’t call services directly to populate a graph, we need to create an intermediary: a template sensor that calls the Nord Pool service and stores the prices.<\/p>\n\n\n\n

        The template sensor below does exactly that. It calls the service periodically to fetch today’s and tomorrow’s prices. Don’t worry about spamming the API; the integration caches the data locally, so frequent updates won’t cause excessive network traffic.<\/p>\n\n\n\n

        This template also includes attributes for tax<\/code> and additional_cost<\/code>, making it easy to replicate the final price calculation you had with the custom component. Tax is added by multiplying original value (e.g. 25.5% = 1.255) and additional costs are added over that. So, if you your add tariffs and your tariffs needs to have VAT included remember to include as well into additional_costs.
        <\/p>\n\n\n\n

        template:\n  - triggers:\n      - trigger: time_pattern\n        minutes: \/1\n      - trigger: homeassistant\n        event: start\n    actions:\n      - action: nordpool.get_prices_for_date\n        data:\n          config_entry: 01K4QBH1H606SDS1V28KGR32K7\n          date: \"{{ now().date() }}\"\n          areas: FI\n          currency: EUR\n        response_variable: today_price\n      - action: nordpool.get_prices_for_date\n        data:\n          config_entry: 01K4QBH1H606SDS1V28KGR32K7\n          date: \"{{ now().date() + timedelta(days=1) }}\"\n          areas: FI\n          currency: EUR\n        response_variable: tomorrow_price\n    sensor:\n      - name: Electricity prices\n        unique_id: electricity_prices\n        unit_of_measurement: \"snt\/kWh\"\n        icon: mdi:cash\n        state: >\n          {%- set region = (this.attributes.get('region', 'FI') | string) -%}\n          {%- set tax = (this.attributes.get('tax', 1.0) | float) -%}\n          {%- set additional_cost = (this.attributes.get('additional_cost', 0.0) | float) -%}\n\n          {% if (today_price is mapping) and (tomorrow_price is mapping) %}\n            {% set data = namespace(prices=[]) %}\n            {% for state in today_price[region] %}\n              {% set data.prices = data.prices + [(((state.price\/10 | float)  * tax + additional_cost)) | round(3, default=0)] %}\n            {% endfor %}\n            {% for state in tomorrow_price[region] %}\n              {% set data.prices = data.prices + [(((state.price\/10 | float) * tax + additional_cost)) | round(3, default=0)] %}\n            {% endfor %}\n            {{min(data.prices)}}\n          {% else %}\n            unavailable\n          {% endif %}\n        attributes:\n          tomorrow_valid: >\n            {%- set region = (this.attributes.get('region', 'FI') | string) -%}\n            {%- if (tomorrow_price is mapping) %}\n              {%- if tomorrow_price[region] | list | count > 0 -%}\n                {{ true | bool }}\n              {%- else %}\n                {{ false | bool }}\n              {%- endif %}\n            {%- else %}\n              {{ false | bool }}\n            {%- endif %}\n          data: >\n            {%- set region = (this.attributes.get('region', 'FI') | string) -%}\n            {%- set tax = (this.attributes.get('tax', 1.0) | float) -%}\n            {%- set additional_cost = (this.attributes.get('additional_cost', 0.0) | float) -%}\n\n            {% if (today_price is mapping) and (tomorrow_price is mapping) %}\n            {% set data = namespace(prices=[]) %}\n              {% for state in today_price[region] %}\n                {% set local_start = as_datetime(state.start).astimezone().strftime('%Y-%m-%d %H:%M:%S') %}\n                {% set local_end = as_datetime(state.end).astimezone().strftime('%Y-%m-%d %H:%M:%S') %}\n                {% set data.prices = data.prices + [{'start':local_start, 'end':local_end, 'price': (((state.price\/10 | float) * tax + additional_cost)) | round(3, default=0)}] %}\n              {% endfor %}\n              {% for state in tomorrow_price[region] %}\n                {% set local_start = as_datetime(state.start).astimezone().strftime('%Y-%m-%d %H:%M:%S') %}\n                {% set local_end = as_datetime(state.end).astimezone().strftime('%Y-%m-%d %H:%M:%S') %}\n                {% set data.prices = data.prices + [{'start':local_start, 'end':local_end, 'price': (((state.price\/10 | float) * tax + additional_cost)) | round(3, default=0)}] %}\n              {% endfor %}\n              {{data.prices}}\n            {% else %}\n              []\n            {% endif %}\n          tax: 1.255\n          additional_cost: 0\n          region: FI<\/code><\/pre>\n\n\n\n
        After creating this sensor and reloading your template entities (Developer Tools > YAML > Template Entities<\/code>), you’ll have sensor.electricity_prices<\/code> ready to use. Here is the ApexCharts card configuration, which is very similar to the old setup:<\/p>\n\n\n\n
        type: custom:apexcharts-card\nexperimental:\n  color_threshold: true\nheader:\n  show: true\n  title: NordPool electricity prices (today\/tomorrow)\n  show_states: true\n  colorize_states: true\ngraph_span: 48h\nspan:\n  end: day\n  offset: +1d\nnow:\n  show: true\n  label: Now\nseries:\n  - entity: sensor.electricity_prices\n    type: column\n    show:\n      extremas: true\n      in_header: before_now\n    float_precision: 3\n    data_generator: |\n      return entity.attributes.data.map((start, index) => {\n        return [new Date(start[\"start\"]).getTime(), entity.attributes.data[index][\"price\"]];\n      });\n    color_threshold:\n      - value: 0\n        color: green\n      - value: 10\n        color: orange\n      - value: 30\n        color: red<\/code><\/pre>\n\n\n\n
        \n
        \"\"<\/figure>\n\n\n\n
        \"\"<\/figure>\n<\/figure>\n\n\n\n
        Step 4: Updating the Energy Dashboard<\/h2>\n\n\n\n
        The official integration creates a sensor for the current price automatically (e.g., sensor.nord_pool_fi_current_price<\/code>), which is perfect for the Energy Dashboard. However, this sensor shows the raw price. If you want your Energy Dashboard costs to reflect VAT, you’ll need another simple template sensor.<\/p>\n\n\n\n
        This one adds the 25.5% VAT to the raw price.<\/p>\n\n\n\n
        template:\n  - sensor:\n      name: Nord Pool current price with taxes\n      unique_id: nordpool_current_price_with_taxes\n      unit_of_measurement: \"snt\/kWh\"\n      state: >\n        {{ (states('sensor.nord_pool_fi_current_price') | float * 100 * 1.255) | round(3) }}<\/code><\/pre>\n\n\n\n
        You can then use this new sensor.nordpool_current_price_with_taxes<\/code> in your Energy Dashboard settings for real-time costs.<\/p>\n\n\n\n
        Step 5: Configuring AIO Energy Management<\/h2>\n\n\n\n
        I use the AIO Energy Management<\/a> integration to calculate the cheapest hours of the day for running high-consumption devices. Version 0.5.0 introduced support for the 15-minute MTU and, crucially, price templating. This is necessary because the raw price from the Nord Pool service doesn’t include taxes or fees.<\/p>\n\n\n\n
        In my configuration below, I use the price_modifications<\/code> template to transform the raw price from \u20ac\/MWh into cents\/kWh (snt\/kWh<\/code>) and add the 25.5% VAT.<\/p>\n\n\n\n
        Here is my updated configuration for AIO Energy Management for all my devices (water heater, outdoor spa and garage heating):<\/p>\n\n\n\n
        aio_energy_management:\n    calendar:\n        unique_id: energy_management_calendar\n        name: Energy Management Calendar\n    cheapest_hours:\n      - nordpool_official_config_entry: 01K4QBH1H606SDS1V28KGR32K7\n        unique_id: cheapest_hours_water_boiler\n        name: Cheapest Hours Water Boiler\n        first_hour: 21\n        last_hour: 12\n        starting_today: true\n        number_of_hours: 6\n        sequential: false\n        failsafe_starting_hour: 1\n        price_modifications: >\n          {%- set as_snt = price \/ 10.0 %}\n          {%- set with_taxes = (as_snt * 1.255) | float %}\n          {{ with_taxes }}\n      - nordpool_official_config_entry: 01K4QBH1H606SDS1V28KGR32K7\n        unique_id: cheapest_hours_hot_tub\n        name: Cheapest Hours Hot Tub\n        first_hour: 0\n        last_hour: 23\n        starting_today: false\n        number_of_hours: 5\n        sequential: false\n        max_price: 5.0\n        price_modifications: >\n          {%- set as_snt = price \/ 10.0 %}\n          {%- set with_taxes = (as_snt * 1.255) | float %}\n          {{ with_taxes }}\n      - nordpool_official_config_entry: 01K4QBH1H606SDS1V28KGR32K7\n        unique_id: cheapest_hours_garage_heating\n        name: Cheapest Hours Garage Heating\n        first_hour: 20\n        last_hour: 14\n        starting_today: true\n        number_of_hours: sensor.garage_heating_number_of_hour\n        sequential: false\n        trigger_hour: 20\n        failsafe_starting_hour: 1\n        price_modifications: >\n          {%- set as_snt = price \/ 10.0 %}\n          {%- set with_taxes = (as_snt * 1.255) | float %}\n          {{ with_taxes }}\n<\/code><\/pre>\n\n\n\n
        Final Steps and Automations<\/h2>\n\n\n\n
        I also had many automations that relied on the old custom component, and as expected, they all broke during this update. The simplest ones just needed an entity ID change, but others\u2014like energy price push notifications<\/a> or automations that change my EV charger’s color based on price<\/a>\u2014required more significant changes to work with the new service-based approach.<\/p>\n\n\n\n
        I won’t be diving into specific automation examples in this post, but if that’s something you’d like to see, let me know in the comments, and I might write a follow-up article!<\/p>\n\n\n
        <\/div><\/div><\/div>\n\n
        \n
        Did you find this guide helpful? You can keep the blog going by bidding me a coffee!<\/h5>\r\n
        \r\n