search

custom-components / nordpool

This component allows you to pull in the energy prices into Home-Assistant.
450 stars 108 forks source link

Integrations broken after v0.15 #423

Open rinowit opened 3 days ago

rinowit commented 3 days ago

I have had this integration for many years. Now sadly my integrations that depends of the past model of the sensor date is broken.

My question is: Why is the structure changed? This is ofcourse not a security issue that is the reason. It's ok with tha name change from Oslo to NO1. But why the structure? It takes down all the integrations I had that was dependent of the maked prices?

I have been using HA for at least 10 years and more. And some times I have been wondering if I have to change a system to a more robust system that don't give surprises like this.

The Nordpool integration has been a wonderfull add-on.

Thank you:)

dana-se commented 3 days ago

Take a look here https://github.com/custom-components/nordpool/issues/420#issuecomment-2421497326

rinowit commented 3 days ago

Thank you:) I will check it up:)

dana-se commented 3 days ago

I think that the easiest way for you, is to rename both the Name and Entity ID to the old ones that worked. image

README Tip: By default, the integration will create a device with the name nordpool__. It is recommended to rename the device and all its entities to nordpool. If you need to recreate your sensor (for example, to change the additional cost), all automations and dashboards keep working.

rinowit commented 3 days ago

I did, but the version 0.14 didn't download the new data. 0.15 downloads the data, but don't work with the other plug-ins I have.

dana-se commented 3 days ago

This is because 0.15 make a new sensor with new name and Identity ID, that you must rename to the old names. Your plugins are looking for the old Identity ID.

rinowit commented 3 days ago

I have already tried renaming it to the previous configuration, but the other plugin uses the old region names hardcoded. I attempted to modify that plugin, but it can't read the new sensor data.

I’ve been trying to understand how the low price percentage works. If I can stop using the other plugin and solely rely on this one, it might prevent future issues. If I want to use the top 30% of the lowest prices of the day, what value should I set to achieve that?

Thanks for helping:)

dana-se commented 3 days ago

@rinowit If you look at the entities of your new nordpool sensor, has the Identity ID the same name as the hardcoded plugin use?

rinowit commented 3 days ago

No, it has the name sensor.nordpool. Not the strang numeric ending. I use this name everywhere in the integration:)

dana-se commented 3 days ago

But you sad "the other plugin uses the old region names hardcoded" Then you must rename your sensor.nordpool to that hardcoded name.

rinowit commented 2 days ago

I used Oslo and not the new NO1. There are probably other differences to. As I have tryed to change the system files for the other plugin to match NO1

thr0t commented 1 day ago

After several days of trying different solutions I was not able to get it working in my container HASS. Seems like all the HASS updates have not gone smoothly as there are a lot of system logic changes and some settings just started conflicting. So the solution that worked for me was fresh HASS install. It is a pain (the esphome needs additional effort, not related to this topic) but at least it started working.