I am new to HA, and have pretty much only set up an alarm system, using BWAlarm. I can also enable the alarm through Lovelace alarm card.
I am running HA 0.107.7 on a Rasberry Pi+. I am using Konnected cards for my alarm (5 cards, 30 channels). I can access HA from my desktop through Chrome, on my Samsung Tab A tablet running Android version 9 and HA App 1.8.0-144. All is well, and things update fast.
However, I bought a new low-cost Android tablet for wall mounting, https://www.amazon.com/gp/product/B082867SXP/. It seems reasonably fast and responsive for most things. I have very little loaded on. However, if I try to refresh the screen in the app, or from Chrome, it takes 2-3 minutes to finally render the screen. The Lovelace view has the alarm system card, a filtered entity card to show open sensors, and a button card. The same action on my Tab A takes 2-3 seconds. Unfortunately, if a reload is needed when someone enters the house, the siren will be going off before the refresh occurs.
The tablet is running Android version 9, and I have tried Home Assistant app, Wallpanel, and web url through Chrome. I believe all of these methods actually use Chrome to render.
I am connecting locally only, and have only given the apps (and Chrome) the direct http url, not the duckdns url.
I tried Ariela, but that app could not render some of my Lovelace cards (filter entities, button), and exposed all of my cards (I am using custom header to limit the cards seen by the wall tablet). The reload on Ariela was much faster, but the functionality was not what I was looking for.
So the problem APPEARS to be isolated to the new tablet, and likely to the Chrome engine rendering.
I could live with 10 second reload, but several minutes just won’t work. What should I be looking at on the tablet to adjust, diagnose, or replace? I hope it is just something needs tweaking, as I cannot see it reasonable to take that long to render.
Thanks
Chuck