Everything since 2.9.0. If you installed from the Marketplace (or HACS) on the stable channel, this is the first release you receive since 2.9.0: the pre-release 2.9.1rc1 was only offered with "Show beta versions", so everything it brought is listed below.
What's new
- The integration settings in the Family Link card. For an administrator, "Configure the integration" in the card's settings opens a dialog with the tamper protection rules, the lock that keeps the always allowed apps reachable and location tracking, worded as in Home Assistant's options screen. The server checks the administrator; the users allowed to control Family Link stay in Home Assistant's options screen. Strict mode rules and the lock option now apply without reloading the integration; location tracking still reloads it.
Changed
- Strict mode is now called "Tamper protection" in the options screen and the cards, with a rewritten description. Each rule lists what it protects (bedtime, daily limit and school time: switching on and off; the weekly schedule: bedtime hours and each day's quota), and the card explains the rules: untick one to be able to change it from Family Link. The child's switch keeps its entity id (
..._strict_mode), so automations are unchanged. In the card, the rules show only while the child's tamper protection is on.
Fixed
- The screen time cards' editor names the YAML
sources. They count in the total but had no field in the visual editor: a PC listed both as a device and as a source was counted twice with nothing on screen to show it. The editor now shows them among the other time sensors, where they can be removed; one kept keeps its name, icon and limit. - Strict mode puts a Home Assistant lock back on a device Google stops listing. Google's applied limits sometimes answer without a child's devices: lock and bedtime are then no longer applied, the device switch reads "usable", and strict mode skipped its lock rule for a device without data. A phone locked from Home Assistant at 21:33 stayed free from 22:05 to the end of bedtime. Strict mode now locks such a device again when Home Assistant locked it today (three tries, then the usual warning and
last_tryevent); it places or lifts no lock of its own without data. An override that names no device no longer drops the device from the reading, a device row that cannot be read is logged with what Google sent, and the device switch has alimits_reportedattribute. - Google's 503 no longer flood the log. Google answers 429 and 5xx in waves and every read is retried at the next refresh with the last data kept, but one failed read wrote up to five error lines (the response body, the URL, the failure at two levels). The API layer now logs a 429, a 5xx, a timeout or a dropped connection at debug, and the coordinator warns once per read and per child, then at debug for 15 minutes before warning again if the outage lasts. A lasting refusal (403, for instance) is still an error. This covers every read: family members, apps and usage, time limit rules, applied limits, screen time, location, contact restriction and batteries.
- A bonus counts down. Google ends a bonus at the time it was granted plus its duration, but the time left stayed at the granted amount (
Active Bonus,Screen Time Remaining, the switch'sremaining_minutes) until the bonus vanished, then fell to 0: at 57 minutes into a 60-minute bonus Home Assistant still read 60 while the Family Link app read 3 (#255, thanks to @Jam3s97). The time left is now counted down from the bonus's own timestamp at every refresh.Active Bonushas a new attributebonus_granted_minutes, andtotal_allowed_minutesstays the granted amount.
Update: a full Home Assistant restart is needed (Python code and translations), then a hard refresh of the browser (Ctrl+Shift+R) for the cards.