> For the complete documentation index, see [llms.txt](https://docs.mobiusflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobiusflow.com/help/technical-docs/mobiusflow-services/ble-devices.md). # BLE Devices Usage of MobiusFlow BLE devices service to decode incoming BLE raw data and populate MobiusFlow objects. The BLE service works in conjuction with the following feeder services: * BLE Gateways * Juniper Mist * Aruba Connectors All three of these services forward undecoded BLE advertisment data to the MobiusFlow hub (via a BLE\_RX broadcast command). The BLE Devices service listens for this data. If the service detects data for a device that matches one registered with it, it will decode the data and populate the corresponding MobiusFlow object. ## Service Configuration Inititally, add the service from the service library:

### Service Settings The service itself has no custom settings. When run, it will automatically listen for data from all feeder services without any configuration. ### BLE Devices / Objects Every BLE device must be added to the service as an object. Initially, view the objects on the BLE devices service by clicking on it's tile:

Here your BLE devices are shown in the region marked here in green. Add new devices from the objects library marked in red here. When you add a new device, you must add its BLE Address so the service knowns where to send incomming data:

Finally, ensure the service is started:

Now as data comes in from feeder services, the corresponding MobiusFlow objects will be populated:

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mobiusflow.com/help/technical-docs/mobiusflow-services/ble-devices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.