deleted deleted

deleted deleted   •   about 6 years ago

Pairing V.ALERT with a Windows PC?

Where can I find specific instructions on pairing the V.ALRT with a
PC? When I put my PC in Bluetooth device discovery mode, the V.ALRT
button flashes green slowly, but I don't see it appear in the
discovered device list on the PC. I tried holding down the button for
10-24 seconds as the doc you sent me instructs, but I still don't see
it in the list. Note, when I held the button down for 10-24 seconds
at the very end I heard 3 slow beeps followed by 2 fast ones. Note,
my phone could not find the device either when it was scanning for BT

My PC is running Windows 8.1 and I am using a Belkin Bluetooth dongle.
I know Bluetooth works because if finds my Windows Phone properly.



  • Manager   •   about 6 years ago

    Hello Robert.
    A few things:

    1) About the V.ALRT: To place the V.ALRT button in advertising mode, press the button for 10-20 seconds. (Do not press it too long...If you hear the 3 slow beeps followed by the 2 fast beeps, the button is in stand-by-mode, meaning you pressed it too long. Just do it again for less than 24 seconds, all you really need is 10 seconds ). When in advertising it should blink once every 10 seconds green.

    2) For the PC to find the V.ALRT the PC must support Bluetooth 4.0. So if the Belkin dongle is BT3.0 or below it will not find the button. V.ALRT uses the latest low-energy BT4.0 technology. Many newer PCs have BT4.0 already and may not need a dongle.

    3) You will need to write and application that interfaces with the V.ALRT BT profiles defined in the developer guide.

    Please do not hesitate to ask more questions if something is not clear!

  • Manager   •   about 6 years ago

    After you connect with the device, you must write to the following characteristic:
    the following value:

    -----from the developer guide:
    e. V.BTTN Verification (UUID: 0xfffffff5-00f7-4000-b000-000000000000)
    The V.BTTN Verification Characteristic enables apps to communicate with V.BTTN. Verification key value is BC:F5:AC:48:40. Refer to section 5, Connecting to V.BTTN for details requirements for connecting to V.BTTN

    Let us know if this is not clear.

  • Manager   •   about 6 years ago

    Any time.
    Keep in mind that the regular sequence that we have seen on Android and iOS development is, that, first you scan for devices, then you connect to the desired device, then you do a "service discovery" which prompts the device to send back the supported services and characteristics, and after that you can typically communicate with the device, such as writing the app verification key etc.
    I guess what I mean to say is to write the app verification after service discovery (this has been our experience).

    Good luck

  • Manager   •   about 6 years ago

    Sorry roschler for the delayed response. so many things, so little time!

    Unfortunately we have not developed a Windows BLE app internally. I suggest to start with a sample BLE app that does some of the basic connection logic to a BLE device...since our device is pretty standard in that regards.

    I did some searching, and apparently BLE on windows RT seems a little, awkward to say the least. Have you tried the Developer Accelerator program from SIG...they seem to have sample windows BLE app. I have not confirmed this information, but it is worth a try. Take a look, and I will continue to search for other information that may help you.

    Please report back on your findings!

Comments are closed.