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.
Now that's an idea I haven't thought of before. I've tried it, and it works (depending on one's preferences) as follows:
Hide the sidebar in the secondary HA instance, show the sidebar in the primary HA instance. I can add the web URL to a Lovelace dashboard in the secondary HA instance, as a panel-width web page in a Lovelace dashboard in the primary HA instance. It displays perfectly in the primary HA instance (though with the second header... not a problem if it's needed to get access to multiple view tabs). (An odd side effect is that I get four narrower columns despite the sidebar being present in the primary instance. I'm not sure if there's a way around this.)
Hide the sidebar in both instances (needed if I want to be able to make this work in both directions). As I get more used to the HA user interface, I'll probably be comfortable with this.
I am thinking that this is a pretty elegant way to manage multiple instances of HA (e.g. two homes), and manage both from a single user interface... much easier than MQTT, Remote Homeassistant, and other solutions. It has the added benefit that I can build and maintain a single Lovelace dashboard that can be used (without needing to be duplicated) on both instances.
Thank you again for your help with this.