The rule can be written in your automation engine of choice. You could create it in Hubitat (eg. Rule Machine) or SharpTools Rule Engine.
Fair warning that this is a medium difficulty, slightly technical project. This is not something we officially support, but the community has used these neat tricks to accomplish similar goals.
Device Handler Installation
Sounds like you got the concept with the device driver. It gets installed in Hubitat and then you create a virtual device using that new device type and then configure the newly created device with the details of your Fully Kiosk Browser (FKB) instance.
You’ll likely want a static IP for the device running Fully Kiosk Browser. Otherwise you’ll have to periodically update the virtual device’s configuration in Hubitat.
The idea would be to run
loadUrl() command for the Fully Kiosk Browser Controller virtual device you create. In SharpTools, this would be an Action > Device command like the following – where the URL is the actual URL of the dashboard you want to show:
Once you get comfortable with the basic approach working with a normal URL, you might consider updating it to use the Fast Navigation approach covered in another community post.
Triggering the Command
How you trigger it would depend on your goal. Based on the original use-case where you want to use Alexa Voice Commands, one approach would be create Virtual Switches for the various dashboards you want to open.
Depending on the device names you choose, you would end up using these like:
"Alexa, turn on the 'Dashboard Homescreen'"
"Alexa, turn the 'Media Dashboard' on"
So in Hubitat, you would do this from Devices → Add Device → Virtual, then select ‘Virtual Switch’ from the type and give it a name. Then authorize these new virtual devices to Alexa.
Then your rule would use the Virtual Switch turning ‘on’ as the Trigger and run the
loadUrl() command as noted above. In SharpTools Rule Engine, this would would look like the following:
Note that after creating the virtual switch in Hubitat, you can update its preferences in the device’s details screen to automatically turn off. That’s particularly helpful for an automation like this where you want to trigger things based on the switch turning to ‘on’, so you need it reset to ‘off’ each time.