Fix non-string manufacturer passed to device registry#217
Open
G3z wants to merge 1 commit into
Open
Conversation
The manual config flow wrapped gateway metadata values in single-element tuples (a stray trailing comma), so `manufacturer` was stored as a tuple instead of a string. Home Assistant's device registry rejects non-string values and warns this will stop working in 2026.12.0. - config_flow.py: store the manual-entry values as plain strings/None. - __init__.py: defensively coerce list/tuple values to a string when building the gateway device entry, so existing config entries that already stored the tuple no longer trigger the warning.
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
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.
The manual config flow wrapped gateway metadata values in single-element tuples (a stray trailing comma), so
manufacturerwas stored as a tuple instead of a string. Home Assistant's device registry rejects non-string values and warns this will stop working in 2026.12.0.