"Add-On failed to start at boot"

Third party integrations Node-RED
1

Hi everyone!
These last weeks I’ve been updating many things in my home, including my Home Assistant (from the december 2024 to january 2025 version), my router’s firmware and I also switched ISPs, so I had a slightly tough time trying to debug many things.

When I first updated Home Assistant (I’m running on a Yellow) everything seemed to work fine, but then after a few restarts I had many errors with add-ons, first there was an error saying that the add-ons repositories were not found and these errors had an option to “fix” the issue by uninstalling the add-ons (!).
These issued seemed to go away on their own, maybe it was an internet connection issue, I’m not sure. But now I’m getting a message saying

“Add-On failed to start at boot”

Home Assistant SupervisorWarning ⸱ Reported by Home Assistant Supervisor

Add-on Node-RED is set to start at boot but failed to start. Usually this occurs when the configuration is incorrect or the same port is used in multiple add-ons. Check the configuration as well as logs for Node-RED and Supervisor.

Use Start to try again or Disable to turn off the start at boot option.

This only happens when rebooting the whole HA Yellow device, but when I restart only Home Assistant or only Node-RED, it all works fine. I’ve checked the Node-RED add-on logs, because during the updates I was having lots of errors with Telegram and Join nodes, but now these have been solved (by configuring routers, not HA or Node-RED).

So if anyone could help me understand where to look at to resolve this issue I’d be glad :slight_smile:

Thanks!
Rodrigo

2

Restarting home assistant only restarts the home assistant container all other containers, like node red and the supervisor, keep running.

Rebooting the host machine restarts everything. You should only need to do this rarely, like after OS updates.

I’ve had the Zigbee2mqtt add-on not start like that after a reboot. Hasn’t happened for a while though. I just check all my add-ons are running after a reboot.

I assume you have the “Start on boot” and “Watchdog” add-on switches on?

3

Thanks @tom_l

Yes, I have both “Start on boot” and Watchdog enabled for Node-RED.

Yep, I knew that Node-RED kept running while restarting Home Assistant. I’ve been having some network issues that were only updated after doing a full reboot (or at least, my only way of verifying if things were running properly was with a full reboot), but yes, normally I don’t do a full reboot, just a HA restart.

I just did a full reboot and things started normally, for the first time these days! I don’t know what was happening. Just wanted to post here to see if anyone else was having similar issues. Will post back if I see these failures again.

Thx
R.