The dashboard has been running by our entrance door for more than 18 months. The full Family Dashboard case study covers the weather, calendar, transport, and school features. This is the less polished part: what happened after it stopped being a project and became a household appliance.
The useful idea was not the interface. It was the location. The screen is visible when someone is putting on shoes, checking whether to take an umbrella, or deciding whether there is time to catch the next tram. Most days nobody thinks about it. They glance at it and leave.
The setup is modest: a used Kindle Fire, SvelteKit, Node.js, a Raspberry Pi, a few external APIs, and a 3D-printed wall mount. The cheap hardware exposed what mattered. Animations had to stay light, partial data had to be better than a blank screen, and stale information had to be visible.
External APIs caused more maintenance work than the interface. If I built it again, I would add health checks and small adapters for each service from the start, rather than after something failed at 7 AM.
It still runs every day. I would not call it a platform or a smart-home system. It is a screen by the door that answers a few recurring questions at the right time.