Localhavenupdate-watch
Is it safe to update?
Before you run docker compose pull: we already did - on a throw-away machine, with real images and test data
(users, files). Each verdict is one tested scenario: snapshot, update, app check, restore drill.
Apps we watch
6 apps · 19 verdicts · last test 11 Oct 2026
All verdicts
Reported by users for this release (8) - not part of our test
- LIFX bulbs going unavailable: the fix is merged for 2026.10.2 and is not in 2026.10.1 (core #185640)
- MQTT select entities can stop Home Assistant from starting (core #185571, open)
- Lutron Pico buttons fire a single press twice (core #185449, open)
- Tasmota energy sensors lose their state class (core #185407, open)
- A hung DNS lookup can block one hostname until a restart (core #185645, open)
- UniFi Protect: snapshots fail with HTTP 503 and cameras go unavailable - 1 report (core #185706)
- Home dashboard: the welcome banner came back and dismissing it wiped favourites - 1 report (frontend #54822)
- Custom (HACS) integrations: some stop loading or lose an action until their authors update them (exact library pins, cv.vol, hass as first argument, pkg_resources); the built-in Tank Utility is switched off in 2026.10
Read by us on 2026-10-11 from the projects' issue trackers; not verified by us.
Reported by users for this release (6) - not part of our test
- 2026.10 lists 22 backward-incompatible changes in its release notes (counted 7 Oct) - read them first
- UniFi Network did not load for several users (core #184838 and #184987, closed since)
- LIFX bulbs going unavailable: the fix is merged for 2026.10.2 (core #185640)
- A false shell template repair for command line sensors, a Hue light crash and the Bosch SHC child lock: fixed in 2026.10.1
- MQTT select entities can stop Home Assistant from starting (core #185571, open)
- Custom (HACS) integrations: some stop loading or lose an action until their authors update them (exact library pins, cv.vol, hass as first argument, pkg_resources); the built-in Tank Utility is switched off in 2026.10
Read by us on 2026-10-11 from the projects' issue trackers; not verified by us.
GREEN update + app check + restore drill worked · YELLOW works with a step first · RED the update or the way back failed in our test.
How a verdict is made
- A new stable release appears (checked twice a day).
- A fresh test machine starts the PREVIOUS version and fills it with test data.
- A consistent snapshot is taken with the free safe-update tool.
- The update runs; the app must come back healthy with the same data.
- The snapshot is restored in a separate copy - proof you can go back.
A verdict is not a guarantee for your setup - read the release notes and keep backups. Made with AI assistance; tests run on our own machines. Not affiliated with the apps listed.
For agents and scripts
The same verdicts as free JSON: /api/verdicts.json, one app's newest test
/api/<app>/latest.json, one exact step /api/<app>/<from>-<to>.json (404 = not tested). Each answer carries the
scenario and the "not a guarantee" note. For AI coding agents there is a read-only skill, ask-before-pull, in the free
safe-homelab-ops skills.