Curious if any Devs are looking at making the companion app perform better.
All pages are super slow to load on my tablet, which has been reporposed from being a dashboard for another app for multiple years, and perormance was perfectly fine on that and web pages
The poor performance is extreme when using auto-entities. When a Dashboard view itself has more than a few auto-entities cards. Even for super simple (not ‘custom’) displays like the below screenshot – it is unusable, the app basically hangs for 60+ seconds.
On my super fast PC everything renders in under a second, but on my tablet is can often take 60+ seconds to render all the auto-entities cards seen below. That screen below is not usable at all on the tablet.
I suspect the problem is HA’s mobile app design needs changing? If I had to guess, its constantly loading all entity values instead of doing lazy loading (loading only those values needed for the view/page being displayed. If its not doing lazy loading, this can bog down the CPU of tablets.
Chrome, same issue… I suspect the HA page is querying the server and asking to update all entities in-memory, then the processing is going to overload the CPU for weaker tablets.
‘custom cards’ is most of Dashboards since you cant do much of anything without custom cards. 90% of my dash is custom cards.
I have cleared cache, rebooted, etc… its slow. And yes, it gets slower over time.
Auto-Entities cards are super slow when there are more than about 10 to 15 entities on a View. For example, I have a card with 15 auto-entities, it can take a second or two to load (sometimes). The screenshot has 26 entities, it can take 10 to 60+ seconds.
Even switching to a different View (using the top toolbar), can take 30 seconds. I suspect because the HA pages are constantly refreshing/loading entity values, reducing the CPU cycles available for the page to switch.
in contrast, loading pages like Amazon.com, HomeDepot.com and others that are VERY graphic intensive, and constantly loading/cycling images… takes 1 to 2 seconds consistently.
yes but if the issue goes away that means the custom cards are the ones that need to have issues raised against to get corrected. Your comment about Chrome having the same issue further suggests that. Either way if you see the same issue in Chrome its not anything the app can handle.
First try to disable custom cards one by one to find the potential culprit and rule them out via process of elimination. Thats the first step in troubleshooting dashboard issues.
Fair… its not an app issue. I’m now 99% sure the way HA’s web is calling for updates is the problem. I suspect they are not lazy loading - and its bogging down the CPU.
