Add kiosk.js
file with the content below to your www
folder in config.
Like any other custom script, use ui-lovelace.yaml
resources section to reference the kiosk.js
file.
Make sure you add kiosk
somewhere in your URL. You can use it in the id of your view or in the query string.
Examples:
/lovelace/0?kiosk
views:
- title: Kiosk
icon: mdi:heart
id: kiosk_alarm
If this is your first file in www
make sure you restart Home Assistant.
Thanks for writing this. I have found what I think is a very interesting use case for this, which is as an alternate solution to having two HA instances supporting two different homes (something I'm trying to set up now). I've tried Remote Homeassistant, but haven't been able to get that to work. So I had the bright idea of adding a Lovelace dashboard on one instance (e.g. main home), that brought up a Lovelace dashboard in the other instance (e.g. vacation home). I did this by creating a Lovelace dashboard, and adding a web page in panel view, pointing to the URL of the intended Lovelace dashboard in the other instance.
This works; but at the expense of having the Lovelace tabs (left-hand column) appear twice, and the header row appear twice. Kiosk.js resolves both. (A key here is that it needs to be installed on the HA instance being called, not the HA instance doing the calling.)
However, there's a limitation, which is that, by cutting off the header, one can't access additional views that are part of the same Lovelace dashboard. I'd prefer to remove only the Lovelace tabs (left column) while keeping the header row (which isn't that bothersome, and allows access to additional views on the dashboard). I've tried the "show_tabs" parameter (not being sure whether this was intended to show the Lovelace tabs on the left, or the header and views on the top) - for what it's worth, it doesn't seem to have any effect.
Is there a way to modify the script so that it would show the header and views, while suppressing the column of tabs on the left? That would allow this to work as a simple solution to having a single view that could show information from multiple HA instances. (Not to mention making the kiosk approach more versatile for other uses, e.g. by allowing for the possibility of a kiosk view that could present more than one view, without exposing the whole Homeassistant configuration.)