No voice que when runni g

[PWF5]

I set my blaze up to get stats every .5 miles while running and I hear no voice why?

[SunsetRunner]

Same problem here. If I start in the app and track a run I get music and audio cues. If I start from the watch I have to start music myself and get no audio cues.

[SunsetRunner]

Same here!!

[beejay1177]

Agreed that the documentation notes read as voice Run Cues - this was something that could be done through the Fitbit app previously and worked perfectly with my Charge HR and using Spotify.  I feel that this is a key item lacking at the moment in my Blaze experience, as running is the core reason I use my Blaze for!

[Rich_Laue]

Actually it doesn't work wroth the Charge HR through the app. It is the App, not the Charge HR that is tracking the miles,  amd producing the voice cues.

When using connected GPS the Blaze, and not the App, is doing the tracking. The Blaze does not have a Voice Chip, speaker, or is able to connect to headphones.

The Blaze, like the Surge will vibrate amd display a summery on their screen

[beejay1177]

Hi Rich_Laue

Yes I do understand about the Blaze's ability to not project the sound as I am a long-time Fitbit user.  It does not take aside the fact that many people want the ability to be able to hear voice cues through their headphones.  As a runner that was using the Charge HR via the Fitbit app to connect to Strava and was excited to be finally able to start and stop my runs on my wrist with the Blaze, it is disappointing that a key functionality I want in a running accessory is not available unless I go back to having to start and stop my runs by going into my phone app.

I'm sure this is where the others who are posting's frustrations are coming from.  We understand that the Blaze itself doesn't produce the sound, but when you are running 1km intervals for example, you want to be able to hear when to stop and the vibration for the lap function often doesnt work effectively so I am constantly needing to look down on my watch face to track. 

[SunsetRunner]

Thank you @beejay1177. This was my exact gripe with the Blaze.

[ajea]

Wait!! You mean that I have to choose between getting voice queues or having all the stats for the current run on my watch? If that is the case Blaze is totally worthless as a runners watch. I will do my first run this weekend and if this is correct I won't keep quiet about it, there will be blood 😩

[Rich_Laue]

@ ajea having voice cues versus cues on the watch is really a personal decision. 

This is where doing some research before buying can be beneficial.

[Muuurgh]

@Rich_Laue it is a personal decision what cues we would like. The fact we don't have a choice is the problem, and that is purely a software decision by fitbit.

I would think it's a reasonable assumption, that since you have to have your phone with you to track runs on the blaze, that they would use the same notification settings and cues! If anything, the blaze should add to the fitbit experience by providing easier access to stats on the wrist.

I'm sure it'll be fixed in a future update, it's very frustrating right now though!

[MikeF]

I'd be surprised. The whole point of the Connected GPS is that the Blaze is doing the distance tracking, not the phone so I doubt it has any clue what's going on. Sure, the Blaze and app software could be re-written to work that way but the same could be said for the Surge and probably the non-GPS trackers too. I think it would have happened already if it were going to.

No doubt we'll find out in due course.

[SunsetRunner]

Seems that since the blaze and app are communicating the GPS feed they could also layer in audio cues through the phone .. Would be a good addition.