A connection-backed presence API removes the heartbeat table's expiry work, but it doesn't make a classroom device trustworthy. TL;DR: use presence for which authorized connections are online; keep a heartbeat table when you need to own the expiry policy, and label both as eventually correct. For an edtech dashboard, the deciding question is what a client's token lets it claim, because a connected browser is evidence of a connection, not proof that the tablet belongs in this classroom or that its learning application is healthy.
What page fired when the classroom stayed green?
Consider a production-shaped tabletop exercise, not a reported outage: a teacher watches a device dashboard during a collaborative editing session, a tablet connection disappears, and the dashboard continues to show the device as online. In that exercise, I would start the postmortem with the page that fired and the evidence behind it. Did an alert report stale observations, or did someone infer device health from a green badge?…