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.
The steam controller has a bluetooth mode you can activate upon turning it on.
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.
[This comment has been deleted by an automated system]