Version 0.0.14 - New Entity Name - Should be breaking change.

[Nornode]

Version of the custom_component

0.0.14

Homeassistant version

2032.05.2

Configuration

UI Configured

Describe the bug

A clear and concise description of what the bug is.

Updated to 0.0.14 and I have suddenly one "Unavailable" integration with the old entity ID and yet another new with a new Entity ID.

OLD: sensor.nordpool_kwh_fi_eur_3_10_01
NEW: sensor.nordpool_kwh_fi_eur_3_10_024

Why? - This breaks all my automations and integrations (to Powersaver.no)

Debug log

[ThePatricide]

This is exactly what happened to me after a restart. I thought something was wrong with the issue #326, but I finally found out the component loads everything fine, but the name has changed. Only thing I did was restart Home Assistant. Which I had done previously of course as well, without the name changing.

[granholm]

This is nothing new, and is mentioned in the Readme.

Tip: By default, the integration will create a device with the name nordpool_<energy_scale>_<region>_<currency>_<some-numbers>. 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.

I agree that it's a bit annoying sometimes, but it is that way by design.

[ThePatricide]

Can we also make it possible via YAML? As I prefer to have the configuration in YAML, to be able to set new taxes and tariffs ready at for example a new year.

[koskila]

I was puzzled as to what's wrong with my template entities and hence some automations breaking, but turns out it's the entity changing names again. Would be lovely to have some sort of mapping or override in the YAML config, but I guess just renaming the entities using the UI will do the trick, too?

[Hellowlol]

Correct, change the id using the ui.