Meta Quest Pro not seeing or connecting to Ubiquiti Unifi 6Ghz networks

[kha1aan]

Looks like there are posts tacking on to some of the PTC notices, etc. But I figured starting a new conversation that is focused on this issue instead of trying to get help interjected into another thread is the best approach. All of us leveraging the Ubiquiti "Unifi" network ecosystem (specifically the Unifi 6 Enterprise access point) and the Meta Quest Pro are having issues with connecting to 6Ghz wifi from our MQP. I happen to also own an HTC Vive XR Elite, which is connecting, as expected, to my 6Ghz Network. I am attaching screenshots from the respective Wifi browsers, WLANScanner for Android, etc. in effort to get the ball rolling on getting this fixed as it likely is something that will need to collectively be fixed across Meta and Ubiquiti Networks.

Due to software restrictions I cannot get screenshots or video from the wifi networks view on the Quest Pro, so I am not able to show what appears there, however it does not display any of the the 6Ghz exclusive networks. When networks are on both 5 and 6Ghz it will only ever connect to 5Ghz rather than 6Ghz.

The Meta Quest Pro does see a beacon network that Ubiquiti makes available for older versions of Android (10 and 11) to help provide hints about the 6Ghz networks since network broadcasting works differently with 6Ghz than it does on 2.4Ghz or 5Ghz.

HTC Vive XR Elite Android Version

C:\Program Files\Meta Quest Developer Hub\resources\bin>adb shell getprop ro.build.version.release
10

[MyloRuiter]

More users reporting - It does see the 6E control SSID from Ubiquity . So i guess its SSID filtering 6E on the quest thats buggy - 

TP Link Deco also had a Wifi 6E control SSID that shows up in the Wifi list and no other normal 6E ssids

Quest pro and 6ghz | Ubiquiti Community

[kha1aan]

My support case with Meta's engineering team came to a close today, where the feedback from the engineering team was that apparently the "enterprise-grade" VR "pro" headset we purchased for either 1100 or 1599 depending on when you bought it shouldn't be expected to work in enterprise settings. It should only be expected to work with lower-grade consumer products.

[jonstatt]

That is absolutely pathetic. @MetaQuestSupport Please get that support case reopened. WiFi is a standard regardless of home or enterprise class and the other routers mentioned here with the same issue are home routers anyway. I am in disbelief at the response received!!

[MyloRuiter]

Well the same issues are with the home grade TP Link Deco set with 6E

As always META support is bull**bleep** again . Pathetic how much people work there that have no clue about what they are doing and what they are releasing to the users . @MetaQuestSupport 

[MyloRuiter]

@MetaQuestSupport ---- Any comments or updates ..... Or as always , offline when issues are serieus and affect more brands and people than you are telling 🙂

[kibleznbitz]

I'm also having this issue and very disappointed after buying a $300 Access Point and $1000 headset that the Quest Pro Cannot see my 6E SSID. 

[MyloRuiter]

@MetaQuestSupport ---- Still nothing ? V56 is even more unstable in everything 🤣

[grittonb]

So, is the problem with the U6 Enterprise access point or the Meta Quest Pro headset.  It is crazy if this is not an open case.  Very disappointed

[kha1aan]

Given several other access points see the exact same behavior this looks like a Quest Pro behavior. I bought another 6Ghz access point that uses the only router chipset I seem to actually being able to work consistently, whcih is the AXE7800. But several of the routers/APs/mesh devices you can buy off the shelf at best buy are reported not working. Anyway, I opened a case, and it got closed with the following response from Meta store support:

---

Regrettably, we can't guarantee that the Quest Pro will be able to connect to an enterprise router as there are too many aspects and factors that go into that specific type of connection. This should be fixed with future versions for most commercial routers but we can't guarantee that our devices will connect with them. If your Quest Pro is able to connect to a consumer router we recommend switching to different hardware. I understand this wasn't he news you were hoping for since you mentioned before that this was intended to be a dedicated connection for your device.

---

[grittonb]

Sure glad I spent $300 on a wifi 6e access point specifically to put in the room where my MetaQuest Pro sits based on Meta saying it supports wifi 6e.... terrible support