Same problem here since a few months. It’s fast again after (on Android) going to settings->apps->home assistant->force close (or whatever it is called on your phone). As it is fast in the browser as mentioned here already that seems to be a bug purely correlated with the (android) app - not your ha version
I’ve just had this start to pop up recently. (Fully up-to-date stock Android and HA app) Of note, it seemed to coincide with me creating and frequently viewing a dashboard with a history graph with LOTS of values (the sensor updates every 1/10th of a second). I’m just viewing it while I setup a new sensor, so eventually I will remove the graph/not view it anymore. I’ll be curious if the issue stops then.
Only fix for me has to been to force close the app and then it’s snappy again for a day or so.
1 Like
I’ve got the same issue lately. Only the app is slow. In browser ha is just as fast as usual
1 Like
Same issue here
any update on this?
yea, I seem to be getting this pretty often as well
2024-01-17 17:04:57.084 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140352984849728] tablet-bedroom from 192.168.120.8 (Fire7-Bedroom): Client unable to keep up with pending messages. Stayed over 1024 for 5 seconds. The system's load is too high or an integration is misbehaving; Last message was: {"type":"event","event":{"event_type":"state_changed","data":{"entity_id":"sensor.lxc_uptimekuma_106_network_out","old_state":{"entity_id":"sensor.lxc_uptimekuma_106_network_out","state":"8873.939375","attributes":{"state_class":"measurement","unit_of_measurement":"MB","device_class":"data_size","icon":"mdi:upload-network-outline","friendly_name":"LXC uptimekuma (106) Network out"},"last_changed":"2024-01-17T22:03:57.063983+00:00","last_updated":"2024-01-17T22:03:57.063983+00:00","context":{"id":"01HMCQ7M8740PFXQ90CC3YA68F","parent_id":null,"user_id":null}},"new_state":{"entity_id":"sensor.lxc_uptimekuma_106_network_out","state":"8874.438183","attributes":{"state_class":"measurement","unit_of_measurement":"MB","device_class":"data_size","icon":"mdi:upload-network-outline","friendly_name":"LXC uptimekuma (106) Network out"},"last_changed":"2024-01-17T22:04:57.075470+00:00","last_updated":"2024-01-17T22:04:57.075470+00:00","context":{"id":"01HMCQ9EVK86J7AK62QK3G8GXK","parent_id":null,"user_id":null}}},"origin":"LOCAL","time_fired":"2024-01-17T22:04:57.075470+00:00","context":{"id":"01HMCQ9EVK86J7AK62QK3G8GXK","parent_id":null,"user_id":null}},"id":46}
How has WallPanel been working out for you vs Fully Kiosk?
I found the best way to fix this is to goto you home assistant address in the the chrome app on your phone or tablet. Then click the three dots in the right corner of the chrome app then select add to home screen. Name the shortcut how you choose. When you click on the shortcut on your homescreen it will open HA dashboard but all the chrome options will be gone. It just shows the dashboard with no browser options like it would in the app with no lag though. If you are trying to connect remotely when you’re not at home use the app instead for me the app does not lag when I’m not on my home network. I think the app lags due to something with nabu casa while on LAN. Guessing it’s something in the script and it doesn’t know how to correctly choose which network to use when on a LAN. So when you are not on your local network it doesn’t have to try to decide between the two it just uses nabu casa.
thats incorrect even users who dont use nabu casa and have 1 defined URL still see this issue. Our suspicion is something changed in the frontend but its been very difficult to track and figure out the cause. Its something WebView related but its more random than that as a user may be fine now then see the issue in a month or longer.
Whether it’s nabu casa or not. The solution I presented works
Worked like a charm! The mqtt Feature is awesome, as I need to reload the page every time something from the frontend updates