Bluetooth I understand and makes perfect sense in a controller. Is a very common way to connect a human interface device wirelessly. It is a direct connection and can be very lower power and doesn’t need to transfer alot of data.
Not only did the Steam controller support Bluetooth like you mentioned but i believe the recent Xbox and PS5 controllers support Bluetooth as well. I think even the Nintendo Wii controllers were Bluetooth.
WiFi doesn’t make much sense in a controller when Bluetooth already exists.
Unless the controller has features that would benefit using WiFI over Bluetooth.
For example I could see maybe an advantage in a steam steaming/steam remote play situation. Instead of a controller going Bluetooth to local device and that local device passing the commands to the remote device, the controller could talk directly over the network to the remote device saving some latency for a more responsive experience.
But I don’t know why they would pick 5GHz that is more of a higher bandwidth application as far as i understand. You don’t need that for sending basic controller commands 2.4GHz would be more than enough. Maybe it has something to do with Latency if your 2.4GHz network is congested you could to go with the less congested 5GHz frequency.
Eh. I’m not sure the implementation details and how high or low level their alterations are. Do they establish connections similarly and just not expose the details and packet formats to end users, or is it completely redone?
But either way, Bluetooth is pretty mediocre for just about anything, and the only way to get good results is to own both sides of the connection, with a console or with a dongle.
WiFi-Direct is a terribly underused mechanism and I wouldn’t be surprised if they went with a WiFi connection to be honest. A point to point WiFi connection is faster, has lower latency, and can deal better with interference. The original Xbox One wireless controller came with a dongle that was just a WiFi card (not a Bluetooth card) with weird firmware, so it wouldn’t be the first time.
Bluetooth is very susceptible to interference, the protocol is annoying to work with, and the frequency band is full of random crap. Its saving grace is that just about anything supports the standard Bluetooth HID input.
I’ve also used Stadia and that worked quite well. What if they’re making a Chromecast version of Steam Link that’s connected to your controller? Take your controller anywhere, connect to a Chromecast, and start playing games from your library. That’s another way for Valve to make use of a Steam controller with WiFi that I wouldn’t be averse to.
Specific low-power wireless devices (wireless devices for wireless access systems including wireless LAN (5150-5350 MHz, 5470-5850 MHz frequency band))
Bluetooth I understand and makes perfect sense in a controller. Is a very common way to connect a human interface device wirelessly. It is a direct connection and can be very lower power and doesn’t need to transfer alot of data. Not only did the Steam controller support Bluetooth like you mentioned but i believe the recent Xbox and PS5 controllers support Bluetooth as well. I think even the Nintendo Wii controllers were Bluetooth.
WiFi doesn’t make much sense in a controller when Bluetooth already exists. Unless the controller has features that would benefit using WiFI over Bluetooth.
For example I could see maybe an advantage in a steam steaming/steam remote play situation. Instead of a controller going Bluetooth to local device and that local device passing the commands to the remote device, the controller could talk directly over the network to the remote device saving some latency for a more responsive experience. But I don’t know why they would pick 5GHz that is more of a higher bandwidth application as far as i understand. You don’t need that for sending basic controller commands 2.4GHz would be more than enough. Maybe it has something to do with Latency if your 2.4GHz network is congested you could to go with the less congested 5GHz frequency.
Proprietary wifi connections perform better significantly than Bluetooth. Bluetooth’s performance blows.
Can they still call it WiFi if it is a proprietary version of WiFi?
Eh. I’m not sure the implementation details and how high or low level their alterations are. Do they establish connections similarly and just not expose the details and packet formats to end users, or is it completely redone?
But either way, Bluetooth is pretty mediocre for just about anything, and the only way to get good results is to own both sides of the connection, with a console or with a dongle.
deleted by creator
@conciselyverbose @ylai @Aurenkin @Catsrules @anon232 we need to support libre and open source things here.
Bluetooth isn’t any more “open”. And more importantly, it’s a horseshit standard with all of bad stability, bad latency, and bad performance.
WiFi-Direct is a terribly underused mechanism and I wouldn’t be surprised if they went with a WiFi connection to be honest. A point to point WiFi connection is faster, has lower latency, and can deal better with interference. The original Xbox One wireless controller came with a dongle that was just a WiFi card (not a Bluetooth card) with weird firmware, so it wouldn’t be the first time.
Bluetooth is very susceptible to interference, the protocol is annoying to work with, and the frequency band is full of random crap. Its saving grace is that just about anything supports the standard Bluetooth HID input.
I’ve also used Stadia and that worked quite well. What if they’re making a Chromecast version of Steam Link that’s connected to your controller? Take your controller anywhere, connect to a Chromecast, and start playing games from your library. That’s another way for Valve to make use of a Steam controller with WiFi that I wouldn’t be averse to.
Yeah that is a good reason.
And looking at the documentation it just saids it uses the frequency band of WiFi not that it uses WiFI. https://www.rra.go.kr/ko/license/A_b_popup.do?app_no=202317210000256753
translated