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

[MetaQuestSupport]

Hi there, @kha1aan. Thank you for providing that information as well as your screenshots. Kindly note that as of v53 the Meta Quest Pro should be able to connect to 6ghz. Do you happen do know what version your device is on? 

Here is a tool that can be helpful for your connection issue. 

Network Band
Channel Width
Ethernet Connection
Round-Trip Time Latency (RTT)
Received signal strength indication (RSSI)
Network Connection
View more information about these options and steps to take for each one below in "Benchmarking Information Details"

Reviewing The Air Link Benchmarking Results
You can review the results of the benchmarking tool within the headset, this is useful for further troubleshooting of the network and potential missing requirements and slow connections when using Air Link.

To view the results:
Open the Quest 2 settings menu
Open "System Settings", likely "System"
Click on "Quest Link"
Results are listed in this menu.

Benchmarking Information Details
Network band (2.4/5GHz)

Context: The 5 GHz band supports 80 MHz channels which are up to 4x faster than the 20 MHz channels often used in the 2.4 GHz band. The 5 GHz band often has less interference too.

Solution: Often the router generates two networks, one at 2.4G and one at 5G. Often they are called MyNetworkName and MyNetworkName_5G. Make sure to connect to the 5G network. Other routers only create a single network and the router decides which band and channel to use. Check if your router can be configured to use a specific channel. If so, select a 80MHz channel in the 5 GHz band.

Channel width (e.g., 80MHz)

Context: The wider the channel, the faster the speed of the data over the wireless channel. A 80 MHz channel transfers data roughly 2x faster than a 40 MHz channel.

Solution: 80MHz channels are not supported by the 2.4 GHz band. Start by configuring your router to use the 5 GHz band. Next, if your router allows it, lock the channel width to be 80 MHz.

Ethernet Connection

Context: When both the PC and the Quest headset are connected to the router wirelessly, the Quest Air Link data must travel over the same channel twice, effectively interfering with itself. That is why we recommend connecting the PC to the router with an Ethernet cable.

Solution: Connect your PC to the Router using a supported Ethernet cable. This is one of the best things that you can do to improve your Air Link capability.

Network Latency

Context: We want to limit the number of devices the VR data has to travel through between the PC and Quest headset. Ideally we want only one device between PC and Quest headset, the router. Network Latency, also known as Round-Trip Time (RTT) helps us measure the minimum latency over the network. High RTT latency may indicate a high number of hops between PC and Quest headset.

Solution: A high RTT value might be due to the use of a mesh router. Consider using a regular Router instead, or move to the room where the main mesh node is located.

Wi-Fi Signal Strength

Context: Wi-Fi signal strength is also known as RSSI. Low signal strength leads to lower Wi-Fi speed, which affects the user experience.

Solution: Move closer to the Router. Ideally you are located in the same room as the Router, and have a clear line of sight between the Quest headset and the Router.

Can you Please select our name to get to our profile page, or click here: Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.

[kha1aan]

I’m not at home, but I’m currently on PTC v55, but I’ve seen the behavior that the Quest Pro does not see my 6Ghz network even though other computers and devices do since v53 when 6Ghz support was introduced.

I will respond to the rest of the thread once I’m home for the day as well.

[MetaQuestSupport]

Hey there, @kha1aan. Thanks for reaching back out and providing what version your device is on. We are looking forward to your response once you are able to get home for the day.

Please let us know if you have any questions.

[kha1aan]

From above, these are the results for 5Ghz, because the real problem I'm trying to solve is that even sitting a few feet from my access point my Quest Pro does not see a 6Ghz wireless SSID that is not hidden.

Network Band: 5Ghz
Channel Width: 160Mhz

Ethernet Connection: Connected

Wifi Signal Strength: Strong

Round-Trip Time Latency (RTT)  Appears to be 1-3ms on average
Received signal strength indication (RSSI) - Unifi Network Controller says Quest Pro is currently at ~ -48 dBm

My 6Ghz Network is currently configured as follows:

SSID: VR-Michael

Broadcast SSID: Yes

Channel: 37

Channel Width: 160MHz

MUMIMO: 4x4

Transmit Power 21 dBm / 27 dBm

Ch. Util. (Busy/Rx/Tx)8% / 0% / 8%

Please let me know what else I can provide to help in figuring out why the Quest Pro simply doesn't see this wireless network, yet the HTC headset, and multiple Windows PCs can see the 6Ghz network. (6Ghz only has one SSID on it, VR-Michael, and that SSID is only on 6Ghz)

[MetaQuestSupport]

Hey there, @kha1aan. Thank you for your reply and providing that information. So we can look into this further for you, can you please select our name to get to our profile page, or click here: https://metaque.st/CommunitySupport. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.

[jonstatt]

It is not just Ubiquiti, the Netgear Orbi 960 6E router 6E specific SSIDs don't show up in a Quest Pro either but do in an HTC XR Elite 

[MyloRuiter]

Same here , doesnt see Wifi 6E on either the Ubiquiti stuff or the new Deco Wifi 6E accesspoints.

[MyloRuiter]

And please no private messages @MetaQuestSupport . If you look at te PTC 55 topic there are a lot of users with wifi 6E not showing up on the Quest Pro . Its a community , not a private kittyhouse

[kha1aan]

Update to those that have posted in the last day --

Meta had used a private message to get a quest diagnostic bundle from me and converted from a help PM into an actual support ticket. I have at least indicated others are reporting the same with more than Ubiquiti devices in this thread and that they may want to look here as the feature (WiFi 6E support) may not be complete.