Fix 500 error during planner setup on recent Home Assistant vrsions - #108
Open
Trihawk-8 wants to merge 1 commit into
Open
Fix 500 error during planner setup on recent Home Assistant vrsions#108Trihawk-8 wants to merge 1 commit into
Trihawk-8 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes the configuration flow on recent Home Assistant versions.
The planner previously relied on template.integration_entities(), which no longer returns the expected Nord Pool entities during setup, resulting in a 500 internal Server Error.
This change discovers the Nord Pool sensor entities directly from the Home Assistant state registry while preserving the existing NORDPOOL_DOMAIN_ and ENTSOE_DOMAIN logic.
Tested on Home Assistant where the original integration failed during configuration.