mirror of
https://github.com/MarekWo/mc-webui.git
synced 2026-07-03 16:31:28 +02:00
docs(ble): add pairing guide, remove unused MC_BLE_PIN config
MC_BLE_PIN was non-functional — bleak in Docker cannot perform interactive pairing (no BlueZ agent). Pairing must be done on the host before starting mc-webui. Added comprehensive pairing guide at docs/meshcore_bluetooth_pairing.md. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
+3
-6
@@ -20,14 +20,11 @@ MC_SERIAL_PORT=auto
|
||||
# MC_TCP_PORT=5555
|
||||
|
||||
# --- Option C: BLE (Bluetooth Low Energy companion devices) ---
|
||||
# Requires: USB BLE dongle on host, BlueZ installed, device pre-paired.
|
||||
# One-time setup on host:
|
||||
# bluetoothctl scan le (find your MeshCore device)
|
||||
# bluetoothctl pair <MAC> (enter PIN shown on device)
|
||||
# bluetoothctl trust <MAC>
|
||||
# Requires: USB BLE dongle on host, BlueZ installed.
|
||||
# The device MUST be paired and trusted on the host BEFORE starting mc-webui.
|
||||
# See docs/meshcore_bluetooth_pairing.md for detailed setup instructions.
|
||||
# When MC_BLE_ADDRESS is set, serial and TCP are ignored.
|
||||
# MC_BLE_ADDRESS=AA:BB:CC:DD:EE:FF
|
||||
# MC_BLE_PIN=123456
|
||||
|
||||
# Your MeshCore device name (used for .msgs file)
|
||||
# Use "auto" for automatic detection from device (recommended)
|
||||
|
||||
Reference in New Issue
Block a user