HydraIssues

Issues / #759
GRM: headset should auto-enter the experience every time (kiosk vs game mode); enable PICO auto-connect + single-app kiosk
open unclassified Project: gallo-romeins-museum Reporter: 23 Sep 2026 07:43

Description

Museum reports 2026-09-23: the experience runs, but the PICO headset intermittently will not re-associate with the experiencenet Wi-Fi after being taken off/put on; staff power-cycle the headset 3-4 times before it reconnects.

Diagnosis (fluffy, node-11da9ea3): PC side is healthy - Mobile Hotspot continuously ON all morning (5-min self-heal, no errors), PeerlessTimeoutEnabled=0, SSID experiencenet on the 5 GHz band, ClientCount 1 during a live session. So the SSID is always broadcast; the failure is client re-association, the known weak spot of the Windows Mobile Hotspot.

Contributing factors:

  1. Wi-Fi adapter (MediaTek Wi-Fi 7 MT7927) still has power management enabled (PnPCapabilities=16, WakeOnMagicPacket=1) so the radio can power down.
  2. 5 GHz Mobile Hotspot auto-selects its channel and can land on a DFS channel; DFS radar-wait makes the AP slow/unavailable to a re-scanning client.
  3. PICO likely competes with the museum staff network grm-medewerkers (seen 2026-09-07); it may auto-join the wrong SSID first.
  4. PICO Wi-Fi power-save on sleep when the headset is taken off between visitors.

Plan:

  • Headset side (museum can do now): forget all saved networks except experiencenet; keep headset on charge / lengthen sleep timeout; when it will not connect, toggle Wi-Fi off/on in the headset instead of full power cycle.
  • PC side (off-hours, brief adapter reset): disable Wi-Fi adapter power management (PnPCapabilities disable-turn-off) so the AP radio never sleeps.
  • Durable fix: replace the Windows Mobile Hotspot with a dedicated venue router/AP (GL.iNet, ties to hydraneck router inventory #533). This removes the re-association flakiness AND decouples the headset network from the PC connectivity (which contributed to the #757/#758 reboot loop via ICS/DNS).

Comments (1)

api 23 Sep 2026 09:01

DIAGNOSIS CORRECTED 2026-09-23 after museum clarified. This is NOT a Wi-Fi problem (the hotspot connection is constant). The real ask: when staff put the headset on, they want it to land in the experience (spelmodus) EVERY time, but sometimes it lands in the PICO kiosk/streaming-client screen (kioskmodus) instead.

Root cause: PICO Business Streaming auto-connect is OFF (the headset reports connect.autoConnect=false in its streaming config; also documented in the venue runbook). With auto-connect off, the headset only drops straight into the experience when a previous streaming session is still alive to resume (short sleep). After a longer sleep or once the session has ended, there is nothing to resume, so it sits on the connect/kiosk screen and needs a manual Connect tap. That is the intermittent spelmodus-vs-kioskmodus behavior.

Fix (headset / device-management side, NOT PC exec):

  1. Enable Auto-connect in the PICO Business Streaming app, target hydra-s-0000. Then the app connects by itself whenever it is open.
  2. Set the PICO kiosk to SINGLE-APP mode locked to PICO Business Streaming (via PICO Business Suite / device management), so the headset always wakes straight into that app instead of a kiosk launcher.
    Result: headset on -> Business Streaming launches -> auto-connect -> experience, every time.

Prerequisite: the PC must always be stream-ready (Business Streaming app + RomeinsMuseum running with the OpenXR runtime attached). Complement to consider: a logon scheduled task on fluffy that starts Business Streaming then the game, so the PC is always ready for auto-connect. HydraBody task stays disabled.

The earlier Wi-Fi hardening notes (adapter power management, dedicated router #533) remain valid resilience improvements but are secondary to this.