Audio prompt for Speed/pace always gives pace

ianmiles Thank you for starting this thread. I have opened a ticket on this. If you or anyone else experiencing this issue would like to be added to the ticket, please send me a direct message with: 

• App version 
• Edge software version 
• Country you are located

Thanks!

-Maeve

I've finally got round to testing this - it's not a function I normally use. I'm getting the same results - pace is reported, despite using an Edge 1040 with a profile that's clearly intended for cycling. I suspect the issue is with Connect rather than with the edge. 

Edge 1040 c.19.22, iOS Connect 4.74.1.3, UK. PM'ed Garmin-Maeve.

Same here.  It happened a few months back.  I do not know if it is a Connect issue or a 1040 issue since I no way of going back to older versions of the software.  I used to get the report in miles/hour or km/hour. Now I get a pace.  It would be great to get a setting to select how we want it reported.  It's been broken even though the 1040 and Connect have been updated multiple times since pace took over.

I have this issue too. My device was replaced for other reasons but soon after receiving it the audio prompt says Current Pace rather then Current Speed. I have an Edge 830 registered to the same Connect app on my phone and the prompt from this device says Current Speed. Since my 1040 has now gone dead and will not charge I am going to have to see if Garmin will replace it again. Hopefully the pace issue will soon be resolved.

I have received my replacement device and set it up from new. From new it had version 17.29 software fitted. I set it up with Connect and enabled the current speed alert on a repeating 1 minute cycle. The announcement was correct stating the current speed. As the device had outdated software I then updated to version 19.22 as prompted and the alert changed to current pace. It would seem that there may be a firmware bug but don't understand why more users are not reporting this issue. It's really annoying and I wish I could find a fix.

It certainly seems like a bug that's been introduced in one of the recent Edge 1040 updates. I think the reason it's not reported much is almost certainly that the feature isn't widely used. I wouldn't normally use it, but started doing so in response to this thread. (Obviously, the defect is still there for me, too.)

Thanks for this. Your experience would seem to confirm that the issue lies with the 1040 firmware and not Garmin Connect Mobile, and further narrows it to an update between 17.29 and 19.22. Those of us who updated firmware as each new version became available have been unable to specify when the bug was introduced so this is new and valuable information.

I just finished a ride using my Fenix 6 and Edge 1040. The Fenix  behaved properly and reported the average speed in miles per hour. The Edge gave the average as minutes and seconds

I haven't had much luck with the Edge 1040. I am now on my third device. I know that the problem with the pace alert occurred just after my previous replacement on the 6th November 2023, so the update that became available on or around then is the culprit. I can't seem to find a list of updates and release dates.