Skip to content

fix: force fresh login on reauth instead of reusing cached session - #504

Merged
sockless-coding merged 1 commit into
masterfrom
fix_reauth
Aug 22, 2026
Merged

fix: force fresh login on reauth instead of reusing cached session#504
sockless-coding merged 1 commit into
masterfrom
fix_reauth

Conversation

@sockless-coding

Copy link
Copy Markdown
Owner

When the user re-enters credentials during reauth, _async_try_login was still calling start_session(), which silently kept reusing the cached (possibly stale) session from the settings file. Pass the flow origin through and call reauthenticate() for the "reauth_confirm" origin so the entered credentials are actually used.

Also bump aio-panasonic-comfort-cloud to 2026.8.8 and release 2026.8.6.

When the user re-enters credentials during reauth, _async_try_login
was still calling start_session(), which silently kept reusing the
cached (possibly stale) session from the settings file. Pass the flow
origin through and call reauthenticate() for the "reauth_confirm"
origin so the entered credentials are actually used.

Also bump aio-panasonic-comfort-cloud to 2026.8.8 and release 2026.8.6.
@sockless-coding
sockless-coding merged commit 438cebb into master Aug 22, 2026
5 checks passed
@sockless-coding
sockless-coding deleted the fix_reauth branch August 22, 2026 19:37
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