Another job is running for job group home_assistant_core / fails to start

Installation Home Assistant OS
1

hardware: raspberrypi5-64
operating_system: hassos 17.1
homeassistant 2026.2.2
supervisor 2026.02.1

info keeps giving state: startup (expected running?)
companion app has lost connection
ping correctly returns

Yesterday I had a few updates which seemed to work OK until in the night.
new in trouble shooting here but when I try things like core stop I get another job is running for job group home_assistant_core
I have no idea why this all of the sudden started.

How can I fix this running job error and ultimately get my installation running again? It ran without any problems during nearly 2 months. It would already be OK for me to restore from an automated backup, if that is possible from the CLI.

2

Entso-e integration? You need to fix it:

9 Likes
3

bingo!
Thanks for the quick answer. It’s all back online again after I was able to successfully run

core stop
core restart --safe-mode

which gave me back the GUI where I could disable the Entso-e integration and restart HA.
It’s a pity that this integration can cause this problem…

5 Likes
4

Took some hours to find this topic, but finally HA is up again.

ha> login

(spawns root shell)

# cd /mnt/data/supervisor/homeassistant/custom_components
# mv entsoe entsoe.disabled
# reboot
9 Likes
5

all, thanks so much ! this saved my day…

unbelievable that 1 integration can stop the entire HA platform!

1 Like
6

WOW that was a nasty one! It took me a whole day to fix. Luckily it is a lazy Sunday; I could not have explained this on a random week day. “Why do the lights not work”?

A custom component that can take down Home Assistant. That should be something we want to prevent…

2 Likes
7

Thanks! Helped a lot.

Core wouldn’t stop at first. So perfomed a reboot, then was able to stop the core and start in safe mode if anybody has the same issue.

1 Like
8

Thanks for this info! had the same issue since today. took me 6 hours of troubleshooting before i found out…

1 Like
9

how can I get there?
I think I disabled SSH.
I don’t have a mini HDMI cable to connect my RP4 to a monitor.
Putting the sd card into my desktop’s reader still doesn’t allow me to alter files as I’m not the owner then.
-edit-
I opened above mentioned directory in terminal
With the sudo command I could run:

sudo mv entsoe entsoe.disabled

and it worked!

10

Is there a line command I can put into my browser to start in safe mode? Or how can I do this? I have a HA Green and use a MacBook Air. I don’t know how to use Terminal or any of the command line editors

11

After everything failed I have now connected a keyboard and a monitor. I can stop the core but when I type in core restart --safe-mode I always get error message another job is running for job group home_assistant_core. I cannot get out of this. Anyone any idea how to solve this issue?

12

Follow the entsoe post/thread.
Disable the entsoe integration through the cli.
Starting in safemode did not work for me either

13

Damn this post took me a while to find but saved the day.

THANKS!!!

1 Like
14

ok, finally I managed to stop the integration. For me it worked in the safe mode to go into File Editor and manually delete all files and directories of the entsoe integration (/homeassistant/custom_components). Then after reboot it could start the GUI without getting hung up.

15

Nice going, it worked for me! Many thanks!

16

Glad someone directed me here. Was working the complete Sunday on fixing this, without succes. I thought the port mapping in Docker was the issue, but is was not. Hopefully it is fixed soon. Thanks again!

17

The solution for me was to not stop core first but instantly type in the core restart --safe-mode command which was then executed. yes, sometimes funny as it was reported differently also in this thread above.

18

@Snappy, thank you. I would have had to start from scratch if I hadn’t found your post. Any suggestions on how to restore entsoe once sufficient time has passed to fix the underlying bug?

19

image
image1116Ă—1361 88.7 KB

The fix is released. @SafeHomeTogether Well too restore: just deploy it like you did when installing this setup a long time ago.

1 Like