Insights · guide
Use one VR headset as a canary before fleet updates
Drafted with Insight · edited by The WE ARE VR team
development

A labelled canary headset lets you test updates without risking every device.
What's the problem?
Updating a fleet feels efficient when every headset changes at once. It is also an efficient way to create eight identical problems.
A firmware update may reset permissions. A new app build may break controller input. Device management software may change kiosk settings. Even a small operating system update can affect casting, boundaries, audio or login sessions.
These failures become expensive at a Jozi event. Venue access may start late. Wi-Fi may behave differently from your office network. The client walkthrough could begin before your technical lead arrives.
Commissioners face a related problem. A supplier may report that an update “works” without defining what was tested. The application might open, while the facilitator reset process remains broken.
A successful launch is not enough.
What's the solution?
Choose one headset as your canary. A canary is the first device exposed to a change, so problems appear before the whole fleet is affected.
Put a visible label on it, such as CANARY 01. Select a normal production headset, rather than the cleanest spare in the cupboard. It should use the same accounts, accessories, network rules and application settings as the fleet.
Before updating it, write down the pass conditions. These are observable checks that decide whether the change is safe.
A useful XR pass list could include:
- The headset completes a cold start.
- Tracking starts in the expected play area.
- Both controllers connect and register input.
- The correct application opens without extra login steps.
- Audio plays through the intended output.
- Casting works on the facilitator screen.
- A representative five-minute experience runs without interruption.
- The facilitator can exit, reset and launch the next session.
Add checks for your actual production. Hand tracking, spatial anchors, multiplayer connections and custom peripherals each need their own line. Keep the list short enough that someone will use it [the finest checklist is useless inside an unread spreadsheet].
Then update only the canary. Test it under realistic conditions. Use the venue network if possible. Follow the facilitator’s normal start and reset process. Test the difficult scene, not just the menu.
Consider an eight-headset activation in Sandton. An operating system update installs successfully, and the application still opens. The canary test then reveals that casting permission has been reset. You can restore the permission, update the facilitator instructions and confirm the fix before touching the other seven devices.
Record the old version, new version, test date and result. If a check fails, stop the rollout. Either correct the problem or return the canary to the known working version. For a larger fleet, update the remaining devices in small batches rather than one sweep.
This habit also improves supplier approvals. “Tested on CANARY 01 against nine pass conditions” gives a commissioner useful evidence. “Seems fine” does not.
What's next?
- Label one representative headset as your canary and photograph its current version screens.
- Write five to ten pass conditions covering launch, tracking, input, audio and reset.
- Test the next update on that device, then record the result before updating anything else.
Share your canary checklist with the Jozi XR community, or send us a question.
The WE ARE VR team
