microbit-pxt-blehid

KO | EN

gitlite — search

#llm #go #android #machine-learning #rust #linux #docker #macos #java #awesome #cli #awesome-list #security #ios

microbit-pxt-blehid

(★ 50)

Micro:bit MakeCode support to act as a Human Interface Devices (keyboard, mouse, etc.) over Bluetooth

microbit-pxt-blehid 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# blehid

```package
blehid=github:bsiever/microbit-pxt-blehid
```

This extension allows the micro:bit V2 to act like a [Human Interface Devices](https://en.wikipedia.org/wiki/Human_interface_device) (HID) over Bluetooth.  It currently supports services for [Keyboard](#keyboard), [Mouse](#mouse), [Media Keys](#media-keys) (play, pause, volume up, etc.), a [Gamepad](#gamepad), and an [Absolute Mouse](#absolute-mouse) (puts the mouse at a specific position on the screen).

See [Cool Ideas and Challenges](#cool-ideas-and-challenges) for some examples of how this extension can be used.

Not all services are supported on all devices or operating systems. Operating systems with some support are:

* Android 11 and later (May work on some Android 9+ devices)
  * Tested on a Galaxy Tab A (8", 2019)
  * Here's an unofficial [Android BLE HID support list](https://github.com/raghavk92/Android_Bluetooth_HID_Device_Profile_CompatibilityList/blob/master/device_list.txt), which includes details on HID support for about 120 different Android devices.
* Windows 10 Pro and later
  * Tested on a Microsoft Surface Pro (5th Gen)
* iOS: Tested on 15.1
  * According to [Apple Support](https://support.apple.com/en-us/HT204387), the HID Profile is supported on "iPhone 5s and later, iPad Air and later, and iPod touch (6th generation) and later".
  * Tested on an iPhone 11 Pro
* macOS:  Tested on 11.4 (Big Sur)
  * Tested on an M1 Air, but it should work on any Mac made after 2014 running Big Sur or later

You are welcome to use the Extensions's discussions forum to share any new/different platforms that work or don't:
* [List of working devices](https://github.com/bsiever/microbit-pxt-blehid/discussions/21)
* [List of *NON*-working devices](https://github.com/bsiever/microbit-pxt-blehid/discussions/23)
* [All discussions](https://github.com/bsiever/microbit-pxt-blehid/discussions)

Not all features are supported on each operating system: <br />

| Service         | Windows  | macOS  | Android | iOS   |
|:---------------|:--------:|:------:|:--------:|:-----:|
| Keyboard       | X        | X      | X       | X      |
| Media          | X        | X      | X       |        |
| Mouse          | X        | X      | X       | Note 1 |
| Gamepad        | X        | X      | X       |        |
| Absolute Mouse | X        | X      |         | &nbsp; |

Note 1: iOS can support mouse control if [AssistiveTouch](#assistivetouch) is enabled.

# Pairing and Programming Quirks

Security is important for wireless Human Interface Devices, like keyboards.  The Micro:bit's Bluetooth communication goes through a process called "pairing" to ensure data exchanged is secure.  The pairing process works like this:

## 1. Program the micro:bit

Here's an example program:

```blocks
input.onButtonPressed(Button.A, function () {
    keyboard.sendString("Hello Bluetooth HID!")
})
keyboard.startKeyboardService()
```

Notice that it starts a service in the ```start```.

## 2. Have your device connect to the micro:bit

1. Open bluetooth preferences on the device you want to interact with (a computer, phone, or tablet),
2. select the micro:bit that you want to connect to (it will be named something like "uBit [XXXXX]"), and
3. your phone/computer/tablet may ask if you want to "Pair"  (Some devices, like Macs and PCs assume  you want to "Pair" because you selected the micro:bit).

Every time pairing happens a new "key" is created to encrypt all future communication.  The micro:bit and the other device will both store the key so they can immediately communicate in the future without going through this pairing process.  For example, if your micro:bit loses power and re-starts, the other device will automatically connect to it without going through the pairing process again.  However, sometimes changes to your program will cause the micro:bit's key to be destroyed! (See [Re-programming and keys](#re-programming-and-keys))

Here are examples of all three steps on each operating system:

### iOS Pairing

https://user-images.githubusercontent.com/1421446/149055788-594206e2-3ec7-477f-8c7f-28380c855a23.mp4

In the video the micro:bit's bluetooth name is "BBC micro:bit". Yours will be named something like "uBit [XXXXX]", where "XXXXX" will be the unique name of your micro:bit.
###  macOS Pairing

https://user-images.githubusercontent.com/1421446/149054357-aed2a475-ddfb-4786-8f2d-72e843a1811f.mp4