Skip to content

Add instruction how to find Nord Pool config entry id #38403

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
JukeboxBill opened this issue Apr 6, 2025 · 1 comment · Fixed by #38554
Closed

Add instruction how to find Nord Pool config entry id #38403

JukeboxBill opened this issue Apr 6, 2025 · 1 comment · Fixed by #38554
Assignees

Comments

@JukeboxBill
Copy link

JukeboxBill commented Apr 6, 2025

Feedback

As mentioned in the title it would be helpful to add instruction for how to find your own Nord Pool config entry id or a link to it.
It's not obvious knowledge for the common user, I had to search for it on the internet.

URL

https://www.home-assistant.io/integrations/nordpool/

Version

2025.4.1

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Apr 6, 2025

Hey there @gjohansson-ST, mind taking a look at this feedback as it has been labeled with an integration (nordpool) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of nordpool can trigger bot actions by commenting:

  • @home-assistant close Closes the feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign nordpool Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants