Massive issues accessing HA

Installation Home Assistant OS
, ,
1

Hi there,

after a failed OS upgrade, after which I had to reinstall and restore from backup I had all things up and running when all over sudden last night various integrations failed and were not loaded. I had to reboot a few times and things looked good for about 15 minutes when now massive network issues (as it seems) are appearing. System responds slow, I cannot get anywhere. Dashboards are white, addons cannot be loaded because of ingress errors. I did several restarts, even a hard reboot of the entire system as I could not access from UI. It seems only related to HA itself as I can directly access some addons (EVCC oder Unifi Controller for example). So I can rule out general (local) network issues. It seems to be just HA itself. Anyone experiencing the same problem? At this point HA is rendered useless and I have no idea what happened, what causes the issue nor can I even get to the logs or something. The last change I did was really to OS upgrade to 17.0 because of which I had to completely reinstall (cyclic dependency on Adguard which I missed… lesson learned though). I wonder if this is related to the new OS version or something else is causing this?

2

If you use The Watchman integration, uninstall it.

It’s causing major issues.

4 Likes
3

Leave it to update overnight. Check again tomorrow.

4

Thank you so much for replying. Indeed I have it installed and will uninstall it right away.

5

System is getting rather hard to access, but trying

6

But how to uninstall it, when you did not access HA at all? Is there a useful hint?

7

if you have Samba add-on, you can delete the Watchman custom component folder and restart using Terminal

(First add-on’s to install always are Samba and SSH…)
repeat: always. before anything else :wink:

1 Like
8

Basically crash Watchman, deliberately. Yikes!

9

just check After update for the v0.8.1 2026-01-25 it briked my HA · Issue #222 · dummylabs/thewatchman · GitHub

it’s the only way to get your instance back

if Watchman is causing your troubles that is….

10

Thank you, I manage to do it by ssh, delete the Watchman in custom_componets folder and now ists running again.

1 Like
11

right, that would be valid too of course.
but do install Samba, it’s much easier to do with that, just from within your file manager (imho)

12

Maybe restart in safe mode from SSH CLI and uninstall Watchman may be the elegant workaround.

13

Sorry to ask but how can I do that? I already search for that but did not find it.
OK found it in the GitHub thread

14

oh but I headless, guess I need to get a head!?

15

Holy mother of… Man I just went through this and after ~2 hours I decided to boot in safe mode and narrowed it down to watchman…

Ripped that sucker off my system. :slight_smile:

16

Yes, however you may find it difficult to install SSH on a sluggish system, so the nasty alternate of Samba and deleting Watchman files to crash the errant task may be an option.

Update edit: Maybe rename, rather than delete may be a preferred option, just in case you got it wrong.

17

finally after you realize everything is crawling, just have to click and walk away. Come back later. +1 on another system resolved and saved

Thought I had ssh enabled, time to check that again