Web App becomes unresponsive on android wall tablet

I have a dedicated wall-mounted tablet for controlling my HA in one room, running Android 8.1 and using the Progressive Web App (PWA), and occasionally MPDroid for selecting audio sources. I find that the web app can appear to become unresponsive after a while, and even when I pull down to refresh, the issue still appears.

Specifically, using the Lovelace UI, on a view with light cards for light groups (see configs below), I find that touching the button will not toggle the on-off state. Instead I have to go into the 3 dots menu and touch the slider to change the state. When I try to toggle directly via the icon on the card nothing happens, and no warning appears in the logs.

It seems to happen more when the tablet is left used for quite a long time, say an hour or so. However, as I say, a two finger pull-down to refresh the UI view does not make it suddenly start working again. This behaviour does not present itself when I use the PWA on my Android 7 phone, nor when I enter HA via the Chrome browser. I am running HA 0.92.1 on a Raspbian venv.

Does anyone with experience of android wall tablets have any suggestions as to what I could try?

light-groups.yaml

# included by top-level node light: 
# see
# https://www.home-assistant.io/components/light.group/
- platform: group
  name: K Work
  entities:
    - light.innr_rs_128_t_12345678_1
    - light.innr_rs_128_t_98765432_1
#  <snip>
- platform: group
  name: K Relax
  entities:
    - light.philips_ltw013_12345678_11
    - light.philips_ltw013_98765432_11
# <snip>
- platform: group
  name: K Colour
  entities:
    - light.gledopto_gl_s_007z_12345678_12
    - light.gledopto_gl_s_007z_98765432_11
# <snip>

ui-lovelace.yaml

views:
# <snip>
  - title: Light Groups
    id: view_light_groups
    cards:
    - type: light
      entity: light.k_work
    - type: light
      entity: light.k_relax
    - type: light
      entity: light.k_colour
# <snip>

did you fix this?

Hi @tomcoleman I did not get a specific fix for this issue, but it was dependant on the client versions specified above. As I have moved off those onto newer clients, this issue is now moot.