nordpool
nordpool copied to clipboard
custom-components
Home-assistant official nordpool integration
There is a new integration on its way in the official repository for home-assistant: https://github.com/home-assistant/core/tree/dev/homeassistant/components/nordpool
is this the same integration ?
That is very nice. But I wonder how long I can be there. The api access is questionable as best 😏. This is the main reason for why I never tried to get it into the main. Lots of good stuff, it’s a modern approach to creating sensors but all advanced stuff is removed.
Do you know if it is possible to run them side by side? Only this custom one shows up on my install when I try to add the "official" integration.
Do you know if it is possible to run them side by side? Only this custom one shows up on my install when I try to add the "official" integration.
Should work, but this new integration is not available before 2024.12 version if you dont use betas then
Should work, but this new integration is not available before 2024.12 version if you dont use betas then
I'm running the beta. Maybe the same name is tripping up Home Assistant.
It seems the HACS version prevents trying the new native because the name is the same. Looking at the docu the new native can only show last, current and next price. And you will need to create a template sensor to add tariffs and VAT. This HACS version is much much better featured.
Sooo.... I was stupid enough to think the official addon was replacing this one, without to much reading up I removed the HACS one, installed the official, realized it was much less advanced.... so here I am, trying to get back my sensors I had created without fully restoring HA.
I looked in a old backup but can't find the sensors I created in the HACS version, any tip where I should look for them? I had some custom ones with VAT and so on, can't remember how I crated them but would be nice to re-create them the same way again if I only could find them, any help would be much appreciated.
So let me explain a bit since it might be off interest. The custom component as well as the native one share the same domain, as such if the custom one is installed, the native one can not be used.
Secondly, as this is a custom component it can do things which are not possible (not allowed) in the native one. The result can be the same but with the native one there would be a need to use templates etc. to achieve the same end result (if that's what you want).
Lastly, as the native one is new there will be some iterations before it's complete. As example in 2025.1 there will be an action call to get all prices for a date etc. There is no preference for which one to use more than your own preference and use-case.
The custom component as well as the native one share the same domain, as such if the custom one is installed, the native one can not be used.
Is that how it works in HA 2025.1? In my development environment, I created an instance of the native Nord Pool to test it. But then I was not able to create any instance of the custom component verison. I removed the instance of the native one, and redownloaded the custom component one, but still when trying to add a new instance, only the native version were found.
EDIT: This was due to local issue I had with my setup. Please ignore this comment.
The custom component as well as the native one share the same domain, as such if the custom one is installed, the native one can not be used.
Is that how it works in HA 2025.1? In my development environment, I created an instance of the native Nord Pool to test it. But then I was not able to create any instance of the custom component verison. I removed the instance of the native one, and redownloaded the custom component one, but still when trying to add a new instance, only the native version were found.
That's how it's always been. If you put a custom component in the /config/custom_components directory which has the same domain (folder name and in manifest) as a one in core, the custom component is always the one which gets loaded.
I think in your case you might have some other issue if you're not able to load the custom one.
Would it be an idea to rename this HACS integration so the core and HACS integration can run side by side? There are several integrations which do this (Home Connect Alt and Tesla come to mind and I have seen more).
I expect it will be a breaking change but it is in my opinion a good choice for the benefit of the users and both integrations. Let each of them shine in their own way.
