Hello,
I am experiencing a connection issue with my Polar Verity Sense after updating to the latest firmware.
Firmware version: 3.0.16
My setup:
- Windows 11 PC
- Zwift using native Bluetooth
- Polar Verity Sense
- Dual Bluetooth connection enabled
- Polar Flow closed
- Phone Bluetooth switched off
I followed the recommended procedure:
- Closed Zwift.
- Removed and paired the Verity Sense again in Windows Bluetooth settings.
- Accepted the Windows pairing request.
- Started Zwift and selected the Verity Sense as the heart-rate monitor.
Zwift detects and connects to the sensor, but it never receives any heart-rate data and eventually shows “No Signal.”
To investigate further, I ran an independent Bluetooth Low Energy (BLE) diagnostic directly in Windows. The results were:
- The sensor is consistently detected as Polar Sense 1F689B3B.
- Bluetooth signal is strong (approximately -52 to -56 dBm).
- Windows connects successfully.
- The standard Heart Rate Measurement characteristic is detected.
- Zero heart-rate measurements are ever received.
- Connections typically last around 19–20 seconds before disconnecting.
- The diagnostic repeatedly reports no heart-rate data received.
I also own another Polar heart-rate sensor with older firmware. It works perfectly with the same Windows PC and the same Zwift installation. This makes me believe the problem may be related to the latest Verity Sense firmware and its Bluetooth implementation rather than my computer or Bluetooth adapter.
I have already opened a support case with Polar.
Unfortunately, I have also discovered that emails sent to Polar’s info support address are returned as undeliverable, so I am currently waiting for an official response through their support system.
Download the BLE diagnostic CSV log
The Verity Sense works correctly in the Polar mobile app and continuously displays heart-rate values, so the optical sensor itself is functioning.
If Zwift or Polar developers need any additional information or would like me to perform further tests, I will be happy to help.
I can also provide the detailed V2 diagnostic log, which confirms that the Heart Rate Service (0x180D) and Heart Rate Measurement characteristic (0x2A37) are present and notifications are enabled, but no heart-rate values are transmitted.