Skip to main content
New Participant
October 23, 2026
Question

Native Smart Home Automation / IoT Triggers via Headset State (Passthrough, HMD Proximity)

Proposal:
Add native smart home / IoT integration capabilities directly to Meta Quest headsets to trigger smart device actions based on the physical state of the headset (e.g., wearing/removing the HMD or toggling Passthrough mode).

How it works & Use Case:
Currently, some users are achieving this by stringing together third-party desktop utilities like OyasumiVR on GitHub or Steam VR, paired with a local server like Home Assistant over MQTT. For example, a user can configure an automation where putting on the VR headset automatically dims or turns off the physical smart lights in their room to prevent light leakage or save electricity. When they double-tap for Passthrough mode or take the headset off, the lights seamlessly turn back on so they can see their real-world surroundings.

Why Meta should implement this natively:

  • Seamless Immersion: Putting on the headset could instantly prepare your physical room for VR (dimming lights, activating a fan, locking smart doors).
  • Real-world Safety: Activating Passthrough is meant to help users see their actual surroundings. If your room is pitch black because you dimmed the lights manually before putting the headset on, Passthrough is useless. Tying a wake-up command for local smart lights to the Passthrough toggle completely solves this safety hazard.
  • Privacy & Efficiency: By enabling these triggers locally over the home network (Wi-Fi), it guarantees a lag-free experience without relying on external cloud servers.

Having a dedicated "Smart Home / IoT" menu in the Meta Quest experimental or network settings would allow users to connect to local smart home hubs or directly to popular local smart devices to configure these simple state triggers natively.

3 replies

Maccyb123
Honored Contributor
October 23, 2026
steve40
Honored Contributor
October 24, 2026

The dev forum is not for random ‘proposals’, ​@Maccyb123 

steve40
Honored Contributor
October 24, 2026

Spam reported.

Feedback and ideas should be formally submitted via the Developer Feedback Centre.

Alternatively, you could consider joining the AR/VR User Research Panel to provide feedback on the future of VR.