Recent unreliability causing disconnections (caused by browser mod)

Can someone please advise me on how to diagnose this problem?

[07:51:02] INFO: Starting NGinx…
14 Jul 07:51:02 - [info] Starting flows
14 Jul 07:51:02 - [info] Started flows
14 Jul 07:51:02 - [info] [server:Home Assistant] Connecting to http://supervisor/core
14 Jul 07:51:02 - [info] [server:Home Assistant] Connected to http://supervisor/core
14 Jul 07:51:03 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
14 Jul 07:51:03 - [info] [server:Home Assistant] Connecting to http://supervisor/core
14 Jul 07:51:03 - [info] [server:Home Assistant] Connected to http://supervisor/core
14 Jul 07:51:02 - [info] User directory : /config/
14 Jul 07:51:02 - [warn] Projects disabled : editorTheme.projects.enabled=false
14 Jul 07:51:02 - [info] Flows file : /config/flows.json
14 Jul 07:51:02 - [info] Server now running at http://127.0.0.1:46836/
[07:51:02] INFO: Starting NGinx…
14 Jul 07:51:02 - [info] Starting flows
14 Jul 07:51:02 - [info] Started flows
14 Jul 07:51:02 - [info] [server:Home Assistant] Connecting to http://supervisor/core
14 Jul 07:51:02 - [info] [server:Home Assistant] Connected to http://supervisor/core
14 Jul 07:51:03 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
14 Jul 07:51:03 - [info] [server:Home Assistant] Connecting to http://supervisor/core
14 Jul 07:51:03 - [info] [server:Home Assistant] Connected to http://supervisor/core

I have disabled all tabs/flows, thinking that it’s a loop I’ve caused - no better.

Try connecting directly to Node-RED instead of through the Home Assistant Supervisor proxy.

Uncheck “Using the Home Assistant Add-on” and enter the correct server details manually.

Documentation:
https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/#configuration

That seems to have helped in the logs - will check tonight to see if automation are running again and it’s more responsive.

Thank you @Kermit

If that fixed it for you, you’re likely running into this issue:
https://github.com/hassio-addons/addon-node-red/issues/1986

I now have this issue:

14 Jul 09:51:07 - [info] [cronplus:30 mins before sunrise] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application

14 Jul 09:51:07 - [info] [cronplus:sunrise and sunset and pt] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application

14 Jul 09:51:07 - [info] [cronplus:Every 15 mins on Sat and Sun] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application

14 Jul 09:51:07 - [info] [cronplus:Every 15 mins on MON-FRI 16:00-23:59] System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application

It looks like Browsermod has gone crazy and added 3000 devices - disabling!

Wow, that was painful. The only way to cure it was to re-install browser-mod (after i’d removed it) to be able to deregister the 3372 devices via Developer Tools > Actions.

Then delete the integration and finally, delete it from HACS. I won’t be using that tool again.

FYI: I did NOT have ‘auto register’ new browsers enabled.

I LOVE this community :slight_smile: