Trial and error I’m afraid. You could check your browser console to see if there’s any warnings/errors that give you an idea of what to try. Otherwise just remove cards one by one and see when the memory leak stops.
For me, the animated svg icons were prime culpit. It’s annoying as I rooted my Fire HD8 with Lineage OS - it’s way snappier and more stripped back, but the webview memory leak is something I haven’t been able to overcome despite many hours trying!
thanks for the tips! I will try this out.
You know, after reading FK documentation on this, they do NOT recommend Amazon tablets for FK Browser. Good to know, because next tablet I will spend a bit more to get a true android tablet, and hopefully avoid these issues.
They don’t recommend it for production use specifically, but there’s loads of people running Fire tablets as wall dashboards with no issues. I don’t even use the kiosk mode. But I agree - it’s worth weighing up whether spending a bit more on the tablet is worth it to avoid potential issues with a Fire.
Just for some horizon widening, i do successfully run two tablets around the house with FKB and HA.
I’m using tablets 7" and 10" from Lenovo. They are fairly priced and work just fine… 
I bought two of cheapest “decent” 10 inch tablets a good year, two ago (Lenovo Tab M10)- i thought they’ll be fine just for HA display. Well… they “kinda” aren’t. They are ok for simple HA lovelace, but when you build a complex lovelace with multiple pages it becomes painfully slow, if you intend to switch pages often.
So, it’s definitely worthed to buy a bit more pricey tablet. Now i have Xiaomi pad 5, it works really fast no matter how complex HA lovelace is. But, it’s appr. double priced as Lenovo…
thanks for the suggestion. I found my leak. I narrowed it down to this frontend integration for my blinds
you can see when I enable it on the green dot, the memory takes a nose dive, and then when I disable it (red dot), the memory recovers.
Ok, good to know!
Well done! Can’t see any svg files or animations in the code for that card so maybe a different issue to mine. Haven’t had chance yet but I have a feeling that an older Webview version might fix for me. I’ll report back if it does.
It’s been a week now and I just wanted to provide an update. Things are going really well now. My Fire tablet is actually operating quite smoothly and quite fast. For those of you who find a situation where performance is slow and crashing randomly definitely do some trial and error finding out which frontend integration is causing the performance issues.
I’m even running 1.49.1 which is what caused the issue in the first place but ever since removing that one front end integration things are going well.
My free memory still goes up and down over the course of days (compared to 12 hours when I had the issue before) however, it does not go below critical under 300 Megs, for example it can go down to 500 mags and then all of a sudden it can jump back up to 1100 Megs for whatever reason.
Firetablet has redeemed itself!
Thanks again @fenty17
I am very sensitive to light at night in the room and the fire tables backlight is pretty obvious in a dark room… I figured out that you can control the screen brightness and it seems like the accepted solution here is to turn it down to 0 at some point and then back to something higher during waking hours. That being said I would love it I could somehow configure or automate something along the lines of the following.
If 9pm dim to 0
if touched go back to 150 for 30 seconds ( assume someone is trying to do something, regardless of time of night ).
If no touch for 15 seconds and after 9pm go back to 0 for remainder of night
7am go back to normal behavior with brightness static at 150-200
Any help would be appreciated
-John
Lowest backlight is still too bright for sleeping for me (unless you have OLED).
I use fully rest command to turn off screen (via automation). My tablet has an option to wake up when i double tap on screen so i use this function. Combined with 15s auto-turn-off it’s ideal.
Since i have also programmed wake-up, i also use rest command to wake up tablet (also via automation).
@Protoncek - Could you send me screenshots showing the full FKB settings for double click to wake , and maybe the rest commands / automation you used to automate this behavior? Thanks !
-John
Double-click to wake up must be function of your tablet, so check that out in settings. (btw…not all tablets have it, but most newer do).
Regarding rest commands: you must have paid version of fully (or live with a warning sign all over the screen) - enable remote administration in fully’s settings and enter password you’ll use for rest commands. Then create rest commands in HA . Whole help section of fully rest interface is HERE .
Expamples for screen on and off - insert this in configuration.yaml (don’t forget to enter your IP and password!):
rest_command:
kiosk_screen_on:
url: "http://192.168.x.yyy:2323/?cmd=screenOn&password=enterpassword."
kiosk_screen_off:
url: "http://192.168.x.yyy:2323/?cmd=screenOff&password=enterpassword"
Then you just call service “rest_command.kiosk_screen_on”.
A word of advice: set IP of your tablet manually, don’t use DHCP!
BTW… you can easily test if above commands work (after enabling all necesarry in fully) by inserting http… line into browser’s address line and hit “enter” - if it works, tablet’s screen should turn on and off.
Warning in my log,
Logger: homeassistant.helpers.template
Source: helpers/template.py:583
First occurred: 8:07:11 AM (74 occurrences)
Last logged: 8:43:59 AM
Template variable warning: ‘dict object’ has no attribute ‘isScreenOn’ when rendering ‘{{ value_json.isScreenOn }}’
My sensor.yaml
#Fire_Tablet
platform: rest
name: fire_HD10_Main
json_attributes:
batteryLevel
kioskMode
screenBrightness
motionDetectorState
maintenanceMode
appFreeMemory
appUsedMemory
totalFreeMemory
totalUsedMemory
hostname4
ip4
mac
locationLatitude
locationLongitude
locationAltitude
startUrl
currentPage
value_template: ‘{{ value_json.isScreenOn }}’
Any suggestions?
After upgrading to lastest core (2022.11.5) I get the following error
Invalid config for [lovelace]: [kiosk_mode] is an invalid option for [lovelace]. Check: lovelace->lovelace->kiosk_mode. (See /config/configuration.yaml, line 36).
This is line 36 in configuration.yaml
lovelace: !include plancia_custom.yaml
and this is plancia_custom.yaml
kiosk_mode:
user_settings:
- users:
- tablet
hide_sidebar: true
mode: storage
dashboards:
lovelace-tablet:
mode: yaml
title: Home
icon: mdi:home
show_in_sidebar: true
filename: lovelace/lovelace-tablet.yaml
Any Advice?
I have the same issue. Were you able to fix this?
I had to turn motion sensor off completely to get it to stay off
Hey,
I can’t recall what the exact fix was but I think it’s in these posts.
I do recall putting the screen “always off” until motion then an automation to turn the screen back on.
just curios, why don’t you use the fully kiosk official integration in HA so, you don’t need to worry about yaml and obsolete commands.
I deleted the platform:rest yaml and it appears to work with no errors. Thanks for the suggestion.
The “add card” selection keeps appearing. Any option to lock this out? I have Fully Kiosk Pro installed and updated. I am also using Amazon Fire HD10.
I’ve set up a non-admin user but the Tablet keeps displaying the “add card”.
To remove I have to edit the Lovelace page to allow admin access which displays the top menu and then I am able to select Done.
Did you clear the cache of Fully Kiosk? Menu → Privacy check → Clear cache
Then restart the tablet.