I too have that Problem, It started with one of the last Updates I guess. I can’t say when, as I didn’t notice it at first and blamed my Zigbee Setup for Automations not firing /not firing exactly. A Week ago I wanted to edit them, to see what I could simplify, but I got the same behavior from HA as it is described here in the Thread:
Timeout after a few Minutes using the Web-UI or App. Access is only possible right after a restart.
Since I used an USB-SSD as my Main-Drive on a Raspberry Pi 3B, I thought it may be the culprit. It ran the last 3 years in that constellation, without any non-resolvable or understandable errors. So I changed the Drive to a fresh SSD in a new USB-Case with Trim support.
I installed fresh, on a new drive, without importing any Backups, and the Problem still persists. I Replaced The Network Cable, Changed the Network-Switch the Pi is connected to, Replaced the PSU with a rather powerfull one (5V 6A), and by now I was about to replace my Raspberry Pi 3B with new Hardware (Somehting NUC-Like), when I found this thread…
Well, I hope we can find a solution, If all our Problems maybe have the same root… I will now roll back Home Assistant Versions and see if that changes anything.
Mine seems coupled with an event in the log where webhooks received some kind of invalid incoming data. Still trying to trap it along with 6 other projects.
I do have a sensor which receives erroneous data (blank instead of JSON) too but that’s every minute that my washing machine is off (most of the time) so more often that the issue I’m getting I believe.
I did just notice something interesting when my doorbell just went offline (running through scrypted on a separate VM in Proxmox on the same hardware) which caused me to look to see if Proxmox had crashed or something. But then checked the summary for my HAOS VM and saw the graph where it seems to spike every 15 mins!
Having a similar issue. Might be caused by zha (as the vmware vm my hus band made seems to losecobtact with the usb (skyconnect) and then i can’t control connected livhts and devices
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:521
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 09:51:08 (2 occurrences)
Last logged: 09:51:27
[139796634957664] xxx xxxx from 127.0.0.1 (Home Assistant/2024.12.1-14604 (Android 14; SM-G996B)): Disconnected: Received non-Text message.
[139796633519440] xxx xxx from 127.0.0.1 (Mozilla/5.0 (Linux; Android 14; SM-G996B Build/UP1A.231005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.39 Mobile Safari/537.36 Home Assistant/2024.12.1-14604 (Android 14; SM-G996B)): Disconnected: Received non-Text message.
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:521
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: December 12, 2024 at 11:09:49 AM (64 occurrences)
Last logged: 2:59:40 PM
The issue I was having was related to the docker network my swag container was running in. I deleted the container and the network and created fresh ones. That solved the issue. I’ve run into this problem with other tools in the past. Sometimes something happens to the docker network that causes connections to get refused, dropped, or closed. I haven’t pinpointed exactly what causes it. But recreating the network solves the issue for me.
