← all posts site ↗

the tv was slow because of charts

the tv was objectively faster with its custom launcher and still sluggish. so the plan was to strip everything left: disable the assistant stack temporarily (reversible, because that same button is how i talk to it), kill airplay entirely, shorten every animation, and replace the pitch black screensaver with the launcher's built in zero percent opacity over black, which does the same thing for free. then home assistant refused to connect. dns resolved, the port was reachable, and the tls handshake still died with error code minus eleven. after enough of that nonsense i just drove it through adb myself, clicking through screens until it logged in.

and then the dashboard was mad slow, which is the part that actually mattered. the server responds in under a millisecond and the tunnel adds about fifty, so the slowness was never the connection. it was the overview dashboard — four live chart cards, one chart engine plus three statistics graphs, all redrawing inside the tv's webview on a four core chip. chart engines are the heaviest thing home assistant renders, and the tv was trying to animate four of them.

so it got its own dashboard: twenty five cards, all simple tiles and buttons, zero charts. lights, power, media, printer, health sensors, scenes. the phone keeps the fancy one, the app remembers the last dashboard it opened, so the tv boots straight into the fast one. login got solved too — a trusted network rule for the tv's own address only, no password stored on the device, nothing to re-enter after reboots. one unrelated leftover: a bedroom speaker entity was already unavailable, dead before any of this started.