@manno02 the most recent one - 0.4.0

and again thanks for reporting

Perfect thanks for coming back to this. Btw I thought that this was also previously a problem.

@mff73 said in Altitude Gradient Screenshot please: @dimitrios-kanellopoulos said in Altitude Gradient Screenshot please: @mff73 is it also for iOS? Googled: [image: 1520520412495-57042688-3098-4301-a2a5-37fd262ccf62-image.png] perfect a friend of mine wanted this

Thanks Saw it in MC as well…

this is now a known issue (took some time due to low prio)

@dimitrios-kanellopoulos Take your time, and enjoy your trip!

Hi guys (again), let’s not spam this thread and create a new one at the Lounge of this forum so we can see how we can solve this issue with the belt. I have been also a victim of the belt not getting good readings but I managed to still use my 1,5 years old one with this: http://www.natharward.com/heart-rate-monitor-not-working/ But please lets create a new one at the Lounge yes please?

@slashas that as well but depending on how many moves you might have douplicates.

@dimitrios-kanellopoulos I guess you could say it that way too. If the current diary view didn’t show/calculate current week, then it would be correctly showing weekly average.

I’m also in the same situation, app showing 58 h of recovery time, and the phone 47 h. I could perfom a photo but no more information will be added

@omunoz nope not yet as there is not a real desktop version. This should come eventually as well. For now testing is limited only on the app

@mff73 yep! I will do! Love France man. What a nice country and people.

@slashas its not lost but the week gets cleared up afaik. But sure, definately something to improve.

@aldo70 said in Cannot Pair App to Spartan Ultra: @dimitrios-kanellopoulos yes, this is a good news, the bad one is that I have to send my spartan to be repaired (gps not working well) and I will be using my Ambit3 … which is not supported by the app. Anyway I am happy to be connected again !!! first world problems (joke). Happy it went good.

@johan6504 said in HR zones are not correct: @jouko-from-suunto @Dimitrios-Kanellopoulos This issue with presentation of wrong data has been part or this beta since the start. And from what I can see hasn’t been resolved yet. I have been working with data visualization development for 8 years (https://spotfire.tibco.com/). One thing in applications involving getting insight from data is to never ever show wrong data, the user needs to trust the data. It is something you avoid at all cost, what is your thoughts about this? Is the problem so deeply buried in legacy code that it requires refactoring or why has it been left unsolved? I get my correct data from STRAVA or MC so I do get my data, but from a beta perspective it feels rather strange not to fix this… Same here

@ze-stuart thank you, I will give that a try. Yes indeed regarding only one bike, I have the Speed & Cadence sensor on two bikes, I haven’t even tried pairing the two, only my commuter bike so far.