I saw in previous threads that there were problems with the Saris H2. I’m not sure the current status, but I’m having problems with erg mode occasionally missing changes.
For example, today I was doing the 5x5x20/10s workout and in the second set it missed 3 of the 5 changes to 120%. I thought maybe the workout was programmed incorrectly, so I redid that section (discarded, started over, skipped ahead) and it caught all 5 sections.
I had this problem several months ago and stopped using the app but tried again and seem to still be having this problem.
I rebooted my phone. Disconnected and reconnect all devices. Rebooted again. I’m sorry I can’t reproduce it. It happens inconsistently, but frequently.
HI, sucks!!! One solution is to click slope and back to ERG. We believe we understand how to improve this and we should be launching a solution for this in the next 2-4 weeks. This seems to affect a small number of devices but Saris and Elite tend to have this type of issue more often. We had a previous solution that seemed to solve this but it caused other issues so we now believe we know what to do.
Hi, it also happens to me. I worked around by tapping on the actual power (switch from Watt to % and then to Watt again). This “magically” solves .
Old Samsung J7 Duo, Android 10
It’s only a real pain during sets of 20/10s or something like that we’re you’re trying to get that quick change multiple times in a row. Having to fiddle with the screen is a real downer.
Hi team, good to hear that this problem is in focus. If it helps - same issue on the Elite suito for me. Had this yesterday during a ramp test. In the ,middle of it I was stuck on one watt level for the rest of the test so I startet it again. After that no issues. Same today during short intervals. Some spikes worked as intended and some did not. Thanks!
So my tester keeps trying to reproduce the issue before he seemed like he could do it within 1 hour and my developer did a fix and it seemed like it took him close to 3 hours to reproduce it. Because it takes so long to reproduce it’s very hard for us to know when it is fixed. It might be improved but seems like it is not 100% yet. We are still working on it and will keep working on it until we can’t reproduce it and no one reports it. I have not heard any one report it in a long time.
20 30/30s you like punishment. Good news, it would be great if it is fixed for you. Only a couple other people reported it so it’s very hard for me to say how many people it affects.
Because it takes so long to reproduce it’s very hard for us to know when it is fixed.
I have a theory that it happens more often in higher gears. I imagine it has to do with how fast the flywheel is already spinning when the signal is sent. TBH I have no idea if that’s actually true. But that seems to be when I noticed it most.
We are seeing that for us it always happens when trying to tell the power to drop not when trying to raise the power. My developer says he sees it going from threshold down to recovery and was worried he would not see it from 80% down so he is doing a lot of short threshold intervals So this kind of aligns with your thinking but we still think it is some bug in our software and then in this case our software has nothing to do with flywheel speed or actual power. But it does seem it is device specific and only affects some devices. So it’s strange for sure. How many devices do you have connected? He could only get it to happen when an HRM is connect for example.
Oh yes we have a special logging function. Are you willing to work directly with my developer on this? We can’t reproduce it any more. It would be ideal if we could get on instant messenger for communication but not a requirement.
.