Troubleshooting

Troubleshooting / FAQ

The sidebar still says "Dashboard", not "Glance"

The panel title is set in addon/config.yaml (panel_title: Glance), but HA registers the sidebar panel once and caches it. A config change won't show until the panel re-registers. Fix, in order — stop at the first that works:

1. Update the add-on to the latest version. If it still shows an old version, the new title isn't installed yet.
2. On the add-on's Info page, toggle "Show in sidebar" OFF, then ON.
3. Hard-refresh the browser (Cmd/Ctrl+Shift+R) — the sidebar is browser-cached.
4. Settings → System → Restart → Restart Home Assistant (Core restart).

"Add to Home Assistant" opened the store but didn't add anything

The button only opens the Add repository dialog (you still click Add), and on some HA/browser versions it just lands on the Add-on Store without the dialog. Use the manual steps in Installation.

Add-on install takes a long time

First install builds from source on your device (clones the repo + npm run build). Several minutes is normal; it needs internet access.

Can I run this without the add-on / Supervisor?

Yes — run it locally with npm run dev (see Installation Option 2). Add-ons require a Supervisor (HA OS or Supervised); HA Container/Core have no add-on store.

Where is my layout stored? Will I lose it on update?

• Local/dev: layouts.json at the project root.
• Add-on: /data/layouts.json (persistent — survives restarts and updates).

Back it up anytime via Settings → Dashboard data → Export layout. See Layout: Backup & Restore.

Is my token safe?

The token is stored only in the browser's localStorage. It is never written to disk by the add-on or baked into the image — unless you opt in to Remember connection on this server, which stores it on the add-on's /data so other devices can auto-connect (see Configuration).

My dashboard is empty after importing a backup

This usually happens when you enter the token and import the layout in the same Settings session — the dashboard reloads into the imported layout without the connection applied. Fix it by setting them up one at a time:

1. Open Settings → Home Assistant, enter your URL + Long-Lived Access Token, then Save & reload (confirm the dashboard is connected).
2. Open Settings → Dashboard data → Import layout and pick your file.

If it's already empty, just re-open Settings, re-enter the Long-Lived Access Token, and Save & reload — the dashboard then populates with your backup.

My new tablet/kiosk shows empty tiles (token didn't carry over)

The layout is shared across devices, but the token is stored per-browser by default, so a new device opens the shared layout with no connection. Two options:

• Recommended: on a device that's already connected, open Settings → Home Assistant, turn on Remember connection on this server, and Save. New devices then auto-connect on first open — no token to type on each one.
• Or just enter the Long-Lived Access Token on the new device in Settings → Home Assistant and Save & reload.

Enable the toggle on a device that has a complete, working connection — both the Server URL and token filled in and Test connection passing. If the URL is left blank, other devices fall back to homeassistant.local:8123, which often isn't reachable and shows Connection failed. A device that already has a partial connection (e.g. a token but no URL) will adopt the shared one on its next reload.

See Configuration → Remember connection on this server.

What happens if I set a direct port instead of Ingress-only?

You get a stable http://<ha-ip>:<port> URL that's great for kiosks/tablets, but that port has no Home Assistant login in front of it — anyone on your network who reaches it sees the dashboard UI. Your HA data is still protected by the token (a fresh device sees an unconfigured dashboard until a token is entered). Keep the port on your LAN only — don't expose it to the internet. Both Ingress and the direct port can run at once. See Installation → Ingress vs. direct port.

The dashboard can't connect to HA

The browser connects to HA directly over WebSocket. Make sure the Server URL you entered in Settings is reachable from the device viewing the dashboard, and that the long-lived token is valid. Use Test connection in Settings.

"Connection failed" — use your HA's IP, not homeassistant.local

Many devices (tablets, Fire tablets, Fully Kiosk, Chromecast) can't resolve the homeassistant.local mDNS hostname, so the default URL fails. Set the Server URL in Settings to your HA's IP address with port 8123, e.g. http://192.168.1.10:8123 (replace with your HA IP). http://homeassistant.local:8123 often will not work on those devices.

Fully Kiosk / tablet: which URL do I open?

Two different things use two different ports — don't mix them up:

Setting	Use	Example
Server URL (inside Settings)	HA's API	http://<HA-IP>:8123
Kiosk start URL (Fully Kiosk address bar)	the dashboard itself	http://<HA-IP>:3000

• Point Fully Kiosk at http://<HA-IP>:3000 (the add-on's direct port — set a host port of 3000 first, see Installation → Direct port access). http://homeassistant.local:3000 usually fails on tablets; use the IP.
• There is no port 8124 — the dashboard runs on 3000, HA's API on 8123.
• If you'd rather not open a direct port, open the dashboard through HA's sidebar (Ingress) instead — but then you must be logged into HA in that browser.