Quest 2, 3 & Pro - Connectivity Issues

My Quest 3 started randomly disconnecting from the WiFi with version 64 and I'm now on version 65, it makes playing multiplayer games frustrating. 

Up to now, it seems I’ve found finally a configuration quite stable …..5Ghz and 6Ghz network activated on router, fixed local IP for PC, router and HMD, connection to router through Mac adress and not DHCP ….

I created a guest account on my router and connected to it, it has fixed the problem for me. No random WiFi disconnects since.

Hey everyone! First and foremost, I want to apologize for the lack of updates on my end. Truthfully, during the hiatus of posted updates, I was back-and-fourth with our internal engineering team probing for more information to share with the community. All of the updates I had received up until this point were too limited to share with you all.

I just received word from our team that they're making good progress on the resolution for the Wi-Fi related issues everyone has been experiencing on this thread in the past month and a half since it was raised to our engineering team. While I don't have a specific timeline on when the resolution will rollout, it seems that the expectation is that we hope to have a resolution in one of the upcoming updates.

I'll be sure to keep you all posted once I find out new information to share with everyone. Thank you for your extended patience as the team works hard towards the resolution!

SimpleCJ I totally agree with your post - there's so many possible hardware combinations variations that issues do obviously arise. I too would roll back to v63 if it were possible and remain on v63 until this issue is fixed. My 5ghz is also a reliable connection but as you say just feels ever so slightly less responsive than the 6ghz network. I consider myself lucky that i am able to use the 5ghz band as i know other users have issues on that too, and their frustration is completely understandable. 

TheLegend27 thank you for the, as you admit, belated update. Maybe don't leave such a long gap of silence before the next update?

SimpleCJ I definitely get wanting to take full advantage of your 6Ghz band. I don't have a huge amount of info regarding what the resolution is going to include, but I'm hoping it addresses a lot of the 6Ghz discovery/connectivity issues I'm seeing a lot of in this thread.

The option to rollback firmware is something I've seen a lot of users ask for specifically for bugs that get missed on live versions. I'm sure it's possible (as it's something that's done regularly when opting out of the PTC.), but it's possible that it may introduce another handful of issues and complications. My best recommendation would be to open up an Idea for that suggestion specifically, if it doesn't exist already.

petecod I'll definitely do my best to keep you all updated as I get more information. Something I want to avoid is a lack of communication on my end, but also providing continuous empty updates of "the team is still working on it" as they don't provide much substance other than confirmation that we're still working towards the resolution. If I don't have any immediate updates to share, I'll be sure to at least pop in weekly to let you all know that I'm still working on receiving updates from the team, so I appreciate the feedback!

SatoriAkiyama Without proper input from engineering, I won't have an exact answer on why something as specific as this is changing the way the Quest interacts with your network, but I'll do my best to provide my best educated guess. When connecting to a guest network, devices are essentially bypassing many of the advanced settings and optimizations applied to the primary networks. Guest networks out of the gate typically have very basic configurations with minimal extra features enabled.

It's possible that one of the main network settings or features intended to enhance performance (e.g. beamforming, MU-MIMO, WMM QoS prioritization, etc.) could be contributing to the instability/discoverability experienced on the primary network. By connecting to the guest network, the device would likely avoid those advanced configurations. I'll be sure to relay to the team that it looks like guest networks are fixing the issue for some users.

Thank you all for sharing your experiences and feedback! Each data point helps our teams better understand the scope of the issues and hopefully get to the resolution sooner. Of course, I'll continue raising comments and suggestions to the appropriate teams where I can!

Got a new Quest 3 with V66. Broken Wifi with 5Ghz. 

idk what they did with this recent update but my wifi 6 is working flawlessly now on my freebox from google fiber. Wifi 6. 

i’ve been experiencing drops at 5ghz so set up a 6ghz network, using firmware v65 and a u7-pro. at first it connected okay… then trying to use it for anything caused drop out loops until eventually the device stopped connecting to wifi completely, different networks, whatever the band, across restarts and power cycles. factory reset and we’re back to an unreliable 5ghz connection but, definitely not a great experience so far. 

Guys, I think I found the solution. I remember that around the v5* update, the Metaquest 2 was having connection issues with Chromecast, frequently dropping out. The solution was to set my router's Channel Width to 20MHz. Today, June 14, 2024, I updated to version 65 and the Wi-Fi simply wouldn't connect; it was stuck on the IP configuration. I tried everything (thanks to the forum folks who were trying to find a solution). I noticed that when connecting to another router, the Wi-Fi worked normally. That's when I remembered to change the Channel Width to 20/40/80/160MHz on my Tplink AX5400 router, and miraculously, everything started working again. I hope this helps someone.