I’ve been using licensed Fully Kiosk for years and its never worked the way I wanted. It ended up “always on” and eventually killed my Lenovo M10 screen.
Now I’ve got a new Samsung A8 (2022 version) and I’d like to set it up correctly this time. I still cannot find the right way to get the behaviour I want.
After 10 (or whatever) minutes of no activity or motion, turn off the screen. To black.
On motion, turn on the screen, but have the Fully Kiosk screensaver active. I use a DAKboard URL as my screensaver in Fully.
Only when I walk up to the unit and touch it, should the screensaver exit and I get the HomeAssistant Dashbourd through fully.
In this way, if nobody is setting off the motion sensor with the integrated camera on the tablet, the screen is off. This is the part that wasn’t working for me with the Lenovo.
I don’t use motion detection with FKB, but I think what you want should work just fine. Disable Turn Screen On on Motion in Fully and manage the screen and screensaver behavior from HA.
Hello and thanks.
I’m willing to explore that path, but I’m not sure how to get started.
The HA app is installed on the tablet. And I see entities for the tablet in the HA entities list.
But I don’t see anything for motion detection when I try to set up an “Automation” in HA.
How do I use HA to manage the screen and screensaver behaviour?
Screen and screensaver control are provided to HA by the Fully Kiosk API. In FKB turn on the API by enabling Remote Administration. Then add the Fully Kiosk Browser integration in HA so that you can control the tablet.
@SackOHammers did you ever figure this out? I’m in a similar position where I want the screen off at night time. For me, every once in a while, the screen would wake up for no reason (not triggered by motion) and affects our sleep. Let me know if you get yours to stay off till actual motion.
You can mitigate this a little by setting the FKB screen brightness to 0 at night, but even then I found my tablet emitted a glow from some kind of backlight if the screen came back on.
I ended up writing an automation to immediately turn off the screen if it triggers to on given certain specific conditions - it’s between hours defined as night, and the motion sensor is clear. Works mostly OK.
Wow, are you able to share the code? I have a similar automation setup based on a TOD sensor that turns the screen off at 10pm and back on at 8am. Even though the automation runs correctly, the screens will still wake up at random times in the middle of the night.
Sure - I edit all my automations in YAML though, so no idea how this would translate to the UI, especially given the use of jinja templates.
This is a slightly simplified version of the one I use, so not fully tested, but hopefully should get you started:
- alias: "Tablet Night Keep Screen Off"
mode: parallel ## just in case more than tablet comes on simultaneously (unlikely perhaps)
trigger:
- platform: state
entity_id:
- switch.tablet1_screen
- switch.tablet2_screen
- switch.tablet3_screen
- switch.tablet4_screen
- etc, etc
from: "off"
to: "on"
variables:
## These variables are probably overkill on the code front, but are leftovers from a more complex version of the automation
tablet: >
{%- set tablet = trigger.entity_id | regex_replace("(?:|switch.|_screen)", "") %}
{{ tablet }}
tablet_screen_switch: >
{%- set tablet_screen_switch = trigger.entity_id %}
{{ tablet_screen_switch }}
condition:
- alias: "Check the tablet screens should be off"
condition: state
## I have set up a binary sensor 'Phase of Tablets' to be 'off' for night, and 'on' for daytime,
## according to the current time matching times I can set in the frontend via a 'start of day' time only input_datetime
## and an 'end of day' time only input_datetime
## I use this in lots of different places, so thought it best to put this in a separate binary sensor
entity_id: binary_sensor.phase_of_tablets
state: "off"
## The FKB integration does not provide a device motion sensor natively, but I got so fed up with the unreliability of the browser_mod ones
## that I used the relatively new MQTT feature in FKB to create a more reliable motion sensor for each tablet
- alias: "Check tablet screen not turned on by motion sensor trigger - motion sensor state would be on"
condition: template
value_template: "{{ states('binary_sensor.' ~ tablet ~ '_motion_sensor') == 'off' }}"
action:
- alias: "Turn off given Tablet Screen Switch"
service: switch.turn_off
target:
entity_id: "{{ tablet_screen_switch }}"
