The Mentra Bluetooth SDK exposes the same core glasses lifecycle across Android, iOS, and React Native:
  • Scan for a supported glasses model.
  • Connect to a discovered Device or an app-restored default device.
  • Read typed lifecycle state through the public surface for your platform.
  • Subscribe to typed hardware events.
  • Send display, camera, stream, audio, Wi-Fi, hotspot, LED, and settings commands where supported by the connected model.

Packages And Imports

PlatformInstall packageImport
Androidcom.mentra:bluetooth-sdkimport com.mentra.bluetoothsdk.*
iOSMentraBluetoothSDK CocoaPodimport MentraBluetoothSDK
React Native / Expo@mentra/bluetooth-sdkimport BluetoothSdk, {DeviceModels} from '@mentra/bluetooth-sdk'
React Native hooks@mentra/bluetooth-sdkimport {useMentraBluetooth} from '@mentra/bluetooth-sdk/react'
Only documented imports are part of the supported app developer API. Undocumented package subpaths or symbols with a leading underscore can change without notice.

Lifecycle

import {useBluetoothEvent, useMentraBluetooth} from '@mentra/bluetooth-sdk/react';

function DeviceScreen() {
  const mentra = useMentraBluetooth();
  useBluetoothEvent('button_press', (event) => {
    console.log(event.buttonId, event.pressType);
  });

  console.log(mentra.glasses.connection.state);
}
Keep one SDK instance per active app session. The SDK owns Bluetooth connection state, native event delivery, and cleanup. Your app owns user identity, UI state, and whether a default device record is persisted across app restarts.

Connection

const devices = await BluetoothSdk.scan(DeviceModels.MentraLive, {
  timeoutMs: 10_000,
  onResults: (nextDevices) => renderDevicePicker(nextDevices),
});

const device = await chooseDevice(devices);
await BluetoothSdk.connect(device, {saveAsDefault: false});

await BluetoothSdk.setDefaultDevice(device);

const defaultDevice = await BluetoothSdk.getDefaultDevice();
await BluetoothSdk.connectDefault();
await BluetoothSdk.clearDefaultDevice();

await BluetoothSdk.cancelConnectionAttempt();
await BluetoothSdk.disconnect();
await BluetoothSdk.forget();
Prefer connecting to a Device returned by SDK scan callbacks. If your app wants connectDefault() to work after restart, persist a small default-device record in app storage and restore it with setDefaultDevice() before calling connectDefault(). Use scan() for user-facing device pickers. The progressive result callback is for UI: render the nearby-device list every time it changes during scanning. The returned final result is for control flow: after the timeout/completion, choose a device from the last list and connect. In multi-device environments, do not auto-connect to the first nearby glasses; present an explicit picker.

Device Identity

Device.id is the stable app-facing key for a scan result, within the limits of the platform identifier available to the SDK. Use it as a list key, selected-device key, and persisted default-device key. Do not parse id for model, name, or address information. Use the typed fields instead:
FieldMeaning
modelSupported glasses family, such as Mentra Live or G2.
nameBluetooth/display name reported during scan.
address / identifierPlatform device handle when available. Android commonly provides a Bluetooth address. iOS commonly provides a CoreBluetooth identifier. React Native exposes this value as address.
rssiOptional signal strength from scan results. It may be undefined at first discovery and appear in a later scan update when the platform reports RSSI metadata.
When the platform does not provide an address or identifier, the SDK falls back to a model:name key. Do not require rssi for picker rows. Use SDK-provided stable discovery order by default, and treat RSSI as supplemental signal-strength metadata when it is present.

Status

import {useMentraBluetooth} from '@mentra/bluetooth-sdk/react';

const mentra = useMentraBluetooth();
React Native exposes mentra.glasses.connection as a discriminated union:
type GlassesConnectionStatus =
  | {state: 'disconnected'}
  | {state: 'scanning'}
  | {state: 'connecting'}
  | {state: 'bonding'}
  | {state: 'connected'; fullyBooted: boolean};
Use mentra.glasses.connection.state for link-layer progress. fullyBooted only exists when state === 'connected'. The hook exposes the React app state as glasses, sdk, and scan.
Status snapshots are safe to read at any time. Treat command success as “command accepted”; keep UI state derived from status callbacks or hook state. Public status is grouped the same way across platforms:
FieldMeaning
glassesConnected-glasses runtime state. Includes connection/readiness, connected device identity, battery, firmware, Wi-Fi, hotspot, and signal metadata when connected.
sdkPhone-side SDK runtime state. Includes default device, gallery mode, microphone route, mic ranking, Wi-Fi scan results, scan activity, system mic availability, other Bluetooth audio status, and recent SDK log lines.
scanUser-facing scan state. Includes whether a scan is active, whether controller scanning is active, and the stable-order discovered Device[] list.
Use glasses.connected / mentra.glasses.connected before reading connected-only fields. Native Android uses GlassesRuntimeState.Connected; native iOS uses GlassesRuntimeState.connected(...); React Native exposes mentra.glasses with the same grouped concepts in React-friendly objects.

