This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bluetooth not connecting

Hi,

1. I tried flashing all ble codes to my nrf kit. It does not seem to connect on Windows machine but connects on Mac. My other nrf kit connects perfectly fine. What is the fix?

2. When my other nrf device is visible on Mac, it displays duplicate names, so its confusing which one to connect to?

Parents
  • Hey, I ran into something similar a while back, one of my BLE modules would connect fine on macOS but refused to pair properly on Windows. In my case, it turned out to be a mix of driver and module compatibility issues. Windows tends to cache older Bluetooth profiles, which can cause confusion when the same device name shows up multiple times.

    You might want to clear your Bluetooth pairing history from Device Manager and re-pair the module after a restart. Also, make sure the COM port assigned to the BLE module isn’t conflicting with another device — that’s a surprisingly common cause of dropped or incomplete connections.

    If you’re using a generic BLE dev board, it might help to test with a simpler serial-based Bluetooth setup first, like an HC-05 Bluetooth Module. It connects over UART and behaves more predictably with both Windows and Mac since it uses standard serial-over-Bluetooth communication. That’ll help confirm whether the issue is in the host side (driver/OS) or with your BLE firmware.

    I’d also suggest checking if your module advertises as both BLE and classic Bluetooth simultaneously — some devices broadcast multiple profiles, which causes those duplicate entries you’re seeing on Mac.

Reply
  • Hey, I ran into something similar a while back, one of my BLE modules would connect fine on macOS but refused to pair properly on Windows. In my case, it turned out to be a mix of driver and module compatibility issues. Windows tends to cache older Bluetooth profiles, which can cause confusion when the same device name shows up multiple times.

    You might want to clear your Bluetooth pairing history from Device Manager and re-pair the module after a restart. Also, make sure the COM port assigned to the BLE module isn’t conflicting with another device — that’s a surprisingly common cause of dropped or incomplete connections.

    If you’re using a generic BLE dev board, it might help to test with a simpler serial-based Bluetooth setup first, like an HC-05 Bluetooth Module. It connects over UART and behaves more predictably with both Windows and Mac since it uses standard serial-over-Bluetooth communication. That’ll help confirm whether the issue is in the host side (driver/OS) or with your BLE firmware.

    I’d also suggest checking if your module advertises as both BLE and classic Bluetooth simultaneously — some devices broadcast multiple profiles, which causes those duplicate entries you’re seeing on Mac.

Children
No Data
Related