Browsers only hand over a microphone or the motion sensors to a page served over a secure (https) connection. On a room Wi-Fi with no internet, ResusSim provides that itself: the host issues its own certificate, and each device agrees to trust it once. Five minutes per device, once ever.
No, for most of the room. The monitor, ventilator, EMR, pumps, POCUS and the consult phone's text messaging all work over the ordinary connection. You need Secure mode only for three things:
If none of those are in today's session, skip this page entirely.
The certificate covers the host's current network addresses. If the host later joins a different Wi-Fi, secure mode re-issues it automatically — devices keep their trust; just re-scan the QR.
Two parts: install the profile, then trust it. The second part is the one everyone misses — without it, everything looks installed but sensors stay silently blocked.
http://<host-address>:4000/api/tls/ca.mobileconfig


https://<host-address>:4443 in Safari. No certificate warning = done, forever. (The pairing QR always uses the standard address — the app offers the secure one wherever a feature needs it.)The host Mac itself needs nothing — this is for an additional Mac joining the room.
http://<host-address>:4000/api/tls/ca.crthttps://<host-address>:4443 — no warning = done.http://<host-address>:4000/api/tls/ca.crthttps://<host-address>:4443 in Edge or Chrome — no warning = done.Firefox keeps its own certificate store: Settings → Privacy & Security → Certificates → View Certificates → Authorities → Import → tick "Trust this CA to identify websites".
http://<host-address>:4000/api/tls/ca.crtchrome://certificates → Authorities → Import → choose the file → tick Trust this certificate for identifying websites → OK.https://<host-address>:4443 — done.A Chromebook running the EMR or a wall display doesn't need this at all — plain http://<host-address>:4000 works fine for screens.

certmgr.msc → Trusted Root → delete. It only ever trusted your own room's host.