Guides

This section provides general instructions on using key OBH SDK features.

Device Ownership and Association

To use a base, it must be assigned to an owner.

Association Process

The association process follows these steps:

• Scan for available devices.
• Connect to the desired device.
• Initiate the pairing process.

Dissociation Methods

There are two ways to dissociate a device from its owner:

• Direct Dissociation: Requires an active connection to the base. The current owner is immediately removed, rendering the base unusable until reassigned.
• Indirect Dissociation (Abandonment): The server records the owner’s intent to abandon the device, but the base retains all ownership data and remains operational. The dissociation occurs automatically when a new owner pairs with the device.

The indirect dissociation method allows for remote ownership transfer, eliminating the need for a direct BLE connection.

Base Operability

Developers can interact with any base where their account holds ownership. The list of owned bases can be retrieved via the available methods.

To unlock the latch securing the headset, call the appropriate function. State changes for bases are dispatched via event-driven mechanisms, following the conventions of the respective programming language.

State Monitoring

The SDK reports device state updates to our servers whenever a BLE connection is established. These updates allow us to analyze fleet-wide performance and identify areas for improvement.

Implementation example

You can find on this page a detailed guide of an operator application implementation example.