Hi,
I’m having an issue where my Zwift Hub only shows up as a Heart Rate sensor in the pairing menu. It is not appearing under Power Source or Controllable, so I can’t get any wattage or resistance.
I have already tried:
Restarting the Hub (unplugged for 60s).
Ensuring it’s not connected to any other app/device.
Checking for firmware updates.
Any idea how to fix this so it’s recognized as a trainer again?
Thanks!
Strange, I would
Make sure it is not paired directly to your OS android/ios settings
Restart your phone
uninstall and reinstall our app.
reset bluetooth/network on your phone (loses all waif
I think I told you this before but my best friend in high school was Daniel47… 
Thanks for the suggestions. I’ve tried everything you listed (reinstalled the app, restarted the phone, reset Bluetooth settings), but the issue persists.
However, I can confirm that the hardware is working perfectly with Zwift. In Zwift, the Hub is recognized immediately as Power Source and Controllable. TrainerDay is the only platform where the Hub only appears as a Heart Rate sensor.
Since the Hub works fine elsewhere, it seems like TrainerDay is having trouble claiming the FTMS and Power profiles on my device. Are there any known issues with the Zwift Hub’s Bluetooth implementation in the current version?
Yeah I remembered that 
So I thought I remember other people using our app with a zwift hub. Jetblack victory has this same problem. I was told they advertise as HRM because then it works with AppleTV. So actually this is a problem how we try to categorize devices. Our desktop app has a new design that is more “fluid” in device recognition. Test that if you want. Can you send me a screenshot of your connections page. I can hardcode our app with Zwifthub to work like it does with JB victory until we can make our mobile app more like our desktop in dynamic device recognition.
I’ve attached the screenshot of my connections page as requested. It would be great if you could hardcode the Zwift Hub for now so it works like the JetBlack Victory on mobile. In the meantime, I’ll try out the desktop app to see how the ‘fluid’ recognition handles it.
Edit*: Desktop app works perfect. 
Thanks for confirmation. I have decided to actually just move to fluid model with mobile too. Should not be so hard since we have good working version in the desktop. I have one other user with a different but similarly related problem.
I have this same problem. Tried re-setting and re installing etc.
But does not detect as smarttrainer on my phone.
Installed desktop app and it Connects perfect.
Ok guys, I have re-written our bluetooth to work how it should have in the beginning but we did not know what we were doing 6-years ago We though bluetooth devices were much simpler. We though when a device said it is HR monitor it is an HR monitor… (like zwifthub). But all devices need to be discovered their hidden secrets… I know I know I look like a Ford Pinto but I am really a Ferrari… Anyway we need to test this a lot, but I was able to write some really good testing so hopeful our ble will be better than ever in the mobile app. The desktop already has this same model / rewrite done so less scary this time.
Hi, Alex. It’s the same for my Magene T300 Plus smart trainer - it’s showing as heart rate sensor and I cannot connect it to the mobile app on my iPhone (actually same issue on my ipad too)
It’s showing properly on the desktop app for Mac though.
I tried to close the app, unplug the trainer, reinstall the app but nothing works.
Should be new version tomorrow.
By the way, I was about to try the Mac app but started this morning, it just crashes few seconds after opening the app.
Here’s a video screenshot:
Oh no… I released linux version and we forgot to make sure it did not affect mac, so sorry. Fix coming asap. The mobile app with the fix might be avilable. Is for android not sure about IOS but coming today, just waiting on Apple to approve it.
Ok fix is coming in 5-10 minutes…
Fix is there. So sorry. Desktop has been treated more like a beta as we had a small number of users but more and more users are starting to use it so we need to be more careful. We will run all releases through full regression testing now going forward.
Thanks, Alex! I tested it just now, my Magene T300 is now detected as a controllable/trainer in the mobile app for both Android and iPhone.
Actually, I am aware that the desktop app is still currently in Beta but because I can’t connect my trainer to my phone yesterday I tried the desktop app and it did work with my trainer. I have a scheduled workout today, so I thought I’m gonna use it but then that’s how I encountered the crashing earlier.
But all great now since I was able to do the workout on mobile. 
Yeah!!! on the mobile working, thanks for confirmation.
Yes, your experience just moved it out of beta… Meaning we are up to about 40 people a day using the desktop app and increasing every week so I have to start to take it serious. This was just total mental oversight…. Usually I have my tester test everything before deployment.
Best of luck with your training.
I see Apple is approved now. Hopefully all devices are fixed!!!
Yes. It worked perfectly today.
Great app! And great support!
