• Hi,

    I've been having some issues with my puck(s). Often, when I joined them to Bluetooth, they'll automatically go back to "Paired" rather than "Connected". Sometimes, when they connect, they don't appear as HID device either.

    Any ideas?

    Here's the snippet where I define the NRF services:

    var services = {
      0x180a: {
        0x2a50: {
          value:     [
            0x6d, 0x04,
            0x2b, 0xc5,
            0x00, 0x00
          readable:  true,
    var kb = require("ble_hid_keyboard");
    NRF.setServices(services, {
      advertise: [ 0x180a ],
      hid : kb.report


  • In Windows you'd expect that the device goes back to 'Paired' from 'Connected' if Windows doesn't find a reason to maintain a connection - which would be the case if it didn't think your device was a HID device.

    Just as a quick sanity check, what happens if you just do:

    var kb = require("ble_hid_keyboard");
    NRF.setServices(undefined, { hid : kb.report });

    without any of the other services?

    I might be that if windows sees the 180A device information service but it isn't in the format it expects, it just drops the connection...

  • Hm. That seems to be working consistently at that moment. I believe I switched to the format for defining services and whatnot because this method became flaky. I'll see what happens.


  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview

puck on windows "paired" but not "connected" (or connected but not HID)

Posted by Avatar for tako @tako