tomspark wrote:
Good news — nothing's broken. SparkBox pins Home Assistant to a specific tested version (right now 2024.12.5), so the in-app update won't jump past it on purpose — that's why it caps where it does. The way versions actually move forward here is through SparkBox itself: when we ship a newer tested Home Assistant, sudo sparkbox update brings it down for everyone. One heads-up on the Portainer rename trick — a SparkBox update will reset Home Assistant back to the pinned image, so that change won't stick, and hand-jumping HA versions is often exactly what causes the "start over" pain. Smart call making a backup first. I'll flag bringing a newer Home Assistant into an upcoming update.
TestedEcho wrote:
sorry for coming back to this, the 2024 version is that the last version you checked and works well with sparkbox? cause when fumbling around in docker, the latest stable version seems to be 2026.6.1. but it also shows another version you can choose that is officially from home-assistant themselves. which also is that 2024 version. just looking around what works best and seeing this confused me after reading your answer.
tomspark wrote:
You read it right, and good question. 2024.12.5 is genuinely the Home Assistant version SparkBox pins and tests right now, which is why the in-app update stops there. But you've spotted something real: that pin is well behind current Home Assistant, so I'm flagging it to get bumped to a newer tested build, and then everyone moves up cleanly with sudo sparkbox update. Your manual update to the latest does work, but heads-up like before: a SparkBox update will snap Home Assistant back to the pinned image, so your instinct to back up first is exactly right. Jumping that many versions can also need a few config tweaks on Home Assistant's own side, so the backup covers you there too.