There is a document on how epoc is calculated at https://assets.firstbeat.com/firstbeat/uploads/2015/10/white_paper_epoc.pdf There is an Ambit app that uses stryd power reading to calculate your energy efficiency similar to the running performance on ambit which was far more accurate than relying on gps data. http://www.movescount.com/apps/app10645993-Average_energy_efficiency Notice the level of filtering on Ambits Running Performance graph relying on gps vs the energy efficiency app relying on power data. By the time you notice changes in Running performance graph to figure out whether you have proper hydration or enough carbs; energy efficiency app would react much sooner as it gets its data from accelerometers vs. gps and barometer on watch used by running performance. Your body makes subtle changes to adapt to current situation, it does not think about finishing line, thats what brain is for (or not). The sooner you notice the sooner you can react because physiological response to recover gets Progressively slower the father you fall in anaerobic energy debt. Constantly changing wind speeds would render ascent descent baro sensor data invalid even on a flat surface no matter ambit or s9. Epoc modeling has a delay, see white paper, basically loose ohr or belt ruins it. Real time running economy would react sooner than any other method. Your model is based on power, sensor will not become loose or fall off (less likely than belt or ohr) Or better yet, Having a small “sandbox“ for custom equations and graphs sent to SA from s9 like we did on Ambit To MC would stop avalanche of nagging user requests to add features. It would also let us innovate without consuming other peoples time on development. Few 32 bit floating data as temporary registers to implement equations is not much of a footprint these days. Add a few kb of data to support at 10s logging interval. It would just be much more fun even if it fed you meaningless numbers. <nudge> <nudge>

@Dimitrios-Kanellopoulos Hello , I also have the concern to transfer big move. I installed version 3.6.x, at first it worked, but no longer I have a move of 12h and she does not want to transfer to the app suunto. I am French, sorry for my English. THANK YOU

@TELE-HO @jahtba just thinking exactly same, take a look on S5

@pilleus … avoid hills… I prefer them to collect more vertical meters Thanks guys, I’ll check this out on the laptop, soonish

I just did an export. Things are getting better and worse at the same time. On the export side, I have now almost all the activities exported: in the app: 3135 activities fit files in the export: 3127 8 are missing. I digged a little to find the missing activities : 1 in 2020: alpine ski missing in January, in a day with multiple activities 2 in 2018: alpine ski missing in January as well 2 in 2017: alpine ski missing in December 1 in 2013: a duplicate in the app (running in February) 2 in 2012 : 2 duplicated yoga activites in August 2011 is something else, with some activities appearing in the export and not in the app and missing activities in the export. I haven’t checked all the activities missing in the export, but some appear like this in the app: [image: 1739804622484-4f2655d5-a9ba-4d89-bdd0-67346feb5be6-img_0831.png] I’m concerned about those missing activities and hope Suunto can do something about it. This also conforts me in using Rungap to frequently backup fit files of all my activities.

@freeheeler I’ve never tried to forget the phone from the watch side. Will have a look. Even if you turn Bluetooth/pairing off on the watch, I think you still need to ‘forget’ it in the Suunto app before you can pair a different watch. I always try to run to one side to allow cyclists to pass. My worst ‘silent’ experience from pre-aftershokz days was a dog nipping at my ankle out of the blue. That was what persuaded me I needed a different way to listen to things whilst out and about in the middle of nowhere.

The colored HR graph is really useful. But it would be nice, if the app would persist the last used setting of this graph. I always want the HR graph first, but whenever I open an outdoor activity (with GPS), elevation (1st metric) and heart rate (2nd metric) are selected. So I always need to deselect heart rate and then select heart rate for the first metric to get the colors. And if I open this graph in full screen mode, my selected metrics are NOT displayed in fullscreen. Instead the selection is always reset to height/hr/speed (at least this is the case for cross country skiing) and I need to make my changes again. So if the user has selected HR as the first metric in non fullscreen mode, it should also be the first metric in fullscreen mode. That’s what I would expect as a user. Another nice addition would be, if the interval sections of a structured interval would be displayed inside this graph (at least in full screen mode). And even better: if those sections could be selected and some metrics about the selected section would be displayed. For example: min/max/avg HR or some info about how long I have spent in the targeted HR zone (maybe as percentage). But to be honest: I don’t know how all of this can be displayed on a smartphone screen. Maybe this is something for tablets

@ChrisA said in ZoneSense: Actually I would interpret it that way, that your interval workout was deemed aerobic as a whole and that you could increase intensity, if you want. Zonesense is not about HR measurement, Suunto says, but about Heart measurement, measuring the stress of the heart. And I think it makes sense, seeing that after your short intervals Zonesene tracks you moving into higher aerobic states. This is by far the easiest to digest explanation of the behavior I have seen. This makes perfect sense.

@dimitrios-kanellopoulos as you wish! Feel free!

Just for clarification Android has autosync when possible. On iOS that was on the past but not anymore.

@Ville-Päivätie afaik I am sure the Android app supports EON so please give it a try. (I think or else it’s hidden from you)

@Dimitrios-Kanellopoulos Ambit 3 users also need this fix. Suunto app fore Ambit has only default HR zone.

@SlaSh Thanks for the explanation, I agree, with just display " - - " like when I turn on the “Daily HR” is more clear for the customers.

My app is also syncing in the background, that is no problem. It was syncing while completely off and that behaviour was new. But seems like its gone already, now App & Watch only sync when app is running, front or background doesn’t matter. @Brad_Olwin said in Strange behavior or lack of knowledge?: @jthomi my app is syncing in the background. Occasionally, it does not and I need to force quit the app. When the app fails to automatically sync, if I check the watch connection it usually cannot connect to the watch. This is rare and either an app force quit or iPhone reboot solves the problem. I do not think this is an app problem but a BT communication issue. When this occurs, my notifications are often missing too.

@Armin-S Thx a lot. I agree with you about displaying heart rate or whatever. Therefore, I think users have to be able to customise this section with their own values. For me, it would be recovery time.

@fweens Pool swimming does not support intervals. That is the only mode that does not as it tries to cleverly define pool lines of course after they are done (pushing on the wall for example “turn”) . Try another mode.

@margusl Usually on the IBI you apply the instant conversion to HR, you crop big and low values and then you do 1-2 rolling average filters. To normalize the HR graph. However , IBI/RR should not derive from HR. They hold more information that the HR (which is kinda stupid imo but well). But I can see perhaps why one would put that chart there, that should be due to showing that the value exists , even if it’s not an RR/IBI plot eg like Runanaluyze does .

@surfboomerang hey it works! Seems to be taking while. Maybe like Pantene add it won’t happen overnight but it will happen!

https://forum.suunto.com/topic/2499/download-a-fit-file-from-suunto-app/7

@Dimitrios-Kanellopoulos here is the link: https://app.suunto.com/move/philip220621/5d33f88517683a59249d4862 Is that what you wanted? The same information shows up on the watch - so it is not a graphing error.