GlassHomeDash
Skip to content

Updated

View MarkdownOpen in ChatGPTOpen in Claude

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, which holds the one token for your home and talks to Home Assistant on your behalf. Your phone, tablet, or laptop never talks to Home Assistant directly and never holds that token.
New in Dash 1.3

Several screens at once

If your phone, a wall tablet, and someone else’s laptop all have GlassHome open, each one gets its own live connection through the GlassHome server. They don’t queue behind a single link: one screen changing a light doesn’t make another screen’s updates wait.

Each connection only carries what that person is allowed to see. If someone’s access covers a few rooms, their screen never receives updates for the rest of the house.

The server also keeps one shared background connection per home, tracking which rooms and devices exist. So six open screens means six connections to Home Assistant, plus that shared one. A dozen always-on kiosks ask more of Home Assistant than a single phone, worth knowing if HA feels sluggish.

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, 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.