Versa vs Pebble music control

[tigerxchaos]

I know this has been posted before, but I want to mention it again in case Fitbit development teams are paying attention.

I'm a Pebble transplant. I acknowledge that Pebble was nowhere near perfect, and overall I like my Versa. However, the implementation of music controls for music playing over your phone is *abysmal*. 

On Pebble, all you had to do was pair the watch once. Every communication, including music control, went through the single pairing connection, and did not interfere with the ability to control music by other Bluetooth devices such as speakers, headphones, car stereos, etc.

On Versa, inexplicably, you have to pair it a second time with the phone to get music control to work, and even then it only works if it's the first device connected with the ability to control music. So you have to start playback on your phone with the Versa connected first, and only then can you connect your speakers or headphones. After doing so, the speakers/headphones cannot control playback.

This is an absolutely bizarre design decision. It's cumbersome at best, hostile at worst.

Does anyone know if there are plans for improving the usability of this feature? 

Moderator edit: updated subject for clarity

[LucyAP]

Welcome to the Forums @tigerxchaos! Thanks for sharing your feedback about your Versa and the Music Control feature. 

As you mentioned  Bluetooth can get interference. Android and Win 10 devices require using a separate Bluetooth classic connection in order to use Music control but with iOS devices, they use the same BLE connection that is used for syncing and notifications. 

Also, you can add your suggestion and make your voice heard in the Feature Suggestions board. There you can create or upvote for a suggestion to support music control over BLE with Versa. The ideas with more vote are taken into consideration by our developers for nest updates or product development. 

Catch you later! 🙂