-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HR monitor connection issues with latest beta #751
Comments
debug-Thu_Mar_31_09_36_16_2022.log |
@janabouc your HR is still OK with the lastest beta? |
Yes!
… |
Not sure what else to try. I have not changed any settings and the issue started when I updated to look at the pzp api issue. |
Will do. Thanks. I'm at the dentist. 🙄 |
Worked instantly this morning for me. |
I will test tomorrow and let you know. Thank. you.
|
@janabouc sends me this |
@janabouc in this log I saw metrics from treadmill and HR isn't it? |
Yes. With cacheing turned on, treadmill and HRM connected. |
ok so just to summarize: the issue that is remaining is only when "Apple Fake Device" is ON. In this scenario your HR device is not recognized correctly unles you disalbe the ios heart cache new setting. |
On my iPad with my rower it wouldn't connect to my Polar until I turned off HR Caching. Everything else was good. |
@janabouc so the behaviour is different from treadmill to rower? |
Seems like it. |
@janabouc ok so try to use profiles to manage it. let's see if it's deterministic |
Yes. I set up a profile for rowing on the iPad with HFB along side to do a PZ ride on the rower. It worked well except my FTP must be lower on the rower -- I couldn't get to zone 6 except for a few seconds and Zone 4 felt like 5. Having the profile to change it just for rower is great! I guess i have to take FTP test on rower. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@janabouc can we close this? |
Yes. I think so. It was working fine today.
On Tue, Apr 19, 2022 at 10:38 PM Roberto Viola ***@***.***> wrote:
@janabouc <https://github.com/janabouc> can we close this?
—
Reply to this email directly, view it on GitHub
<#751 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONHDMI6J7NRPA2VUH7H6PTVF6J5VANCNFSM5SFO4RPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Jana Bouc
Website and Blog <http://janabouc.com>
Instagram <https://www.instagram.com/janabouc/>
Facebook <https://www.facebook.com/jana.bouc>
|
Describe the bug
Before the last update my scoshe hr monitor would connect every time with no issues. Since the beta it connects maybe one out of every 8 tries.
To Reproduce
Steps to reproduce the behavior:
I have set heart belt name to disabled and rebooted. Then upon restart refreshed and found my rhythm and selected it and hit ok and rebooted. Start qz it does not find the rhythm. Look in the settings and its still selected but when I refresh its not there.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Append a debug log
Follow this guide https://github.com/cagnulein/qdomyos-zwift/wiki/How-do-i-get-the-debug-log-in-case-something-doesn't-work%3F
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: