Yesterday I was trying to connect my V3s to Zwift which I use on an iPad so I have to use Bluetooth rather than ANT (I know I can take the power reading from my trainer, but I've always preferred to take it straight from my power meter). However, I couldn't get Zwift to 'see' my V3s. Then it occurred to me that the V3s are designed to be paired with GCM when you set them up (as GCM is used for updates and monitoring battery level etc) so I checked my iPhone and the V3s were showing an active BT connection with it - and as BLE doesn't support simultaneous connections, this explained why Zwift/my iPad wasn't seeing them. I tried disconnecting the active connection on my iPhone, but straight away, the V3s requested it again. After a few more attempts, I killed BT on my phone but still nothing. I then left the pedals for 30 minutes to allow them to go to sleep, then woke them up and tried again (with BT still 'off' on the phone), but still nothing in Zwift. As soon as I turned BT back on on my phone, the V3s connected themselves back to GCM.
So, how is this meant to work? It would seem that the V3s are designed to establish a permanent (whilst on) BLE connection with GCM, but how then can the BLE output be used by anything else? And why even when I forced the phone to disconnect did Zwift still not see the V3s? Are the pedals still prioritising making a connection to a phone they can't find, or is there simply a bug preventing Zwift from seeing them?
A workaround would possibly be to remove the V3s from GCM and the list of paired devices on the phone once initial setup is complete, but this would seem to be working around the way they're actually meant to be used (i.e. with the permanent GCM connection), but I don't see how this can be achieved without committing the BLE signal.
