As per the title.
Web app is fine and correct.
What is going on here?
It is aprox 0.69IF on the web but 0.45IF in the mobile app. Ftp setting seems to be the same
As per the title.
Web app is fine and correct.
What is going on here?
It is aprox 0.69IF on the web but 0.45IF in the mobile app. Ftp setting seems to be the same
One other user reported this. I saw it once and then can’t reproduce it. It’s very strange. Investigating.
Yes..its working again. Have had the same issue with my ThinkRider.
But - I figured out an other issue in the app. It’s a minor thing, but maybe worth mentioning: A workout with focus on Sweet Spot should not be marked as ‘recovery’. Additional the intensity factor is different from the value in the Web-App. For example: A VO2max WO which has an IF of 1.02 is marked in the Mobile App with 0.66. Maybe I’m doing something wrong, but I don’t know what ![]()
Can you show me a screenshot? This does not sound like you doing something wrong. IF 1.0.2 is the hardest recovery ride I have heard of…
This is the screenshot how it appears on the mobile and below you can see the screenshot from ‘My Workouts’ in the Web-App.
What causes the difference in stress and intensity? The mobile app is updated (Ver. 9.8.3)
It is possible but I can’t really explain it until I check something with my developer. But right now you should try refreshing the app and tell me if the app still shows the same. On my devices it shows the same.
After refreshing the app it still shows the same issue. Seems to be only in the mobile app because in the Live display the zones are correct.
Oh I see it’s just in the popup in the mobile app. The list is fine. Let me research more.
Merging these conversations. I saw it once and now can’t see it again but I will figure this out.
I uninstalled the mobile app and reinstalled, so it is the latest version.
I tried changing my FTP and CP but it didn’t help.
Nevermind, I’m seeing the problem now. Sorry.
Is it because I recently got a device with running power and threshold for that is 405 watts. Where as my bike threshold is 220 - 225w
No the problem is I switched from using server calculations to app calculations and segments that start at 70% of FTP end with NULL/0, which means flat segment… but my calculation in the app treated it as a ramp down. If you see this issue. It’s the visual problem of how the TSS is calculated.
Fix is coming tomorrow (should be).
Thanks.