Fix: avoid assigning to read-only config_entry in OptionsFlow (fixes options UI 500 error) #65
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 a 500 error when opening the Greenely integration Options (Configure) UI.
Background:
Historically integrations could set
self.config_entry(though it was discouraged and logged a deprecation warning). Beginning with Home Assistant Core 2025.12 the deprecation period ends,self.config_entrybecomes truly read-only and attempting to assign to it raises an AttributeError (which produces the 500 error shown in the UI).What I changed:
self._config_entry = config_entryself._config_entry.options.get(...)to populate option defaults in the options schema.async_get_options_flowto accept aConfigEntry.Tested: