Steam Frame: Wireless Adapter "Paired, but could not connect" after Windows restart (WlanConnect error 1168)
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 42/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- networking
- 領域
- networking
調査の方向性
Start by reviewing the PC's remote_connections.txt entries around the Realtek driver initialization, repeated connection timeouts, and WlanConnect error 1168. Compare behavior with the onboard RZ616 Wi-Fi adapter enabled and disabled, since the reporter could not identify which of several changes restored the connection. Done means identifying why the headset fails to connect after a Windows restart and confirming a reliable fix across restarts.
索引モデルが issue の本文から書いたものです。
説明
Your system information
- Steam client version: 1792618285 (PC, beta)
- SteamOS version: 0.4.5
- Opted into Steam client beta?: Yes (PC)
- Opted into SteamOS beta?: No
- Have you checked for updates in Settings > System?: Yes
- Host PC: Windows 11 64-bit, MSI MS-7D75, AMD Ryzen 7 7800X3D, NVIDIA RTX 5080 (driver 32.0.16.2114), 32 GB RAM, SteamVR 2.18.4
- Steam ID: 76561198179305869
- System report submitted from the headset: Yes
Please describe your issue in as much detail as possible:
Expected: The Steam Frame connects to the included Wireless Adapter after pairing, and PC VR streaming via SteamVR works.
What happens: Pairing succeeds, but the headset never connects to the adapter.
Steam on the PC shows: "Paired, but the Steam Frame could not connect to the Wireless Adapter".
The headset shows the adapter as detected, then stuck on "Waiting...".
SteamVR stays on "Awaiting Wireless Connection", the headset shows "SteamVR not ready".
It worked at first (PC VR incl. Half-Life: Alyx ran over the adapter). After a PC restart it stopped working. A fresh re-pair fixed it once, but it broke again after the next restart. Now re-pairing does not help anymore.
From remote_connections.txt on the PC:
- Realtek driver initializes, "Dongle VR Mode Initialize Ok"
- then repeated "Connect timeout event"
- WlanConnect() fails with error 1168
- "sent ssid frame_CA7F6F2D"
The headset is found via broadcast, but the WLAN link between adapter and headset is never established.
Already tried:
- Unpair/re-pair on PC and headset, toggled "Enable Streaming Adapter"
- Clean SteamVR reinstall incl. resetting steamvr.vrsettings
- Steam client and SteamVR beta
- Different USB ports (rear motherboard USB 3.0, no hub)
- Disabled Bluetooth PAN adapter (stopped a USB connect/disconnect loop, but did not fix the connection)
- Windows Fast Startup disabled
- Firewall rules for Steam, SteamVR and vrserver allowed (private + public)
- Factory reset of the headset
Possibly related: a stale SSID on the headset side, as reported by another user who fixed a similar "Waiting..." state with softapcmd refresh via ADB.
Steps for reproducing this issue:
- Pair the Steam Frame with the Wireless Adapter (works, PC VR streaming works).
- Restart or shut down the Windows PC.
- Adapter is detected again, but the headset stays on "Waiting..." and Steam shows "Paired, but the Steam Frame could not connect to the Wireless Adapter". Re-pairing no longer fixes it.
Update: Got it working again.
What changed right before it worked:
- Disabled the onboard Wi-Fi adapter of the motherboard ("RZ616 Wi-Fi 6E 160MHz", also 6 GHz capable) in Windows network connections
- Re-plugged the Steam Frame Wireless Adapter into a different USB port
- Clicked "Pair" again from Steam on the PC
After that the headset connected to the adapter and PC VR works again.
netsh wlan show interfaces showed both adapters ("Realtek 8832CU Wireless LAN WiFi 6 USB NIC For Valve" and the onboard RZ616), both disconnected, before the fix. Possibly the onboard 6E adapter interferes with or conflicts with the Steam Frame adapter. Not 100% sure which of the steps fixed it.
Will report back whether it survives a PC restart, since that is when it broke before.
- 主要言語
- 言語のデータがありません
- スター
- 2.7k
- フォーク
- 89
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
ValveSoftware/SteamOS のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
ValveSoftware/SteamOS#3037 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
ValveSoftware/SteamOS#2983 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
ValveSoftware/SteamOS#2927 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
ValveSoftware/SteamOS#2875 · コメント 1 件 ·
-
steam-short-session-tracker: incorrect registry backup path resets settings during automatic repairオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
ValveSoftware/SteamOS#2829 ·
ValveSoftware/SteamOS の issue をすべて見る
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
virtualsquare/picotcp#88 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
imapproxy closeForMaintenance grace timer calls clientConn.Close() before closeMaintenanceTransport対応中かも @dejanstrbac が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
メンテナーはふだん 1 日以内に返信