Title: LoRa BLE App Link Description: Pair the official Meshtastic app to GhostESP over BLE URL: /v2.2/lora/ble-app/ Version: v2.2 Section: LoRa (Meshtastic & MeshCore) Keywords: LoRa, Meshtastic, BLE, phone app, Ghost-XXXX, MTU Search index: /search-index.json # LoRa BLE App Link > Pair the official Meshtastic app to GhostESP over BLE ## On this page - [Advertising](#advertising) - [Pairing](#pairing) - [Text Flow](#text-flow) - [Drop and Link Semantics](#drop-and-link-semantics) - [Troubleshooting](#troubleshooting) --- GhostESP exposes the same BLE GATT service as stock Meshtastic nodes so the official app connects without mods. ## Advertising - Name: Ghost-XXXX where XXXX is the last two bytes of the node ID (hex). - Service: Meshtastic BLE service UUID; LongFast channel is the default (chash 0x08). - Start: lora ble on (or lora start if BLE bridge is set to auto). Check lora ble status. MeshCore runs its own companion service under meshcore ble on (Nordic-UART-style GATT); the two are mutually exclusive because one radio owns the SX1262. See [MeshCore Mode](/v2.2/lora/meshcore/). ## Pairing - Enable location/Bluetooth on your phone and open the official Meshtastic app. - Scan, then select Ghost-XXXX when it appears. - Wait for configuration sync to complete. The app should then show the LongFast channel, node list, and chat. ## Text Flow - App → mesh: type in the app; GhostESP encrypts as AES-CTR with the channel PSK and transmits via SX1262. - Mesh → app: received frames are forwarded once by packet ID. Reliable repeats are still acknowledged without creating duplicate messages. - Direct messages: DMs use the recipient’s NodeInfo public key. Public-channel access alone is not enough. - Other nodes see GhostESP as a regular peer (NodeInfo, routing, ACKs all interop). Messages received while the phone is disconnected are queued for the next connection. The pending queue depth is 8 (32 on PSRAM builds); the oldest packet is dropped when it fills. ## Drop and Link Semantics - Drop: app disconnect, BLE timeout, or lora ble off tears down GATT and clears the session nonce. Reconnect triggers fresh nonce reads. - Link: lora ble status reports linked vs advertising; lora companion ble keeps the bridge tied to BLE, while lora companion wifi keeps BLE free for scans. - Only one phone link at a time. A second connect preempts the first. ## Troubleshooting - Key unavailable: wait for NodeInfo, or run lora nodeinfo <node-id> and check lora pkinfo <node-id>. - Blank or old node name: chat packets do not carry names. Request NodeInfo and let the app sync again. - Message remains pending: reliable messages retry twice. LongFast retries are several seconds apart, so delivery is not immediate when an ACK is lost. - Connection has no data: wait for configuration sync, then check lora ble status and lora diag. See [Commands](/v2.2/lora/commands/) for transport switching.