React Native Public Surface

These are the supported React Native app developer entrypoints:
AreaMethods
Status and subscriptionsuseMentraBluetooth, useBluetoothScan, and useBluetoothEvent for React components; addListener is available as the lower-level non-React subscription API
Default devicegetDefaultDevice, setDefaultDevice, clearDefaultDevice
Connectionscan, startScan, stopScan, connect, connectDefault, cancelConnectionAttempt, disconnect, forget
DisplaydisplayText, clearDisplay, showDashboard, setDashboardPosition, setHeadUpAngle, setScreenDisabled
Wi-Fi and hotspotrequestWifiScan, sendWifiCredentials, forgetWifiNetwork, setHotspotState
Camera and galleryrequestPhoto, queryGalleryStatus, setGalleryMode, setButtonPhotoSettings, setButtonVideoRecordingSettings, setButtonCameraLed, setButtonMaxRecordingTime, setCameraFov, startVideoRecording, stopVideoRecording
StreamingstartStream, keepStreamAlive, stopStream
AudiosetMicState, setPreferredMic, setOwnAppAudioPlaying, getGlassesMediaVolume, setGlassesMediaVolume
LED and versionrgbLedControl, requestVersionInfo
React Native helper exports include DeviceModels, isConnectedGlassesConnectionStatus, isReadyGlassesConnectionStatus, isBusyGlassesConnectionStatus, isConnectedWifiStatus, and isEnabledHotspotStatus. The React subpath exports useMentraBluetooth, useBluetoothScan, and useBluetoothEvent. For React Native status UI, use useMentraBluetooth() from @mentra/bluetooth-sdk/react. It returns mentra.glasses, mentra.sdk, and mentra.scan for connection, battery, Wi-Fi, hotspot, scan, and SDK runtime state. Important defaults:
  • scan(model, options) reports progressive results through options.onResults, resolves with the final matching Device[], and times out after 15 seconds unless options.timeoutMs is set.
  • connect and connectDefault default saveAsDefault and cancelExistingConnectionAttempt to true.
  • displayText(text, x, y, size) defaults to x = 0, y = 0, and size = 24.
  • setMicState(enabled) defaults to glasses microphone on, VAD bypass on, transcript events off, and LC3 events off. VAD means Voice Activity Detection; pass bypassVad=false only when you want speech-detected microphone events instead of continuous PCM.
  • requestPhoto(..., authToken, ...) omits the Authorization header when authToken is null or empty.
  • startStream optional video and audio configs are omitted unless supplied, so the connected glasses use their model defaults.
  • Photo capture, video recording, and streaming always enable the camera light as a privacy indicator.

Common Commands

AreaCommands
DisplaydisplayText, clearDisplay, showDashboard
Connectionscan, startScan, stopScan, connect, connectDefault, disconnect, forget
Wi-Fi and hotspotrequestWifiScan, sendWifiCredentials, forgetWifiNetwork, setHotspotState
CamerarequestPhoto, button photo settings, button video settings, camera field of view
StreamingstartStream, keepStreamAlive, stopStream
AudiosetMicState, audio callbacks, local transcription, media volume
SettingsBrightness, dashboard position, head-up angle, screen disabled, gallery mode
LEDsrgbLedControl on supported glasses
SystemrequestVersionInfo
Mentra Live has camera, microphone, and speaker hardware, but no display. G2 has display and microphone hardware, but no camera or speaker. Gate UI for display, camera, and speaker features by the connected model.

Events

React Native components should use useBluetoothEvent() for hardware events. The hook keeps the callback typed and removes the native subscription when the component unmounts. Native apps receive the same event categories through listener/delegate methods:
import {useBluetoothEvent} from '@mentra/bluetooth-sdk/react';

