You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel that there is need for friendly_name. You can rename one single nordpool sersor, but I cannot find a way to add two or more individual nordpool sersors without giving sensors unique name using friendly_name.
If you try to add second sensor it will fail (I have renamed mine to sensor.spot_hinta)
"Platform nordpool does not generate unique IDs. ID nordpool_kwh_fi_eur_3_10_024 already exists - ignoring sensor.spot_hinta"
I have used my forked version with for friendly_name to allow two nordpool sensors. One is with additional costs and other one is just a bare spot price.
I have modified your latest version with fix that supports friendly_name and created pull request (I hope it's done correctly, my first pull request in GitHub). For some reason after reboot second sensor may not start outputting correct values instantly, until that it works it just shows error "Entity is non-numeric: sensor.XXX". But eventually it works and this fix allows to add several nordpool sensors.
Version of the custom_component
Version 0.0.3
Configuration
Describe the bug
A clear and concise description of what the bug is.
Setting
friendly name
during configuration flow (adding through Integrations) does not apply to sensor.I have not tried if it works with yaml.
Debug log
The text was updated successfully, but these errors were encountered: