Skip to content

Conversation

@johanzander
Copy link
Contributor

Proposed change

Adds migration logic to handle config entries created before the CONF_AUTH_TYPE field was introduced in PR #149783. The migration automatically detects the authentication type based on the presence of either CONF_TOKEN (for API token auth) or CONF_USERNAME/CONF_PASSWORD (for password auth) and updates the config entry accordingly.

This resolves the 'Unknown authentication type in config entry' error that users experienced after upgrading to Home Assistant Core 2025.11.0.

Fixes #155906

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

Adds migration logic to handle config entries created before the CONF_AUTH_TYPE
field was introduced in PR home-assistant#149783. The migration automatically detects the
authentication type based on the presence of either CONF_TOKEN (for API token
auth) or CONF_USERNAME/CONF_PASSWORD (for password auth) and updates the config
entry accordingly.

This resolves the 'Unknown authentication type in config entry' error that users
experienced after upgrading to Home Assistant Core 2025.11.0.

Fixes home-assistant#155906
@joostlek joostlek added this to the 2025.11.1 milestone Nov 6, 2025
@frenck frenck merged commit b79b443 into home-assistant:dev Nov 7, 2025
36 checks passed
frenck pushed a commit that referenced this pull request Nov 7, 2025
#155993)

Co-authored-by: epenet <6771947+epenet@users.noreply.github.com>
@frenck frenck mentioned this pull request Nov 7, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Nov 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Growatt: Unknown authentication type in config entry

4 participants