BikeControl - MyWhoosh Link on iPad not working

[abeilprincipino]

Hi all,

I'm having an issue when I try to control MyWhoosh on the same iPad running BikeControl.
If I use my iPhone to run BikeControl it connects immediately (blu link icon on MyWhoosh) and everything is smooth.
If I try to do the same from the same iPad that is running MyWhoosh application I cannot get it to connect.

My Zwift Ride is connecting perfectly to BikeControl but I can't get MyWhoosh connection.
I've checked the logs but there's basically nothing.

What can I do?

Thanks in advance,

[jonasbark]

Did you follow the instructions from
https://github.com/jonasbark/swiftcontrol/blob/main/INSTRUCTIONS_MYWHOOSH_LINK.md

?

[abeilprincipino]

Hey Jonas,

Thank you for the prompt answer.
Yes, I did follow the instructions but nothing :(

[javi-flow]

Hi @jonasbark ,

same issue here, let me provide more details:

myWhoosh Link on Android device -> myWhoosh on iPad ✅
BikeControl on Android device -> myWhoosh on iPad ✅
myWhoosh Link on same iPad -> myWhoosh on iPad ✅
BikeControl on same iPad -> myWhoosh on iPad ❌

thank you for your great work, I'm happy to help/debug

[jonasbark]

I was able to briefly able to reproduce it, but it "fixed" itself after:

• opening MyWhoosh Link => works
• closing MyWhoosh Link
• opening BikeControl => works

[Frucoboti]

Hi everyone,

I've been investigating this connectivity issue using Proxyman to intercept the traffic between the MyWhoosh main app and the Link emulator (Bikecontrol).

I found a consistent point of failure that might be the root cause. MyWhoosh appears to use an Amazon MQ (MQTT) broker as a signaling server to exchange local IP information before attempting the local handshake.

In my logs, the connection to this specific endpoint consistently fails with a SSL/Status 999 error or a timeout:

Endpoint: b-0f4c34b8-9348-4437-b915-8c832e4df381-1.mq.eu-west-1.amazonaws.com

Port: 61619

It seems MyWhoosh has implemented strict SSL Pinning or a specific security layer on this port. When this connection fails, the apps never "announce" themselves to each other, so the local discovery never starts. Even when bypassing SSL proxying, the handshake on port 61619 is extremely sensitive.

@jonasbark, could it be that MyWhoosh changed the authentication method or the specific broker instance for the eu-west-1 region recently?

[jonasbark]

I have no tangible insights there, but MyWhoosh Link announcing the internal IP via MQTT may explain why, for some users, the Link connection within BikeControl works when starting MyWhoosh Link beforehand.

BikeControl doesn't do any announcements itself and it will hopefully be obsolete soon, anyway

[Frucoboti]

@jonasbark thanks for the feedback.

To clarify and add more context: the official MyWhoosh Link app is also failing to connect under the same conditions. It stays on the "Waiting" screen indefinitely.

Through the logs, I can see that the official app also tries to reach that same Amazon MQ broker on port 61619 and fails. This suggests that the issue isn't specific to Bikecontrol's implementation, but rather a broader problem with how the MyWhoosh ecosystem handles the signaling/handshake process in certain regions or network setups (possibly due to aggressive SSL Pinning or port blocking at the ISP/Broker level).

If even the official app can't establish that initial "handshake" via Amazon, it's impossible for any local discovery to trigger.

Do you think there is any way to "spoof" or bypass this cloud requirement, or is the app now completely dependent on that Amazon MQ response to even start looking for local devices?

[fraagol]

hi @Frucoboti ,
did you make any progress in your investigation or got any feedback from MyWhoosh?

For me, the connection between Link (or BikeControl) and MyWhoosh is very unpredictable. Sometimes it works sometimes it doesn't.

I agree on your diagnosis about the Amazon MQ broker. For me, when you connect Link first, you get more chances to connect BikeControl from the same device afterwards, so the local ip announcing seems valid. But not always

I was considering also the Proxyman approach, but I don't think I would get further than you

[jonasbark]

I just published 4.7 for those plagued with the MyWhoosh Link not working:

You can now use your iPhone to act as Bluetooth keyboard for your iPad. In my tests this worked really well. Currently MyWhoosh on an iPad seems to only support virtual shifting keys (K + I)
https://www.youtube.com/shorts/qalBSiAz7wg

[beFinisher]

Hello everyone, yesterday I bought the bikecontrol application for iOS but I can't make it work with mywoosh, neither on iPhone, nor on iPad nor combining both. Bikecontrol recognizes the Zwift play when you press but in mywoosh it doesn't work, I don't understand the section where the link icon is supposed to light up in blue ... it always comes out in gray.

Tell you that where I am I don't have wifi so I have mywoosh on iPhone using 5G data or I share the iPhone's wifi with the iPad and use it but I can't get it to work. If you can help me, I appreciate it.

[jonasbark]

Here's a lot of useful information about the Link method:
https://github.com/OpenBikeControl/bikecontrol/blob/main/INSTRUCTIONS_MYWHOOSH_LINK.md

[beFinisher]

Hello, I also tried it before entering this forum as you have in the instructions but it doesn't work or something I'm not doing well.

[pvid]

I am also facing a similar issue. Running BikeControl on the same iPad as MyWhoosh does not result in a link connection. Running Link app on the same ipad works. I also tried running MyWhoosh on iPad and BikeControl on iphone - also does not work, while running Link on that iPhone results in a connection. I am running the latest version of both MyWhoosh and BikeControl and connect via WiFi

[jonasbark]

I assume you did it exactly as written in the instructions, i.e.

1. launch MyWhoosh
2. launch MyWhoosh Link, check if connection works => close MyWhoosh Link completely
3. open BikeControl, check if "Link" connection method is enabled (try de-selecting and enabling again)

I've tried this many times and succeeded nearly every single time.

Which version of BikeControl and MyWhoosh do you have? Just to be sure.

[fraagol]

I am also facing a similar issue. Running BikeControl on the same iPad as MyWhoosh does not result in a link connection. Running Link app on the same ipad works. I also tried running MyWhoosh on iPad and BikeControl on iphone - also does not work, while running Link on that iPhone results in a connection. I am running the latest version of both MyWhoosh and BikeControl and connect via WiFi

Hi @pvid ,
when connecting MyWhoosh Link, they store your local ip in a remote server, and then MyWhoosh uses that ip to connect to MyWhoosh Link.
So, it is very important that you first connect MyWhoosh Link in the device that you want to run BikeControl.

I had the same issues when I was trying different configurations.

I also noticed recently that the MyWhoosh icon that turns blue when connected to MyWhooshLink doesn't seem to work consistently. Sometimes it doesn't turn blue but BikeControl is connected and working. Sometimes pressing the grey button makes it turn blue.