summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJonathan Rascher <jon@bcat.name>2020-11-15 20:04:27 -0600
committerPete Johanson <peter@peterjohanson.com>2021-02-04 07:45:55 -0500
commit1368a6481e591d6c19ac9f54f44916373d1897d2 (patch)
tree3e48bcceb3de5fac342abfaff2d98cfe91d71c11 /docs
parent11d990e59a55bf1e834c12cae4542e1ab6af4f20 (diff)
docs: Explain ZMK stays connected to inactive host
This behavior was not obvious to me, and I actually considered reporting it as a bug until @Nicell explained to me on Discord that it's WAI. :)
Diffstat (limited to 'docs')
-rw-r--r--docs/docs/behaviors/bluetooth.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/docs/behaviors/bluetooth.md b/docs/docs/behaviors/bluetooth.md
index f2d1b2f..5a5ad19 100644
--- a/docs/docs/behaviors/bluetooth.md
+++ b/docs/docs/behaviors/bluetooth.md
@@ -13,6 +13,10 @@ computer/laptop/keyboard should receive the keyboard input; many of the commands
Please note there are only five available Bluetooth profiles by default. If you need to increase the number of available profiles you can set `CONFIG_BT_MAX_CONN` in your `zmk-config` `.conf` file.
:::
+:::note Connection Management
+As an implementation detail, a ZMK device may show as "connected" on multiple hosts at the same time. This is working as intended, and only the host associated with the active profile will receive keystrokes.
+:::
+
## Bluetooth Command Defines
Bluetooth command defines are provided through the [`dt-bindings/zmk/bt.h`](https://github.com/zmkfirmware/zmk/blob/main/app/include/dt-bindings/zmk/bt.h) header,