What do you expect from the next update?

@seanvk said in What do you expect from the next update?:

Support for multi-sensor pairing when of the same type

I second that!

Jacek M

@Frederick-Rochette better cycling support. ClimbPro is one thing, but it is really irritating that you cannot pair with watch two dedicated sensors for speed and cadency. BTW it was possible in ambit2 watches. In current models including vertical you can either connect speed or cadency unless you are not use two in one sensor. Other thing is that it will be good to have few slots for each of this sensor types so I can pair sensor for few bikes, without a need to pairing each time I am choosing different bike.

Egika

Now the “what do I think the update will contain” became a “what would I like to get”

seanvk

I would expect a better separation of VO2Max for non-running. It’s amazing how a week of hiking in the Canadian Rockies tanked Suunto’s VO2Max.

leafs93

Not sure if I have seen correctly on internet. There seems to be a smaller version of the vertical with a different name. Probably on test mode now. Perhaps all the new updates will be launched together with this new watch which I believe will replace the 9 peak series ?

Jonathan C

@seanvk I just got my Vertical recently and did a couple of runs. The first one was done using the default Running Basic profile which recorded my VO2Max, while the second using a custom Running profile as I want to tweak the data screens, but that time it didn’t record a value. I read in another thread that VO2Max is only supported with the default profiles—I wonder if you could try creating a custom profile to do those hikes so it doesn’t affect the Fitness Level?

seanvk

@Jonathan-Chu Thanks. Yes, I will probably have to create a custom outdoor activity and name it Hiking to avoid this issue.

Jonathan C

@seanvk why it behaves like this is beyond me. VO2Max separation and integration with specific sports NOT profiles has to be on the wishlist of updates.

Tieutieu

@Jonathan-C said in What do you expect from the next update?:

@seanvk I just got my Vertical recently and did a couple of runs. The first one was done using the default Running Basic profile which recorded my VO2Max, while the second using a custom Running profile as I want to tweak the data screens, but that time it didn’t record a value. I read in another thread that VO2Max is only supported with the default profiles—I wonder if you could try creating a custom profile to do those hikes so it doesn’t affect the Fitness Level?

I only use custom modes for trail running and running. Vo2 calculation works
To avoid vo2 calculation for hiking, so far you only have two options :

disable HR/OHR when using a walk/hike mode
using another sport mode where there is no vo2 calculation and change the type of sport after recording, in SA

Łukasz Szmigiel · S9PP 2.37.48

@Jonathan-C because, as we’ve recently learned, Suunto has no resources to focus on such subtleties when it’s busy racing its competitors

zhang965

Łukasz-Szmigiel said in What do you expect from the next update?:

Jonathan-C because, as we’ve recently learned, Suunto has no resources to focus on such subtleties when it’s busy racing its competitors

Racing! Must be with 16’40/km

jjpaz

@Jonathan-C I never use default running profiles and my Suunto Vertical shows Vo2 values after every training, isn’t that correct?

Egika

@jjpaz it is becoming a little off topic here.
Maybe open a separate thread for VO2max…
In short: it can be calculated in default and custom modes. Just the VO2max calculation requires some minimum data quality.
So if GPS or HR data is not of sufficient quality, VO2max is not calculated for an individual activity.

Jonathan C

@Tieutieu thanks—and my mistake. Just gave custom Running profile another try on what should be my cross training day (too impatient ) and this time VO2Max is calculated! It’s possible that I have to make sure the battery mode is Performance (somehow it defaults to Custom when creating a new profile) for this to happen… but glad it is working as intended.

Promise this will be my last comment on this subject here.

darxmurf

@Frederick-Rochette honestly, what I’m expecting from suunto is a better communication. There is clearly a serious issue with this watch and the “black screen of death” but they did not provide any information or confirmation about that. I opened a case at their support, asking for clarifications and the only answer I received is “if you have a problem with your watch, please contact your local dealer for support”.

Yes, it’s a complicated piece of hardware with a lot of dev and code running in there but when a serious bug is clearly identified, it would be more than welcome to inform customers and confirm the issue.

Honestly, the lack of communication from suunto is quite ridiculous.

Egika

@darxmurf said in What do you expect from the next update?:

@Frederick-Rochette honestly, what I’m expecting from suunto is a better communication. There is clearly a serious issue with this watch and the “black screen of death” but they did not provide any information or confirmation about that. I opened a case at their support, asking for clarifications and the only answer I received is “if you have a problem with your watch, please contact your local dealer for support”.

Yes, it’s a complicated piece of hardware with a lot of dev and code running in there but when a serious bug is clearly identified, it would be more than welcome to inform customers and confirm the issue.

Honestly, the lack of communication from suunto is quite ridiculous.

In which way would it help you if Suunto shared their service stats with you?
Like 0.02% watches back with button malfunction
1% watches experienced restart during activity
0.1% of watches have sealing issue at the glass connection
10% have barometric sensor failure

This is company internals and no comapny in the world shares those numbers.
They use it to improve product quality.
What you as an individual customer should expect a prompt handling of a possible service case.

BrunoH

@Egika I would like to support @darxmurf . Back when I had serious crashing problems with my S7 I did what they suggested and contacted my local dealer. My watch was sent to be serviced, but it came back with factory settings and unsurprisingly continued crashing. At this point I would expect the support to take responsibility of the problem escalation. Their communication was minimal at best and I had to take extra effort and literally demand support and service.

It was never about sharing statistics, but instead coming up with a solution for the customer with a bad device. If there is a SW bug causing problems, then they should come clean and say that it is a known problem and will be addressed in the next bugfix release in a few months. Playing dead won’t get the problem go away. Some info about a brighter future would be better than no info at all.

Egika

@BrunoH And I am fully with you here.
If an issue is not resolved with standard procedures, support should be high alert to ensure customer satisfaction.

Also fully agree with your other points about a good problem solving.

maybe I misunderstood @darxmurf

darxmurf

@Egika not about stats, but in our case, about this “black screen of death” users are facing with their Vertical. There is clearly something wrong here, maybe related with water as most of the time, the watch was in water before crashing or maybe about something else, who knows. When there is a serious issue like this with hundreds of peoples sending back their watch, it could be a good idea to inform a bit about the issue and give news to the community. I don’t know, maybe just say “yep it’s a water problem, avoid swimming with your watch until the next update”.

Or maybe I’m just over thinking about this problem and only a bunch of guys got this issue.

freeheeler

@darxmurf
I really can’t imagine what water would do to our waterproof watches.
I have some of them and none of them failed.
I surf, kite, bike, run, cycle, snowboard, skitour, sweat, swim, paddle and shower with all of them.
my personal opinion: it’s coincidence.