Guest — guest.html

Open it on a device you want to be able to look but not touch. It pairs, then forwards to the hub about a second later. The pairing URL is on the Settings page under Security, and Plugins → Dashboards → Show Guest Access Info logs it too.

What it shows

A single card, in one of three states, before the page forwards on:

• Setting up guest access… — a spinner while it pairs, which takes well under a second.
• Guest access ready — “This device can view everything but control nothing.” Then it forwards to the hub.
• Pairing failed — with the reason in brackets. Guest pairing works on the home network and Tailscale only.

How it works

It fetches guest-bootstrap from the plugin’s proxy on port 8177, with a four-second abort. On success it stores the returned guest token in localStorage and removes any full API key that was there — so a device that previously held the key is demoted rather than left holding both. The proxy refuses any non-private source address, which is what makes guest access home-network and Tailscale only by construction.

What a guest device can do

View every page. Control nothing: the tiles render, the toggles do not act. It holds no Indigo API key, so the restriction is not a matter of the interface politely hiding buttons.

Worth knowing

• Pairing is per-browser. Clearing site data un-pairs the device and it will need the URL again.
• A wall tablet is the intended case. A visitor’s phone on your Wi-Fi is the other.