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.
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.
I have now received an official reply from Polar Support regarding my case.
According to Polar, starting with firmware 3.0.15, the Verity Sense was modified to comply with the EU Radio Equipment Directive (RED). Because of this change, the sensor now requires the receiving device to handle a new Bluetooth pairing procedure.
Polar also states that not all receiving devices correctly handle this new pairing process, which may result in unstable connections or the sensor not working as expected.
However, after extensive testing, I believe there is more to the issue:
I tested the Verity Sense on two different Windows 11 PCs.
I tested with different Bluetooth adapters.
I performed a factory reset and paired the sensor again.
I created a Bluetooth Low Energy diagnostic tool that confirms Windows detects and connects to the Verity Sense, but it receives zero heart-rate data.
I have another Polar sensor with older firmware that works perfectly on the same PCs with the same Zwift installation.
This strongly suggests that the problem appeared after the new Verity Sense firmware and is related to the new Bluetooth pairing implementation.
If Polar is correct, this means Zwift and/or Windows may need to update their Bluetooth implementation to fully support the new RED pairing process. On the other hand, if many users are affected after the firmware update, Polar may also need to improve compatibility.
Has anyone else received a similar response from Polar or experienced the same issue after updating to firmware 3.0.15 or 3.0.16?
Thanks, Mike. I already tested it without pairing the Verity Sense manually in Windows.
I removed the sensor completely from Windows Bluetooth settings, closed Polar Flow, switched off Bluetooth on my phone, restarted the sensor, and then opened Zwift.
Zwift finds the Polar Sense and starts connecting, but during that process Windows automatically displays a pairing request. If I close or reject that request, Zwift remains disconnected or shows “No Signal.” If I accept it, Zwift briefly connects to the sensor but still receives no heart-rate data.
I have also confirmed with a separate Windows BLE diagnostic that the sensor is detected with a strong signal and the connection is established, but the standard Heart Rate Measurement characteristic sends zero readings and the connection usually drops after approximately 19–20 seconds.
The same computer and Zwift installation work correctly with another Polar sensor that has not been updated to firmware 3.0.16.
Paired the Polar Verity Sense in Windows 11 first.
Connected it in Zwift afterwards.
Factory reset the sensor.
Tested on two different Windows 11 PCs with different Bluetooth adapters.
Disabled Bluetooth on my phone during testing.
The result is always the same:
Windows detects and connects to the sensor.
Zwift detects the Verity Sense.
No heart rate data is ever transmitted.
I also captured BLE diagnostic logs showing that the sensor connects successfully but never sends heart rate measurements.
As a comparison, another Polar heart rate sensor with an older firmware works correctly on the same PC, with the same Bluetooth adapter and the same Zwift version.
Polar has now escalated my support case to their technical department for investigation.
Has anyone else with Verity Sense firmware 3.0.16 experienced the same behavior on Windows 11?
I realize this might seem counter-intuitive but have you tested it with and without dual BLE connections enabled on the device? You should find that as a setting in Polar’s app.
Hi Paul,
I’ve now completed the ANT+ comparison test you suggested.
Using the same PC, the same Zwift installation and the same ANT+ USB dongle:
Polar H10: Zwift detected it as HR Strap 20825 via ANT+, and it successfully displayed heart-rate data (59 bpm during the test).
Polar Verity Sense: I then closed Zwift, removed/turned off the H10, switched to the Verity Sense, reopened Zwift and repeated exactly the same search. The Verity Sense does not appear at all in the ANT+ heart-rate device list, even after waiting and searching under “All”.
So the H10 test confirms that the ANT+ dongle, USB connection and Zwift ANT+ reception are working correctly. The only variable changed was the heart-rate sensor.
This is also consistent with the BLE diagnostics I previously performed on Windows: Windows can detect and connect to the Verity Sense, including its GATT heart-rate service, but we receive zero heart-rate measurements.
Thanks for suggesting this test — I think this gives us a very useful comparison.
Hi Paul,
I repeated the ANT+ test under controlled conditions.
I completely disabled Bluetooth on both my phone and my Windows PC, so there were no Polar devices connected via Bluetooth. I also closed Polar Flow and made sure nothing else could connect to the Verity Sense.
Then I opened Zwift with only the ANT+ USB dongle active and tested the Polar Verity Sense. In Zwift I went to Heart Rate → Search → All and left it searching for more than one minute. The Verity Sense never appeared — Zwift continuously showed “Searching for devices…”.
As a control test, using exactly the same PC, Zwift installation and ANT+ dongle, the Polar H10 was immediately detected as HR Strap 20825 and transmitted heart-rate data correctly.
So the ANT+ receiver and Zwift ANT+ connection are definitely working. The difference is the Verity Sense: it is not being detected over ANT+ at all.
I also have photos/screenshots of both tests, including the Verity Sense search running for more than one minute with no device detected.
Thanks again for your help, Paul.
Esta respuesta deja la prueba mucho más cerrada: Bluetooth del móvil apagado + Bluetooth del PC apagado + Polar Flow cerrado + mismo dongle ANT+ + H10 funciona + Verity Sense no aparece
Yes. I turned OFF the “2 Bluetooth devices” setting in the Polar Flow app before the test.
I also completely disabled Bluetooth on both my phone and my Windows PC, so there were no Bluetooth connections that could interfere with the test.
Then I tested the Verity Sense in Zwift using ANT+ only. I went to Heart Rate → All and left Zwift searching for more than 1 minute. The Verity Sense never appeared.
For comparison, using exactly the same PC, Zwift installation and ANT+ dongle, my Polar H10 is detected immediately via ANT+ as “HR Strap 20825” and transmits heart-rate data correctly.
The ANT+ protocol does not support encryption at all (it’s one of the reasons why the ANT+ group at Garmin shut down last year). So it’s puzzling that it would not work with ANT+. That sounds buggy to me. It should always work with ANT+ even if encrypted Bluetooth communication is blocked for some reason.
Thanks Paul. That’s exactly what makes this so puzzling.
Since ANT+ is not encrypted, I agree that the Verity Sense should still appear and transmit heart-rate data over ANT+ regardless of any secure BLE changes.
The comparison seems quite conclusive:
Same Windows 11 PC
Same Zwift installation
Same ANT+ USB dongle
Polar H10 → detected immediately and transmitting HR
Polar Verity Sense → not detected at all via ANT+
Bluetooth was disabled on both the PC and phone during the ANT+ test, and “2 Bluetooth devices” was turned off in Polar Flow.
So at this point it does look like something may be wrong on the Verity Sense side, possibly related to firmware 3.0.16.
I found another report that may be very relevant to this issue.
There is a bug report in Polar’s official GitHub repository describing a problem with the Polar Verity Sense on Windows 11 after updating to firmware 3.0.16.
The report states that the problem did not exist before the firmware update and was reproduced with TPVirtual and MyWhoosh.
This is particularly interesting because both of my Verity Sense units also stopped working correctly after being updated to firmware 3.0.16, while my Polar H10 works correctly on the same Windows 11 PC.
This suggests that the issue may not be specific to Zwift.
Polar GitHub report: https://github.com/polarofficial/polar-ble-sdk/issues/827
I have now found a workaround that makes my Polar Verity Sense firmware 3.0.16 work correctly with Zwift on Windows 11.
Before the workaround:
Zwift detected the Verity Sense over Bluetooth.
It showed “Connected”, but heart rate stayed at 0 bpm or changed to “No signal”.
In one test, Zwift briefly showed 56 bpm for about one second, then lost the HR signal again.
I confirmed that the sensor itself was working correctly:
Polar Flow on my phone received HR normally (around 52–53 bpm).
The Web Bluetooth Heart Rate Sensor demo in Chrome on the SAME Windows 11 PC also received 53 bpm correctly.
Updating the Intel AX211 Bluetooth driver did not solve the Zwift issue.
The workaround that worked:
Close Zwift completely.
Turn Bluetooth OFF on the phone.
Turn on the Polar Verity Sense.
In Windows 11 go to:
Settings → Bluetooth & devices → Add device → Bluetooth.
Pair “Polar Sense 1F689B3B” directly with Windows first.
Only AFTER Windows has paired the Verity Sense, open Zwift.
In Zwift, select the Verity Sense as the heart-rate monitor.
Result:
Zwift then received HR normally and continuously: 51 bpm, then 49–50 bpm, without dropping to “No signal”.
So on my Windows 11 system, pairing the Verity Sense with Windows first appears to be necessary before Zwift can maintain the heart-rate connection with firmware 3.0.16.
This may be related to the secure Bluetooth changes introduced in the recent Polar firmware.
Update from Polar – Verity Sense 3.0.16 / Zwift / Windows 11
I have now received a new reply from Polar regarding the Verity Sense issue with firmware 3.0.16 and Zwift on Windows 11.
After sending them the full results of my testing and the workaround that finally made the Verity Sense work correctly, Polar confirmed that their headquarters have received the information and thanked me for documenting the procedure.
The working procedure in my case is:
Close Zwift completely.
Turn off Bluetooth on the phone.
Turn on the Polar Verity Sense.
In Windows 11, go to Settings > Bluetooth & devices > Add device > Bluetooth.
Pair the “Polar Sense” directly with Windows first.
Only after the Windows pairing is completed, open Zwift.
Select the Verity Sense as the heart rate monitor in Zwift.
Using this sequence, the heart rate is now received correctly and remains stable in Zwift.
The most interesting part of Polar’s latest reply is that they say they are now investigating whether they can make changes “through the sensor” to make the pairing process easier and to improve the stability/maintenance of the connection.
So at this stage, Polar appears to be actively investigating the behaviour introduced with the newer firmware and the Bluetooth pairing process.
They have not confirmed yet whether this will result in a new firmware update, but I have asked them to keep the case open and to inform me if they release a firmware change, an official workaround, or any other solution.
I will update this thread again as soon as Polar provides more technical information.
I have the same issue, but I’m not able to add the device through windows 11 BT; I never see the device even though I turned of BT on my phone, shut down my Garmin Enduro 3.
When I start zwift and try to connect the sensor in there I get the connection issues as described above and only then I’m getting a windows notification about the sensor trying to connect every 30 sec or so, but connecting from there doesn’t work.
When I shut down Zwift and go to windows settings; device will not show up.
Thanks for your reply. I experienced very similar Bluetooth connection issues with my Polar Verity Sense after updating to firmware 3.0.16.
In my case, I managed to get it working by completely closing Zwift, disabling Bluetooth on my phone, and pairing the Polar Sense directly through Windows 11 Bluetooth settings before opening Zwift.
I understand that Windows 11 is not detecting your sensor, even with Zwift closed.
Could you please confirm two things?
Is your Verity Sense running firmware 3.0.16?
Has your Verity Sense ever successfully paired directly with Windows 11, or has Windows never detected it?
The fact that your sensor works correctly over ANT+ and with your Garmin and phone is particularly interesting.
Polar previously confirmed to me that firmware 3.0.15 introduced a new secure Bluetooth pairing process related to the EU RED requirements. I suspect this may be related, although we cannot confirm it yet.
Please let me know. I’d be happy to help you troubleshoot this further.
I only bought the sensor a month ago, and tried to use it for the first time with Swift last week for the first time (on PC).
So no, never connected before. Windows does not detect it, only when I start Zwift windows will show the popup about a new device (but linking from there doesn’t actually link it)
(Also tried it with MyWhoosh on a W10 laptop, but it’s the same)
Hi StefKe,
Thanks for the additional information.
Your situation is very similar to the problems I experienced with my Polar Verity Sense running firmware 3.0.16, although there is one important difference.
In my case, Windows 11 detected the sensor, and Zwift showed it as connected, but the heart rate remained at 0 bpm or stopped updating.
After extensive testing with different computers, Bluetooth adapters and ANT+ connections, I eventually found a working solution by pairing the sensor directly with Windows before launching Zwift.
However, since Windows does not detect your sensor at all, I would suggest checking the following:
Check your Polar Flow settings
Open Polar Flow and verify that:
“Heart rate visible to all” is enabled.
“2 Bluetooth devices” is enabled.
Both settings are important for Bluetooth connectivity.
Completely isolate the sensor
Close Zwift and MyWhoosh.
Disable Bluetooth on your smartphone.
Turn off your Garmin Enduro 3 temporarily.
Restart your Polar Verity Sense in heart rate transmission mode.
Change Bluetooth discovery settings in Windows 11
Go to:
Settings → Bluetooth & devices → Devices
Look for “Bluetooth devices discovery” and change it from “Default” to “Advanced”, if that option is available.
Then try adding the Polar Verity Sense directly through Windows Bluetooth settings, without opening Zwift.
If Windows successfully pairs with the sensor, launch Zwift afterwards and connect it as your heart rate monitor.
If Windows still cannot detect it
I would recommend checking the Bluetooth adapter model and driver version.
A factory reset through Polar Flow could also be worth testing if you have not already done so. Be aware that this clears stored sensor data.
My observations
The fact that your sensor works correctly through ANT+ and with your Garmin suggests that its heart rate measurement and transmission functions are operational.
Since you experience Bluetooth problems with both Zwift on Windows 11 and MyWhoosh on Windows 10, I suspect a Bluetooth discovery or pairing issue rather than a problem limited to Zwift itself.
Firmware 3.0.16 could be involved, but we do not yet have enough evidence to confirm that.
Could you tell us which Bluetooth adapter you are using on your Windows 11 computer?
Also, please let us know whether enabling Advanced Bluetooth discovery makes any difference.
I would be very interested in your results, as we may be dealing with another variation of the same firmware-related connectivity issue.
Best regards,
Jordi Riu Popito