Skip to content

Fix non-string manufacturer passed to device registry#217

Open
G3z wants to merge 1 commit into
anotherjulien:masterfrom
G3z:fix/device-registry-manufacturer-type
Open

Fix non-string manufacturer passed to device registry#217
G3z wants to merge 1 commit into
anotherjulien:masterfrom
G3z:fix/device-registry-manufacturer-type

Conversation

@G3z

@G3z G3z commented Jul 1, 2026

Copy link
Copy Markdown

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.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant