Repository navigation
Predbat will not run after performing hardware upgarde and full restore of HA #5049
Closed
Javert1969
started this conversation in
General
Replies: 1 comment 1 reply
|
OK - I did another complete full backup and restored it to the new HA - Predbat is now working - I still saw a bunch of errors in the console upgrade log about Predbat, but it then seemed to repair them itself! |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I am not 100% sure whether this is a Predbat issue or something else. I am upgrading from an HA Green to a Beelink Mini PC.
After doing a full restore of backup, Predbat will not start.
Error from the HA Supervisor logs: "HA Supervisor logs - "2026-09-11 09:38:49.748 ERROR (MainThread) [supervisor.apps.app] Could not start container for app 6adb4f0d_predbat: Another job is running for job group container_app_6adb4f0d_predbat"
Error from the HA console whilst performing the upgrade attempt a 2nd time: "...predbat uses build.yaml which is deprecated. Move build parameters into the Dockerfile directly"
I am hoping I can work around this but doing a backup without the Predbat app from the old hardware, then re-install Predbat and re-install my apps.yaml, but maybe this should be raised as an issue somehow unless I'm doing something wrong in the restore?
All reactions