Claude-Built HTML Dashboard Replaces YAML Dashboards in a Weekend

Oct 17, 2026 Last reply: 4 hours ago 2 Replies
Jump to replies (2)

The problem here is one many of us know: the native companion app dashboard feels sluggish, and heavy YAML dashboards are painful to maintain. The maker's answer was to have Claude migrate the whole setup into a hardcoded HTML dashboard, and it was finished in a single weekend. In the maker's own testing, the browser version loaded three seconds faster than the native app, and loading now feels instantaneous.



How it is put together: dash.html and config.js sit in the Home Assistant www folder and get served at /local/dash.html. The page runs in a browser on tablet, phone or PC and talks to Home Assistant directly over websocket. Claude writes and edits the code and tests it against a fake Home Assistant in a sandbox, without any direct connection to the real instance. The maker subscribed to Claude Pro for this and kept it that way on purpose, citing security concerns.



The details that stand out to me: animations and colors react to metrics like temperature and on/off/playing state, camera streams can drop between fluent and clear modes to save resources while still showing 2k when needed, and there is two-way audio plus synced lyrics when available. The pages cover an overview, media, climate, rooms, cameras, energy, irrigation, calendar, vehicle diagnostics and theme customization, with lighting sliders, presence and movie mode toggles, an alarm keypad with siren toggles, and irrigation flow up to 0.4 m³/h.



The open part: everything is hardcoded to the maker's entities, and energy tracking relies on just three smart plugs, with more planned for better measurements. The maker also offered to strip private data and share the file.


This looks really polished. I am curious about the access side: the maker mentioned a lot of refilling long-lived API tokens while copying new HTML files around. Does that token juggling still happen every time the dashboard is opened, or is it a one-time setup per device now?

From what the maker has said, the token gets saved to the browser, mobile or tablet and is cleared on logout, so it should not need refilling on every open. They also got the Home Assistant default login page to appear before the dashboard loads, which fixed the earlier weakpoint where anyone with the link could get in. The whole thing sits behind Nabu Casa for HTTPS too.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required