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.
