I have a tablet that runs Fully Kiosk with Tasker that has my Sharptools dashboard. I don’t want my tablet to have an always on screen. My tablet’s front camera is busted so I cant use the motion detector of fully kiosk, but what I do have is a generic z wave motion sensor which I can run automations on my Smartthings.
I’m looking for some help to see if it’s doable to run a sharptools rule if there’s motion detected in my motion sensor, it will wake up the screen of my tablet. Is this something possible?
I built an Edge Driver for Fully Kiosk browser that you could use to interact with your tablet(s) running Fully Kiosk. You can turn the screen on/off, start and stop the screensaver, and control other features of the tablet. Even though it’s a personal project, I’ve limited access to SharpTools premium users for the time being.
In theory, you could use something like the Web Requestor Driver to make calls directly to the Fully Kiosk REST API if you aren’t a SharpTools premium member with access to the driver.
Would love to mess around with it. I’m assuming this could be use to wake tablet from screen saver and in theory display a notification if specific events occur?
Is this edge driver for Fully Kiosk still functioning? If so could I also get access to it?
I had a solution that worked years ago but it went away with groovy and i didnt look for a fix. Now that ActionTiles stopped I started looking into it bringing my stuff back to their former glory while I was setting up up SharpTools dashboards.
Absolutely and you don’t even need SharpTools. Set up a rule on your hub, such as Hubitat which is what I use. When your camera detects motion, trigger a notification on your tablet from Hubitat that then triggers Tasker. Within tasker, just use the AutoTools AutoInput plug in with a single tap on your screen to wake it up.
On Tasker, I have a profile set up that triggers anytime there is a Hubitat notification (via AutoNotification). Then it triggers this task (HUBITAT HANDLER) to make Tasker do whatever you want in response to the notification:
So for example if you wanted your camera to trigger Tasker to run a task like “Wake Up Tablet” with that single tap from AutoInput, you would have Hubitat send the notification of “Wake Up Tablet” and it would trigger the task.
You can also pass as many parameters as you want to Tasker using a single notification and that handler. As an example, I wrote a program to automate door locks and welcome messages, etc. for all of my Airbnb guests. When I put a guest into the system, Hubitat sets door codes, displays a welcome message on the tablet of the guest’s room, alerts me when the guest checks in, etc.
To make all that happen, Hubitat has to communicate with my phone so that I have the guest’s name and phone number. So when Hubitat gets all of that information from my program, Hubitat then sends a single notification to my phone that triggers 1) the task within Tasker that processes all the information (called “GuestMachine”), 2) the specific unit the guest is staying in, 3) a specific command within GuestMachine (in this case “5” which tells GuestMachine to store the guest’s name and phone number of two separate variables, and then 4) actually passes the name and the phone number.
The single notification that Hubitat would send as an example when Greg is checking into Gladstone building, room 320 would be “Gstone GuestMachine}320}5}Greg}555-555-1212”
