feat(container): update image ghcr.io/home-operations/home-assistant (2026.8.3 → 2026.9.1)

[bot-akira]

This PR contains the following updates:

Package	Update	Change
ghcr.io/home-operations/home-assistant (source)	minor	2026.8.3 → 2026.9.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

home-assistant/core (ghcr.io/home-operations/home-assistant)

v2026.9.1

Compare Source

• Fix SMTP attaching valid images as files when content sniffing fails (@​Chang-Jin-Lee - #​176774) ([smtp docs])
• Warn that removing an app deletes its data in repair flows (@​agners - #​181009) ([hassio docs])
• Fix receive backup streaming (@​MartinHjelmare - #​181012) ([backup docs])
• Fix potential deadlock in receive_file backup util (@​emontnemery - #​181070) ([backup docs])
• Add missing state_class for miele filling level sensors (@​astrandb - #​181093) ([miele docs])
• Update python-roborock to 7.2.3 (@​Lash-L - #​181096) ([roborock docs])
• Bump vizaio to 0.6.1 for vizio state_extended 404 fallback fix (@​raman325 - #​181131) ([vizio docs]) (dependency)
• Stop rounding Amber Electric prices to 2 decimal places (@​romeovan - #​181157) ([amberelectric docs])
• Fix host override ignored in UniFi Protect public-only mode (@​RaHehl - #​181176) ([unifiprotect docs])
• Purge unreachable deleted devices on device registry load (@​emontnemery - #​181207)
• Bump pydaikin to 2.19.1 (hotfix) (@​GhislainC - #​181219) ([daikin docs]) (dependency)
• Fix Besen config flow schema serialization (@​moryoav - #​181223) ([besen docs])
• Speed up lookup of colliding orphans in device registry (@​arturpragacz - #​181244)
• Revert orjson to 3.11.9 (@​emontnemery - #​181245) (dependency)
• Bump aioflo to 2026.9.3 and scope Flo consumption by device (@​BradKollmyer - #​181246) ([flo docs])
• Bump serialx to 1.10.0 (@​puddly - #​181249) ([serial docs]) ([usb docs])
• Bump env-canada to 0.19.2 (@​michaeldavie - #​181250) ([environment_canada docs]) (dependency)
• Bump python-hotspring to 2.1.0 (hotfix) (@​Moustachauve - #​181256) ([hotspring docs]) (dependency)
• Bump samsung-exlink to 1.1.1 (@​balloob - #​181260) ([samsung_exlink docs]) (dependency)
• Reject Hot Spring Spa Network Adapter (SNA) in config flow (hotfix) (@​Moustachauve - #​181261) ([hotspring docs])
• Update knx-frontend to 2026.9.4.63549 (@​farmio - #​181268) ([knx docs]) (dependency)
• Allow empty motionEye usernames (@​frenck - #​181270) ([motioneye docs])
• Handle Tradfri devices without a firmware version (@​frenck - #​181276) ([tradfri docs])
• Update frontend to 2026082.6 (@​bramkragten - #​181293) ([frontend docs]) (dependency)
• Bump reolink_aio to 0.21.15 (@​starkillerOG - #​181300) ([reolink docs]) (dependency)
• Bump pylitterbot to 2025.6.5 (@​natekspencer - #​181346) ([litterrobot docs]) (dependency)
• Bump uiprotect to 16.6.1 (@​RaHehl - #​180670) ([unifiprotect docs]) (dependency)

v2026.9.0

Compare Source

https://www.home-assistant.io/blog/2026/09/02/release-20269/

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[bot-akira]

Tip

Routine: only container-image and chart-version changes; 2 resources across 2 apps

image	from	to	upstream
ghcr.io/home-operations/home-assistant	2026.8.3@sha256:16ca44…	2026.9.1@sha256:1bcf77…	❔

_{konflate 0.6.3 · rendered 08e0ad5 · full diff →}

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.