-
-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Do not refresh OAuth token during Tibber unload #176595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
joostlek
merged 4 commits into
home-assistant:dev
from
honzup:tibber-unload-no-oauth-refresh
Jul 27, 2026
+136
−54
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
1310c4b
Do not refresh OAuth token during Tibber unload
honzup cf63edf
Exercise real timeout deadline in Tibber unload test
honzup e6627fd
Disconnect Tibber client via runtime data action method
honzup de33c6f
Test Tibber client handling through the integration
honzup File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's right, and worth spelling out.
rt_disconnect()reaches_reset_connection(), which takesLOCK_CONNECTbefore_reset_connection_locked()cancels the watchdog.reconnect()holds that same lock, and gets to it through an unbounded token refresh. So if the watchdog is mid-reconnect when the entry unloads, the timeout cancels the lock acquisition rather than the disconnect, and the watchdog survives.It's a deliberate trade rather than a fault this PR introduces. Before it, the unload awaited
rt_disconnect()unbounded: the watchdog did always stop eventually, but a half-dead socket could block the unload indefinitely and leave the entry inFAILED_UNLOAD, which needs a Home Assistant restart to clear. This swaps a state the user can't recover from for a task that can leak in a narrow window, and I'd rather leak the task.The force-stop path you describe belongs in pyTibber rather than here - the integration can't cancel the library's watchdog without reaching into private attributes. Part of it is already open as Danielhiversen/pyTibber#435, which makes the connect lock per-instance and bounds both
wait_closed()andclose_async(). That narrows the window without closing it: there's still no cancellation path that runs before the lock is taken, and the token refresh insidereconnect()is unbounded.