JohnnyG
Active member
I’m not sure what Polaris was thinking when they decided to require Ride Command to use Bluetooth tethering instead of a good old-fashioned Wi-Fi connection. They really missed the mark on this one.
Here’s my problem: Samsung phones will not allow you to Bluetooth tether a Wi-Fi connection. The phone forces Wi-Fi off. I can Bluetooth tether the mobile connection, but that does not help much because I usually do not have cell service where I ride.
I run a Starlink Mini on the roof of my XP5, so I almost always have a solid connection.
The plan is to add a Raspberry Pi 4 to act as a bridge between Ride Command, using Bluetooth, and the Starlink Wi-Fi connection.
I have the hardware and took a run at it last night. Right now, I am having trouble getting the Pi to connect to Ride Command, but I will keep working on it.
Stay tuned.
JG
Here’s my problem: Samsung phones will not allow you to Bluetooth tether a Wi-Fi connection. The phone forces Wi-Fi off. I can Bluetooth tether the mobile connection, but that does not help much because I usually do not have cell service where I ride.
I run a Starlink Mini on the roof of my XP5, so I almost always have a solid connection.
The plan is to add a Raspberry Pi 4 to act as a bridge between Ride Command, using Bluetooth, and the Starlink Wi-Fi connection.
I have the hardware and took a run at it last night. Right now, I am having trouble getting the Pi to connect to Ride Command, but I will keep working on it.
Stay tuned.
JG
