Skip to content
GlassHome
Dash pages

Updated

View MarkdownOpen in ChatGPTOpen in Claude

Connecting to Home Assistant

After installing, open http://<host>:3123. The welcome screen opens on first launch and looks for your Home Assistant by itself.

Connection methods

Continue with Home Assistant

GlassHome finds Home Assistant on your network by itself and asks for the address only when it finds nothing. Sign in there once, and it sends you back. No tokens to copy or rotate.

Look around first

A demo home with its own sun and weather, seven dashboards, a family, a kitchen tablet and a live front door camera. Nothing to set up. Start over in Settings puts it back the way it started, and a copy is cleared once it is a day old and nobody has used it for an hour. Ready for the real thing? Choose Use my Home Assistant in Settings, then connect Home Assistant from the welcome screen.

Already set up? An admin can still look around: in Settings, tap the Sample home row on your home’s card. It opens the demo in this browser, so you sign in again when you leave it. Uploading pictures, Developer Mode, connecting widgets you are building and copying diagnostics stay with your own home.

When you type the address

The welcome screen asks for the address only when it cannot find Home Assistant. The address must include the protocol and the port Home Assistant is actually listening on.

Setup Address example
HA on the same LAN, plain HTTP http://homeassistant.local:8123
HA on a fixed IP http://192.168.1.100:8123
HA behind HTTPS (reverse proxy / Nabu) https://ha.example.com

The address must match what HA serves

If HA is behind HTTPS, use https://. If HA is plain HTTP, use http://. A mismatch fails silently or returns a confusing CORS error.

What happens when you connect

  1. GlassHome finds Home Assistant, or uses the address you typed.
  2. Your browser opens Home Assistant’s sign-in page, and you approve GlassHome there.
  3. Home Assistant gives GlassHome’s server a token.
  4. The token is stored in Dash’s local SQLite (never sent to Hub).

The Home Assistant panel

In Settings, the Home Assistant panel shows your address, how many entities GlassHome can see (the things Home Assistant tracks, like lights and sensors), and a diagram of the connection. A sentence appears there only when something is wrong.

To move to a different Home Assistant, change the address and tap Save. Your dashboards and layouts are stored locally and stay; only the Home Assistant connection is replaced.

Disconnect removes the connection and stops Home Assistant sign-in until you connect again. Only admins see it.

Privacy

The GlassHome server talks to HA directly over WebSocket; your browser only ever talks to that server. Entity state, your HA URL, and the auth token never leave your network, and never reach Hub. See How GlassHome Connects.

Troubleshooting

Symptom Likely cause Fix
Welcome screen rejects the address Missing protocol or wrong port. Try the address in a browser tab first. Add http:// or https:// and confirm the port.
Stuck on the welcome screen after Continue with Home Assistant This device cannot reach Home Assistant, even though the GlassHome server can. After about ten seconds GlassHome says so and suggests Home Assistant’s IP address. Try that address, or use Code from a phone on a device that is already signed in.
Mixed-content / CORS error in console HTTPS Dash URL + plain HTTP HA URL (or vice versa). Options: serve HA over HTTPS (Nabu Casa or a reverse proxy), access Dash over plain HTTP on your local network, or use a VPN so both are on the same network.
Connection drops after restart HA was rebooted while the WebSocket was open. Refresh the page. Dash reconnects automatically.
Connected but entities not loading Token user has no entity permissions in HA. Re-authorize with a fully-permitted HA user.

Still stuck? See Troubleshooting or post in Discord and I’ll take a look.