iPhone 11 - Siri not working with bluetooth helmet

There's a possibility that the helmet is not compatible with the iPhone 11 series or possibly iOS 13. You'll want to check with them to see if there's a firmware update. Also, you could try completely forgetting the helmet in your Bluetooth settings on the phone and setting it up as a new device.

I'm so happy to see other users are having this issue. It bugged me so badly months ago but there was no info online. Heres what i did that seemed to work

1. Unpair your headset
2. Hard reboot the phone (volume up, volume down, hole power button till the phone reboots on its own, don't use the slider)
3. pair your helmet again

From what I can tell the issue has something to do with applying an iOS update so you need to re-pair your bluetooth devices afterwards to ensure functionality.

Same issue here and glad to see I'm not the only. Currently running iOS 13.3.1 on an iPhone 8

Issue is that Siri either:

1. Goes through the process of "One moment", "Just a sec" then "I'm having problems with the connection"
2. Activates then immediately turns off

This is happening both in with my Sena SMH10 and in my car.

I have the absolutely exact same problem, except I'm using a Cardo Freecom 2 unit.

I've being using iOS 13 beta versions and I expected they would fix it for public release, but no, problem persists.

I'm in touch with headset's manufacturer in hope for some new firmware release to fix the problem.

Even really odd, I'll try this shutdown later today, hope it works for me too!!

I was having the same problem with Siri through my Freecom 4+ after upgrading to the release version of iOS 13 (including 13.1.2) on my iPhone X. After I said "Hey Siri", I received the acknowledgment tone. I then issued the command and after a lengthy pause she replied with an error message saying there was a problem with the connection and to try again later. Siri worked fine when the command was issued directly to the iPhone rather than through the Freecom mic inside my helmet. I used the Settings -> General -> Shutdown suggestion above and this fixed the problem.

Interesting. I'm using a Cardo rather than a Sena so it does seem to be an iOS bug. Mine is still worjking fine since I did the reset. In fact, Siri's response is noticably faster. Whenever I ask her to close the garage door as I ride away, the command is executed within 1-2 seconds whereas it used to take up to 10 seconds.

I'm getting this problem too with a Sena 10C after I upgraded my iPhone X to iOS 13. It all worked perfectly before upgrading. I've removed the device from the phone and re-added it and also upgraded the firmware on the Sena 10C to the latest version which is compatible with iOS 13. I needed to do this firmware upgrade in order for the Sena software to recognise the 10C headset from iOS13.

I had same problem with Cardo responding correctly to “Hey Siri” but Siri not responding. Was fixed by Resetting Network Settings on IPhone (XR). But does anybody else have problems with the microphone hearing the Cardo correctly, but not Siri correctly above 10 or 15 mph? Full face helmet, using the microphone that Velcro’s to the front inside part of the helmet. Very frustrating.

I am not having that ssue. I have used Hey Siri and Hey Cardo commands at over 100km/h (60mph) without any issues. I do find that I have to speak at a normal level. If I shout or speak loudly it only sometimes works. If I speak in a normal voice, no problems. It might be worth experimenting with rhe "VOX Sensitivity" setting on the Cardo Community page. I have mine set to Medium (default).

Can confirm that this problem is recurring. Siri will periodically report "problem with the connection. Please try again later". iPhone needs to be rebooted to sort out the issue but after a while, it happens again. This does seem to be an iOS bug.

Thanks for the replies. This issue was driving me crazy and glad the community use this forum to help each other. Thanks again :)

P.S. As I ride away, the command is executed quicker as well as adding an extra couple horsepower :D haha

It's a shame that this answer is listed as "apple recommend" here. It's incorrect and hides the answers that provide a workaround for this bug later in the thread. If you have the ability to remove your comment, it would be helpful. This appears to be the only place where people have shared their solution. I started having this problem witha helmet-based bluetooth unit shortly (not immediately) after upgrading to iOS 13. It's odd, and it's clearly an iOS bug, and it's extremely frustrating when it happens to you.