I don’t have any direct Bluetooth pairings with the Neo, only through the app
I’ll give it another try today
Update. It worked fine today and I think I found the problem with yesterday, and it was at my end.
I am pretty sure there was a 3rd light showing on my Neo yesterday (the middle one), and I expect that was an error notification of some sort.
Sorry for not realising this yesterday.
WRT today’s workout, it took the full 20 minutes of the inital 20 min workout to get up to the HR target with the 120 sec steps. Seems a bit long to get up to target. I then auto extended for a total of 75 minutes, and the adjustments of power up and down were within a tight range which was great, and probably attributable to the long warm-up. So pros and cons in the new algorithm for me anyway
I believe you’ve nailed the reason, it’s a per-person dependent situation due to how HR lags vs power. For me, the HR can lag up to 20-30s before it catches up the the power I’m outputting.
Good news. Sounds like you are using the beta version. You should try our production version. We are doing a 120 second test right now. The prod one is 60/30 60 up 30 down. We will go back to 60/30 in beta early next week.
I tried to go back to the production version by leaving the beta group, uninstalling the app, and then installing the app again. But when I did this I got a message to say the beta version of the app is still installed and I should uninstall it.
Is there another way to roll back to the production version?
I just uninstalled again and re-installed and still get this message despite not being in Beta. See attached
Oh no. Sorry. I am not really an Android user so I don’t know how to “escape.” We will try to have beta version fixed Monday or Tuesday if you can wait. I did not expect so many beta users to be using this HR feature. If you don’t figure it out, I can try to escape beta also and give instructions. I do have Android for testing.
Sorted.
For future reference in case someone strikes the same problem, I had to Clear Data in the Storage settings for Google Play Store to let me install the production version again
Oh that is good to know. Thanks for that info. Since I am not Android user I don’t know all the tricks.
I was excited to try the APP, especially for the HR feature, but I must say my first experience was not good. I use Wahoo Kickr 6, with an iPhone. On the TV, I have a Apple Tv that runs Zwift, but only cadence and power, not controllable.
I set the HR to my preference. (why one is only able to change the HR in increments of 5%, does not make sense. I want to set it to a specific number.) Then started pedaling, it was like torture. There was no rhyme or reason, when my target rate was lower, it would drop the Watts, and when my HR was already above, it would further increase the Watts. I set, power smoothing to 5secs, I tried disconnecting and starting again, it only worked for a brief period, when I reduced my target HR below what I really wanted and when after 5mins, I felt brave enough, to up it by 5%, the craziness started again. Let me know, when you’ve sorted it.
Hi, sorry for your experience. You can go to settings and change it to 1% increases. It works well for many users. I only know of one other user that it does not work correctly for and I am working with him to try to figure out why. It’s something to with his specific heart conditions (post surgery) but still it should work for him and for you.
Do you have your threshold HR set correctly? I have Kickr V5 and works perfectly for me. Can you send me the link to your completed activity from our website?
Thanks, I changed the increments to 1%. Here is the link. There is one more that is shorter after I tried to restart.
https://app.trainerday.com/activities/6506c388897bc6e2eaf271a6
That is very strange. What heart rate monitor are you using? My only guess right now is we are receiving zeros (or strange values) from your HR monitor and we filtering them from the UI and data but they are being processed by the logic. Just a guess as this is strange. I have one other guess. That our next version of our app will fix. We have 3.9.2 today but sadly that has a different critical bug…
Also what did you use for your HR target? We will definitely get this fixed.
I use a Wahoo Tickr, a fairly new one.
Ok that should not be it. Let’s see (hope) the next version 3.9.3 fixes this issue. In Android you can join our beta program. In IOS, I could invite you if you want. Or you can wait until it gets to production version. Don’t join android beta now because current version has serious bug 
If 3.9.3 does not fix your issue, I will try processing your data from code and see if I can spot the problem.
I can see it looks like it was working correctly and then stopped.
This is similar to the issue the other user I am working with so I am hopeful my fix, fixes the issue. Something strange did happen to HR, but does not look to be cause of issue.
I realized one more test you could do now that should prove my theory of the problem which is if you set your FTP to 260 I think it will work better or ideally great. Also in looking at our site I do see some strange HR values. This does not seem to be the cause of the problem but you never know. Make sure your HR sensors are wet.
Thanks, will try again and report back.
1 Like
Sweet!!! I guess you updated to our latest version which likely fixed your problem. 
1 Like