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

Minimal requirements for HID

Hi,

I've been trying to add the option for BLE HID to the Espruino JS interpreter on nRF52 - it's something that ideally would be switchable at runtime.

After having had something mostly working with SDK11, the removal of device_manager meant quite a lot changed and to avoid it getting even more messy than it currently is it's been worth starting again from scratch.

After just adding BLE HID, without a device/peer manager, Android refuses to find the device to pair.

What is the bare minimum that is needed to get a HID device working? For example, is the peer manager absolutely required? What about whitelisting? What about the battery service?

The hids_keyboard example is relatively complicated, and I'm wondering if that's all really needed.

thanks!

Parents
  • Well, at the moment there is no pairing/bonding implemented - it's just a device that you can connect to, so ideally I'd have it working just like that for the moment. Yes, I try and connect via Android Bluetooth settings, but it doesn't show up under 'Available Devices' (but it does via nRF Connect on the save device). I guess Android might require that there is some security in the link?

Reply
  • Well, at the moment there is no pairing/bonding implemented - it's just a device that you can connect to, so ideally I'd have it working just like that for the moment. Yes, I try and connect via Android Bluetooth settings, but it doesn't show up under 'Available Devices' (but it does via nRF Connect on the save device). I guess Android might require that there is some security in the link?

Children
No Data
Related