---
title: "How GlassHome Connects"
description: "The three connections behind your dashboard, and which one to check when something doesn't load."
canonical: https://glasshome.app/docs/dash/how-glasshome-connects
section: "Getting started"
updated: 2026-08-10
---
# How GlassHome Connects

Under the hood there are three separate connections. Most problems come down to exactly one of them.

Three things follow from this picture:

- **Your device only talks to the GlassHome server.** If the dashboard won't load at all, that link is the problem. If it loads but nothing updates, the GlassHome-to-HA link is the problem.
- **Sign-in is the one exception.** Your browser visits Home Assistant's own login page once, approves the connection, and comes back. Same pattern as "Sign in with Google", with your HA playing that role. After that, HA hands GlassHome a long-lived token; your device never holds HA credentials.
- **Everything live is relayed.** State updates, commands, camera and media content all flow through the GlassHome server over its single WebSocket to HA.

## Which address to give GlassHome

- **Use the local address** (usually `http://192.168.x.x:8123`), not your remote URL (DuckDNS, Nabu Casa, your domain). A remote URL sends every tap across the internet and back, and dies with your internet connection. Some routers can't even loop back to it from inside the house. Your remote URL's job is [Remote Access](/docs/dash/remote-access), not this field.
- **Prefer the IP over `.local` names** if things are flaky. `homeassistant.local` relies on mDNS discovery, which silently fails on some devices and networks; an IP always resolves.

## Signing in when this device can't reach Home Assistant

1. **At home**: use the Home Assistant sign-in. The green check means the GlassHome server can reach HA; the sign-in itself is where your device has to reach it, and if HA's login page doesn't open within a few seconds you're brought back with a note to try the IP address instead.
2. **Away, or on a kiosk that can't reach HA, with another device already signed in**: use **Quick Connect**. The new device shows a short code; approve it from any signed-in device.
3. **Away and nothing signed in yet**: the very first setup must happen at home. HA's login page has to load on the device doing the first sign-in; that's an HA requirement.

## Troubleshooting: which connection is failing

| What you're seeing | Problem link | What to check |
|---|---|---|
| Dashboard won't load at all | Device → GlassHome | Does the GlassHome address load in a plain browser tab? Try the IP instead of `.local`. |
| Loads, but entities never update | GlassHome → HA | Is HA itself reachable and running? Recent restart or network change? |
| Stuck on HA's login page | Device → HA (sign-in hop) | Can this device reach HA directly? Otherwise use Quick Connect. |
| Camera/media images fail, rest works | GlassHome → HA (media relay) | Does the entity work inside HA itself? |
| Works at home, fails away | Device → GlassHome, over the internet | See [Remote Access](/docs/dash/remote-access). |

## Related docs

- [Connecting to Home Assistant](/docs/dash/connecting): the sign-in step, URL formats, reconnecting
- [Remote Access](/docs/dash/remote-access): reaching GlassHome from outside your home
- [Concepts](/docs/dash/concepts): how GlassHome, Home Assistant, and Hub relate