Fully Kiosk Browser on Fire HD 10 & 7 Becomes Unresponsive Every 2-3 Days

Third party integrations
1

I’m running HA in Fully Kiosk Browser (paid) on 2x Fire HD 10 tablets & 1x Fire 7 tablets + the HA integration, and the dang things keep locking up every 2-3 days. Can anyone help suggest what logs I should be checking or what I should try? Also, I’m aware this might not be a HA issue, but a Fully Kiosk Browser or Fire Tablet/Android issue.

They quit working at different intervals, like yesterday I had to mess with the one by the garage door because it was unavailable while the other two were still working, and today the one by the front door is unavailable, looks like the front door one went offline at 21:57 last night. I’ll notice it in HA because all the entities for that tablet are unavailable, or when I walk up to the tablet or trigger the light sensor, it doesn’t come up. The screen stays black. To get it working again, I press the power button, and then have to launch Fully Kiosk Browser.

IMG_1578
IMG_15781920×1237 106 KB

IMG_1579
IMG_15791920×1126 120 KB

Kiosk Browser Unavailable
Kiosk Browser Unavailable1008×1375 117 KB

I used Fire Toolbox to debloat the tablets. I’ve got the integration set up in HA with automations for the outlet to turn on/off depending on the battery. I updated the Fully Kiosk Browser firmware on the tablets recently to 1.55.3 and checked everything again with Fire Toolbox.

I’ve looked in HA Systems/Logs. Only Home Assistant Core has anything related to Fully or the IP of the tablet that’s gone down, and there’s nothing helpful there. Only things like (X’s placed by me)

Logger: homeassistant.components.fully_kiosk
Source: helpers/update_coordinator.py:325
integration: Fully Kiosk Browser ( documentation, issues)
First occurred: July 13, 2024 at 12:55:44 PM (3 occurrences)
Last logged: 5:45:32 AM

* Error requesting XXX.XXX.XXX.182 data: Cannot connect to host XXX.XXX.XXX.182:2323 ssl:False [Connect call failed ('XXX.XXX.XXX.182', 2323)]

or

Logger: homeassistant.components.fully_kiosk
Source: helpers/update_coordinator.py:318
integration: Fully Kiosk Browser (documentation, issues)
First occurred: July 13, 2024 at 1:03:04 PM (8 occurrences)
Last logged: 5:02:58 AM

Timeout fetching XXX.XXX.XXX.182 data

or

Logger: homeassistant.components.fully_kiosk
Source: helpers/update_coordinator.py:344
integration: Fully Kiosk Browser (documentation, issues)
First occurred: July 13, 2024 at 12:55:43 PM (1 occurrences)
Last logged: July 13, 2024 at 12:55:43 PM

Error fetching XXX.XXX.XXX.182 data: (500, "Remote admin server can't find a running Fully activity...")

The Fully Logs aren’t much help, either, and don’t really line up with when the tablet went unavailable except the 2 at 21:57:

2024-07-13 11:16:03 INFO Exit app
2024-07-13 11:16:09 INFO Start app as launcher, ver. 1.55.3 (101284)
2024-07-13 11:23:01 INFO Exit app
2024-07-13 11:23:06 INFO Start app as launcher, ver. 1.55.3 (101284)
2024-07-13 12:35:37 INFO Exit app
2024-07-13 12:35:42 INFO Start app as launcher, ver. 1.55.3 (101284)
2024-07-13 12:55:51 INFO Exit app
2024-07-13 12:55:56 INFO Start app as launcher, ver. 1.55.3 (101284)
2024-07-13 20:53:06 WARNING The foreground service has restarted, will try to restart the activity...
2024-07-13 20:54:51 WARNING The foreground service has restarted, will try to restart the activity...
2024-07-13 21:01:46 WARNING The foreground service has restarted, will try to restart the activity...
2024-07-13 21:29:25 WARNING The foreground service has restarted, will try to restart the activity...
2024-07-13 21:29:27 ERROR Unresponsive WebView rendering process was killed! Restarting app...
2024-07-13 21:29:27 ERROR Unresponsive WebView rendering process was killed! Restarting app...
2024-07-13 21:29:27 INFO Exit app
2024-07-13 21:29:32 INFO Start app as launcher, ver. 1.55.3 (101284)
2024-07-13 21:33:24 WARNING The foreground service has restarted, will try to restart the activity...
2024-07-13 21:34:32 WARNING The foreground service has restarted, will try to restart the activity...
2024-07-13 21:39:03 WARNING The foreground service has restarted, will try to restart the activity...
2024-07-13 21:57:06 WARNING The foreground service has restarted, will try to restart the activity...
2024-07-13 21:57:18 INFO Accessibility Service connected
2024-07-13 23:09:11 WARNING The foreground service has restarted, will try to restart the activity...
2

I have the same kind of issues with my fire tablets. I wish I could go back and get “normal” android tablets. Fully Kiosk Brower has documentation suggesting not to use Fire tablets because they have so many issues. I plan on replacing mine at some point. I know this isn’t helpful, sorry. Hope you find a solution.

3

I have the same issues and have a normal tablet, so the problem is not fire tablet

2 Likes
4

Agreed, I have a Lenovo and getting the same error.

homeassistant.components.fully_kiosk
Source: helpers/update_coordinator.py:318
integration: Fully Kiosk Browser
1 Like
5

I have a Samsung Tab A7 that I purchased to replace one of my three Lenovo M8s and while the stability has improved, I still receive the unresponsive notices (looks like as a result of network issues perhaps). I did change two things to at least eliminate the nagging of the notice. In Fully Kiosk, under Settings/Web Auto Reload, I turned on Auto Reload on Network Reconnect and Delete Cache on Auto Reload. In configuration.yaml in HA, I filtered anything short of an error (i.e., no more warnings) in my HA log as follows:

logger:
  default: warn
  logs:
    homeassistant.components.fully_kiosk:  critical
6

HI, I’m facing the same issue on my two Fire Tablets.
Did you solve the issues meanwhile?