v1.1.1 - Auth add-on: self-recovery from stuck browser sessions
🐛 Bug fix - Auth add-on no longer gets stuck in permanent "BROWSER_BUSY"
This release fixes a deadlock in the authentication add-on where screen-time reads and writes could get stuck returning 503 BROWSER_BUSY for hours, with no recovery short of manually restarting the add-on - even with no authentication session running.
What was happening
The add-on serializes all browser work behind a single lock. If that lock was ever left held by an orphaned task (a request killed at the wrong moment, or a Chromium launch that hung inside the virtual display), every subsequent screen-time call short-circuited to BROWSER_BUSY forever.
In Home Assistant this surfaced as the integration looking "down": screen-time sensors stuck on unknown, schedule/limit changes silently failing.
What changed
- The add-on now self-heals on the next poll cycle instead of staying wedged. It only fast-fails with
BROWSER_BUSYwhile a real sign-in is in progress; an orphaned lock is recovered automatically. - Browser-lock acquisition and Chromium launch are now time-bounded, so a hung browser turns into a clean, retryable error rather than an indefinite hang.
Impact / upgrade notes
- No re-authentication needed - your stored Microsoft session is untouched.
- Just update the Microsoft Family Safety Auth add-on and restart it.
- The Home Assistant integration is unchanged in this release.
Full changelog: v1.1.0...v1.1.1