I’ve seen modern web designs use ‘lazy loading’ (requesting status/value updates ONLY for displayed entities) to avoid this problem. I hope that can fix these issues with HA.
I have been testing multiple tablet. Normal tablets (lower-end Amazon Fire HD10, older Samsung A8, etc) run any graphic intensive web page (Amazon. Home Depot, etc, etc) just fine. Even my Samsung S7 is slow and barely usable.
All, even the older tablets, load non-HA web pages quickly (over Wifi N or AC) and are all very responsive to touch/click… but Home Assistant’s page is ridiculously slow, unusable
the HA pages gets exponentially slower, and even hang, when even simple, basic Auto-entities cards using only one or two simple filters with basic/default/non-fancy card graphics – anything with more than 10 entities to render is 10 to 60+ seconds to render!?
Of course on my very fast PC it renders in under a second… I suspect that indicates its CPU dependent. Which indicates that HA’s web page are constantly loading all entity status/values… which overloads the CPU, and that never lets up. I have >2500 entities so it never lets the CPU rest.
You reported a 3rd party card issue in the core frontend repository rather than in the third party developer’s repository. You supplied no configuration details and you lied about the issue template questions. This one in particular:
So I’m not really surprised no one is going to listen to you.
FYI I use Auto entities quite a bit and have no issue with displaying HA dashboards on my tablet.
I did not, not at all. But I used that as an extreme example of the problem. Sorry if that confused you. 190 words in that description, only 1 of them is ‘auto-entities’… also, repro says exactly this…
get tablet
run HA web page
stare for a long time hoping it actually fully renders and becomes responsive
no-where does it say anything about 3rd party integrations, nor non-native pages.
This issue has been report on several posts across the last few years, I spent the past 2 days searching and trying different tablet / android tweaks before posting. Tying 3 different launchers and removing all other apps, only having native android stuff and HA companion… that is all. And clearning Chrome completely. Oh, and trying 2 different tablets… on is an S7, which still lags on HA
Say what you want, but the HA web UI has poor performance. I already pointed out web sites that are 100x more graphic intensive and run ads that are 10x faster than even then most basic HA native page.
You dont want to admit that fine… doesnt make it any less true, and the fact you wont even look into it says a lot.
Instead of your answer bing… “please you send me a video showing the issue” … it was “not out problem, must be a 3rd party issue”
and you so easily also blame 3rd party integrations on the problem even when the issue shows on native pages? but you ignore that part of my posts
When I run in safe mode, and open the Areas dashboard (native yes), from the time the page changes, to the time anything shows in the view is 6 seconds. And that is not including the refresh of the cams that happens after that (cam refresh is normal of course).
Is it faster than not being in safe mode, of course it is. But just like when I was at Microsoft, we only test in safe mode as a first step to eliminate core code and kernel issues… it was a first step. We still cared about figuring out if there was an issue with the core memory handlers, communication pipelines, etc… issues that might only be exposed by 3rd party code.
I’m clearly not going to create an extensive dashboard the likes of what I have purely in native cards… no one does, not even you I’d bet