export function HardwareEventLogger() {
  useBluetoothEvent('button_press', (event) => console.log(event));
  useBluetoothEvent('touch_event', (event) => console.log(event));
  useBluetoothEvent('photo_response', (event) => console.log(event));
  useBluetoothEvent('stream_status', (event) => console.log(event));
  useBluetoothEvent('mic_pcm', (event) => {
    console.log(event.sampleRate, event.bitsPerSample, event.channels, event.encoding);
    console.log(event.pcm);
  });

  return null;
}
For non-React modules, BluetoothSdk.addListener(...) is the low-level subscription API. Keep the returned subscription and call remove() when the listener is no longer needed. The React Native event surface is typed through BluetoothSdkEventMap. These are the public event names accepted by useBluetoothEvent() and BluetoothSdk.addListener():
Event namePayload typeWhen it fires
logLogEventSDK diagnostic log line.
device_discoveredDeviceA supported glasses device is discovered during scan.
default_device_changed{device?: Device}The SDK default device changes.
glasses_not_readyGlassesNotReadyEventA command needs ready glasses but the connected device is not ready.
button_pressButtonPressEventGlasses button press.
touch_eventTouchEventGlasses touch or swipe gesture.
head_upHeadUpEventHead-up state changes.
vad_statusVadStatusEventVoice Activity Detection state changes.
battery_statusBatteryStatusEventBattery update from glasses.
local_transcriptionLocalTranscriptionEventSDK local transcription text update.
wifi_status_changeWifiStatusChangeEventGlasses Wi-Fi connection state changes.
hotspot_status_changeHotspotStatusChangeEventGlasses hotspot state changes.
hotspot_errorHotspotErrorEventHotspot operation fails.
photo_responsePhotoResponseEventPhoto request succeeds or fails.
gallery_statusGalleryStatusEventGallery content/camera-busy status changes.
compatible_glasses_search_stopCompatibleGlassesSearchStopEventCompatible-glasses search stops for a model.
swipe_volume_statusSwipeVolumeStatusEventSwipe-volume setting changes.
switch_statusSwitchStatusEventGlasses switch status changes.
rgb_led_control_responseRgbLedControlResponseEventRGB LED command succeeds or fails.
pair_failurePairFailureEventBluetooth pairing fails.
audio_pairing_neededAudioPairingNeededEventThe phone needs Bluetooth audio pairing for the device.
audio_connectedAudioConnectedEventBluetooth audio connects.
audio_disconnectedAudioDisconnectedEventBluetooth audio disconnects.
mic_pcmMicPcmEventPCM microphone frame arrives.
mic_lc3MicLc3EventLC3 microphone frame arrives.
stream_statusStreamStatusEventCamera stream lifecycle, reconnect, or error state changes.
keep_alive_ackKeepAliveAckEventGlasses acknowledge a stream keep-alive request.
For example, useBluetoothEvent('photo_response', ...) receives a PhotoResponseEvent, while useBluetoothEvent('mic_pcm', ...) receives a MicPcmEvent. MicPcmEvent includes sampleRate, bitsPerSample, channels, encoding, and vadGated; MicLc3Event includes sampleRate, channels, encoding, frameDurationMs, frameSizeBytes, bitrate, packetizedFromGlasses, and vadGated. Public React Native event payload fields use camelCase. For example, touch events expose deviceModel and gestureName, successful photo responses expose uploadUrl, hotspot errors expose errorMessage, and gallery status exposes hasContent and cameraBusy. Android and iOS expose typed callbacks/delegate methods instead of the React Native string event API. Android uses MentraBluetoothSdkListener methods such as onStateChanged, onGlassesChanged, onSdkStateChanged, onScanChanged, onDeviceDiscovered, onButtonPress, onPhotoResponse, onMicPcm, and onStreamStatus. iOS uses MentraBluetoothSDKDelegate methods such as mentraBluetoothSDK(_:didUpdate:), mentraBluetoothSDK(_:didUpdateGlasses:), mentraBluetoothSDK(_:didUpdateSdkState:), mentraBluetoothSDK(_:didUpdateScan:), mentraBluetoothSDK(_:didDiscover:), mentraBluetoothSDK(_:didReceive:), mentraBluetoothSDK(_:didReceiveMicPcm:), and mentraBluetoothSDK(_:didReceiveMicLc3:). Microphone audio callbacks use MicPcmEvent and MicLc3Event objects with the same metadata as React Native.
Event areaExamples
InputButton press, touch, swipe, head-up
Device stateBattery, case, Wi-Fi, hotspot, connection, RSSI
CameraPhoto request result, gallery state, camera settings
StreamingStream initializing, active, stopped, error
AudioMicrophone PCM, LC3, local transcription, audio route state
DiagnosticsSDK log events

Version Fields

Call requestVersionInfo() after connection when your app wants the glasses to refresh version metadata. Updated values arrive through the normal glasses-status callback and are also available in the next status snapshot.
FieldMeaning
firmwareVersionGeneric glasses firmware version when the connected model reports one.
deviceFirmwareVersionDevice firmware version for models that report device info as a structured payload.
leftFirmwareVersion / rightFirmwareVersionPer-side firmware versions for glasses that report left/right firmware separately.
besFirmwareVersionMentra Live BES firmware version.
mtkFirmwareVersionMentra Live MTK/system OTA firmware version.
appVersionGlasses-side companion app version. On Mentra Live this is the ASG client APK version, not firmware.
androidVersionAndroid OS version on Android-based glasses. This is not firmware.
Different glasses models expose different version fields, so apps should prefer the generic firmware field when present, then fall back to model-specific firmware fields. Keep app and OS versions visibly labeled as app/OS versions.