One robustness correction for strict mode, seen live the same evening. Update through HACS and restart; nothing to change in your configuration.
Fixed
- A single failed read of the time limit rules made strict mode "correct" everything. When Google answered an error (a 503 on 2026-09-26, three minutes after a restart) to the time limit rules request, the client returned a default result, bedtime off and no schedule at all, that looked like a real answer. The coordinator never fell back to its cache, and strict mode read it as bedtime switched off, school time switched on and seven bedtime slots missing: nine corrections in 25 seconds and seven notifications, for nothing. The client now raises on such an answer, the coordinator uses its cache as designed, and strict mode skips a child whose rules or applied limits could not be read on that refresh: neither a reference to take from Google nor anything to correct.
Notes
- Together with 2.2.2 (a quota changed from Home Assistant is declared to strict mode before it is written), this closes two ways strict mode could act on something other than the truth.