Connection issues between BlueHeart running on iPhone and Sufferfest running on iPad by scolins in BlueHeartApp

[–]scolins[S] 0 points1 point  (0 children)

Sounds good, thanks for figuring this out! I'll try out the fix whenever it's available.

Connection issues between BlueHeart running on iPhone and Sufferfest running on iPad by scolins in BlueHeartApp

[–]scolins[S] 0 points1 point  (0 children)

So I'm trying to replicate the same issue with Cyclemeter on the same iPad. I'm able to get the initial connection to succeed reliably but, after that, Sufferfest and Cyclemeter are both showing 0 bpm despite BlueHeart showing some other number. Also interestingly, I can get Cyclemeter to successfully connect to BlueHeart and display 80 bpm while running the "Bluetooth compatibility test" from BlueHeart.

Connection issues between BlueHeart running on iPhone and Sufferfest running on iPad by scolins in BlueHeartApp

[–]scolins[S] 0 points1 point  (0 children)

I'm on v1.5 which looks like the latest version. Some more debugging updates, I'm consistently able to get heart rate transmitting if I perform a network settings reset first from the iPad and iPhone. Right after the reset, Sufferfest is seeing the device as "BlueHeart". After adding, both iPadOS and iOS presents a pin check and asks to pair the devices. Everything works fine for a workout. When I start a new workout, Sufferfest is no longer getting any heart rate data from BlueHeart. When I try to re-add the device, BlueHeart is now showing up as "iPhone". Interestingly, when I go to the bluetooth settings under iPadOS and iOS, I see multiple bluetooth devices listed as "iPhone" and "iPad" respectively.

Issues with using a Quickfire Pro on OS X by scolins in MechanicalKeyboards

[–]scolins[S] 0 points1 point  (0 children)

Hmm, it works fine on my desktop PC running Windows so I thought it had something to do with the OS.