Open DeManMetDeHamer opened 5 days ago
hi @DeManMetDeHamer the debug log is corrupted, you need to wait the finish of the upload before pushing comment. Please upload it again and let me know! thanks
debug-Wed_Oct_16_08_03_27_2024.log
Hope this is now working
@DeManMetDeHamer remove the VIFHTR2 device from the heart rate belt setting and press ok and restart QZ Let me know!
@cagnulein That fixed the issue with the bike not connecting to the phone, however mywoosh still does not find the qz device. I renamed the bluetooth name to bike like you said, and restarted the phone.
Anything else i can try?
on which device mywhoosh is running?
It is running on an android 13 tablet. If im using qz from my iPhone it finds the device normally but from this android version it does not
you can't run mywhoosh and qz on the same device. you need one device for qz and one for mywhoosh. I guess this is your issue Let me know
if you are instead using 2 device (2 android devices), be sure to rename your phone with qz to "bike" from the android settings and reboot it
im using an android phone with qz on it and a tablet running mywoosh. For the phone i renamed it in the system settings to bike and rebooted. im currently trying the same with the bluetooth name.
ok let me know
debug-Wed_Oct_16_09_38_50_2024.log
I renamed the qz phone in both Bluetooth and system settings. Now the app seems to think it connected but the bike does not. And mywoosh still does not find it
if i remember correctly the issue of this bike is that the bike it's connecting to the FTMS virtual device from QZ creating a dead loop. If i'm right, disabling the virtual bluetooth device setting in the experimental settings you will fix this. I don't remember if mywhoosh has the ability to connect using the Wahoo KICKR device from QZ as zwift does. I guess mywhoosh does this only on PC.
Let me know
Describe the bug Android beta does not connect to vitufit htr 2.1 and does not broadcast for mywoosh
Desktop (please complete the following information):
Smartphone (please complete the following information):
Append a debug log [Uploading debug-Wed_Oct_16_08_03_27_2024.log…]()
Additional context Add any other context about the problem here.