#486 · multi-device dashboardconsumes the #485 registry · v1 device_id/sensor_ididentity per ADR-0020 · never a MACsecond device is real · s3 bring-up 2026-07-03
The host dashboard once the second Sprout exists: cards group under the device that grew them. Each device is its own fence — its own connection state, time source, calibration status. One device's bad day never colors another's numbers.
Try it{{ simHint }}
{{ fleetDevices }}{{ fleetChannels }}{{ fleetReporting }}{{ fleetUnwired }}{{ fleetOffline }}order: first-seen in the registry — never re-sorted by state
last-known snapshot · {{ d.lastHeard }} — viewer-stamped; the device tends on its own (ADR-0001)
↳One device, no chrome: with a single registered Sprout the group header collapses to this slim ribbon and the cards flow exactly as today's dashboard — grouping appears when the second device does, not before. Nothing to relearn, nothing redundant.
The grouping ruleswhat Data builds against
{{ r.tag }}{{ r.text }}
#486 · the device is the fence — states, time, and calibration never leak across ittend well.