TransparentBLE
No in-app products collected for this app.
| Rating | |||
|---|---|---|---|
| United Arab Emirates | <1%0 | — | |
| Afghanistan | <1%0 | — | |
| Antigua And Barbuda | <1%0 | — | |
| Anguilla | <1%0 | — | |
| Albania | <1%0 | — | |
| Armenia | <1%0 | — | |
| Angola | <1%0 | — | |
| Argentina | <1%0 | — | |
| Austria | <1%0 | — | |
| Australia | <1%0 | — |
Description
TransparentBLE is a local-first Bluetooth Low Energy utility for discovering, inspecting, logging, and controlling BLE devices from iPhone or iPad.
Use it to scan nearby BLE peripherals, connect to devices, inspect GATT services and characteristics, read values, write payloads, subscribe to notifications, and debug raw BLE traffic in console and terminal-style views.
TransparentBLE also supports reusable BLE profile files. A profile can describe how a device should be matched, which services and characteristics it uses, how notification payloads should be parsed, and which controls should appear in the app. This lets makers, developers, and hardware owners create an iOS control surface for BLE devices without building a custom Swift app.
Features:
BLE device scanning with configurable refresh intervals
GATT service and characteristic inspection
Read, write, and notify support
Console and terminal-style BLE debugging
RSSI tracking and RSSI history graph
JSONL diagnostic log recording
Log history with filtering, timeline view, export, and share support
Optional background recording for diagnostics
Live Activity and Dynamic Island status while recording
Import local .bleprofile.json files
Import profiles from supported TransparentBLE links
Profile-based controls including switches, sliders, RGB controls, and option pickers
Local-first design with no ads, analytics, tracking SDKs, or developer-operated cloud service
TransparentBLE is useful for BLE debugging, hardware testing, IoT projects, ESP32 experiments, embedded devices, meters, sensors, chargers, and custom BLE hardware where you understand the device protocol.
Safety note: BLE profiles and write commands can affect connected hardware. Only import profiles you understand and trust, and test control commands carefully.