# XR controllers in Quest headset not connecting unless put in sleep mode during XR

**URL:** <https://discourse.threejs.org/t/xr-controllers-in-quest-headset-not-connecting-unless-put-in-sleep-mode-during-xr/82373>\
**Category:** Questions\
**Tags:** webxr\
**Created:** [May 10, 2025, 12:37pm UTC](https://discourse.threejs.org/t/xr-controllers-in-quest-headset-not-connecting-unless-put-in-sleep-mode-during-xr/82373 "2025-05-10T12:37:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![danrossi](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/danrossi/32/1017_2.png) [@danrossi](https://discourse.threejs.org/u/danrossi)\
**Post date:** [May 10, 2025, 12:37pm UTC](https://discourse.threejs.org/t/xr-controllers-in-quest-headset-not-connecting-unless-put-in-sleep-mode-during-xr/82373/1 "2025-05-10T12:37:18Z")

</div>

Is anyone experiencing the same thing. I am unable to get a controller connected unless I put the headset and controller into sleep mode during an XR session. When relaunching to XR there is no controller again.

Can be tested with these

> **[three.js xr - cubes](https://threejs.org/examples/webgpu_xr_cubes.html)**

> **[three.js xr - ball shooter](https://threejs.org/examples/webxr_xr_ballshooter.html)**

more info

> **[Controller is webXR are not connecting randomly. No inputsourceschange event.](https://communityforums.atmeta.com/t5/Quest-Development/Controller-is-webXR-are-not-connecting-randomly-No/m-p/1319730/thread-id/11235)**
>
> I have discovered the controllers are taking ages to connect or don't connect at all because of no inputsourcechange event. I get it sometimes but not all the time. If I put the headset down and controller and enable where the controller vibrates I...

---

<div class="post-metadata">

**Author:** ![Patrick\_Morrison](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/patrick_morrison/32/60485_2.png) [@Patrick\_Morrison](https://discourse.threejs.org/u/Patrick_Morrison)\
**Post date:** [June 2, 2025, 5:39pm UTC](https://discourse.threejs.org/t/xr-controllers-in-quest-headset-not-connecting-unless-put-in-sleep-mode-during-xr/82373/2 "2025-06-02T17:39:28Z")

</div>

I’m having a similar problem with a custom threejs app. Controller won’t initialise in a VR session until I hit the oculus button:

> <https://github.com/patrick-morrison/shipwrecks/blob/8f78a1b118e7a7f091196235323ce5f50b81d58e/index.html>

---

<div class="post-metadata">

**Author:** ![danrossi](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/danrossi/32/1017_2.png) [@danrossi](https://discourse.threejs.org/u/danrossi)\
**Post date:** [June 3, 2025, 5:53am UTC](https://discourse.threejs.org/t/xr-controllers-in-quest-headset-not-connecting-unless-put-in-sleep-mode-during-xr/82373/3 "2025-06-03T05:53:02Z")

</div>

Its a confirmed bug. And if you click the menu button 5 times it brings up a bug report menu.

I think its the PTC OS v77 which the issue. They also broke h265 playback and im getting no answers about it. 76 plays back h265. I cant get answers how to roll back to v76.

the work around is you click the menu button to exit back to the browser. Then click “resume” at the top of the browser.

To avoid this complication doing upgrades for controllers. I test in RIFT and the emulator first. Much quicker.