-
Notifications
You must be signed in to change notification settings - Fork 2
Installation
There are two ways to run Glance: as a Home Assistant add-on (recommended for most people) or locally for development.
Runs on the HA server itself and shows up as the Glance panel in the sidebar. Requires a Supervisor (HA OS or Supervised). HA Container/Core have no add-on store and cannot use this.
Open the Add repository dialog pre-filled in your own HA:
https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2Fjvenuto80%2FDynamic-HA-Dashboard
Then click Add.
The button only adds the repository — it does not install the add-on, and on some HA/browser versions it just opens the Add-on Store without the dialog. If that happens, use the manual steps below.
- Settings → Add-ons → Add-on Store.
- Top-right ⋮ menu → Repositories.
- Paste and Add, then Close:
https://github.com/jvenuto80/Dynamic-HA-Dashboard - Refresh the store. A new Glance — HA Dashboard Add-ons section appears.
- Open Glance — HA Dashboard → Install → Start → Open Web UI (it also appears as Glance in the sidebar).
First install builds from source on your device (clones the repo +
npm run build), so it can take several minutes and needs internet access.
Next: Configuration for first-time token setup.
By default the add-on is served through Ingress only (no exposed port — it inherits HA's authentication). To point a kiosk browser straight at the dashboard, give it a direct port:
- Open the add-on → Network tab.
- Map host port
3000to the container's3000/tcp(or any free host port you prefer). - Save and restart the add-on.
Then browse to http://<home-assistant-ip>:3000. The dashboard listens on
container port 3000.
npm install
npm run dev # Vite dev server on http://localhost:3000
npm run build # tsc -b + vite build → dist/
npm run preview # serve the production buildStrict TypeScript is enforced (noUnusedLocals); the build must be 0 errors.
Set connection values via .env (copy .env.example → .env) or in the in-app
Settings modal. See Configuration.
When a new version is published, the add-on page shows an Update button. After updating, restart the add-on so the sidebar panel re-registers (see Troubleshooting if the panel name looks stale).