Bluetooth Traffic Capture for Gadgets

I’m looking for people who already own Bluetooth or Bluetooth Low Energy (BLE) devices and can collect Bluetooth traffic while using the device’s official mobile app. This is for an interoperability and device-preservation project. Payment is per accepted device/capture, not hourly. Important: prior Bluetooth capture experience required This is not a good project for someone who has never collected Bluetooth traffic before. You do not need to be an expert at reverse engineering Bluetooth protocols, but you should already have experience doing at least one of the following: Android Bluetooth HCI snoop logging Apple PacketLogger / Bluetooth capture workflows BLE captures using Nordic Semiconductor / nRF Sniffer Capturing Bluetooth traffic into Wireshark Similar Bluetooth debugging or protocol-analysis work If you have never successfully produced and opened a Bluetooth capture before, this probably is not the right Fiverr project to learn on. I care much more about getting a clean, complete, correctly timestamped capture than about receiving protocol analysis. Devices wanted I have a list of devices I’m specifically interested in, but I’m also interested in weird, unusual, discontinued, cloud-dependent, or otherwise funky Bluetooth/BLE devices that are not on the list. Examples of potentially interesting devices include: Smart appliances Kitchen gadgets Fitness equipment Lighting Displays Sensors Vehicle/motorcycle accessories Wearables Toys Robots Health/wellness gadgets Bluetooth controllers Devices with discontinued or poorly maintained apps Anything where the manufacturer appears to have invented its own Bluetooth protocol If you have something unusual, send me the manufacturer + exact model + app name and I’ll tell you whether I’m interested before you do the capture. Devices I already have Please do not submit these unless we specifically agree otherwise: Glow screen/display Airthings AdMore lightbar CHEF iQ Sense Ember Mug Enphase Envoy WalkingPad LIFX I’m looking for the other Bluetooth/BLE devices on my list, plus interesting devices I may not have discovered yet. Android, iPhone, and nRF captures are welcome Captures may be made using: Android iPhone / iOS Nordic Semiconductor nRF Sniffer or similar BLE sniffing hardware Android Android Bluetooth HCI snoop logs are great, especially for BLE devices where the official app communicates directly with the hardware. iPhone iPhone captures are also welcome and may be particularly useful for Bluetooth Classic / non-BLE devices. If you already know how to collect useful Apple Bluetooth traces, please mention your setup when you contact me. nRF / over-the-air BLE captures For Bluetooth Low Energy devices, captures made using Nordic Semiconductor nRF Sniffer for Bluetooth LE, a compatible Nordic development dongle/board, or another BLE sniffer are also welcome. If you have experience doing BLE captures with something like an nRF52840 dongle and Wireshark, definitely mention that. An nRF/over-the-air capture can be especially useful for seeing: Advertising packets Scanning Connection establishment BLE service traffic Reconnection behavior Other communication occurring over the air If you can conveniently provide both a phone-side HCI capture and an nRF over-the-air capture of the same session, that is particularly interesting. The important thing is that the resulting capture can be inspected later and correlated with the exact operations you performed. What you will do For each accepted device: Set up your Bluetooth capture method. Start the capture. Open the official app. Disconnect from the Bluetooth device. Wait several seconds. Reconnect to the Bluetooth device. Exercise the device’s normal app-controlled functionality. Keep a timestamped operations performed.txt file while doing this. Disconnect and reconnect again near the end if practical. Stop the capture. Send me the capture and supporting information. If possible, I would also like a separate capture that includes initial pairing/setup from an unpaired state, but please do not factory-reset a device unless we agree on that beforehand. Required deliverable #1: Bluetooth capture Send the raw Bluetooth packet capture in whatever usable format your setup produces, for example: .pcap .pcapng Android Bluetooth HCI snoop log Apple Bluetooth / PacketLogger capture nRF Sniffer / Wireshark capture Another Bluetooth packet capture format we agree on Do not just send screenshots of Wireshark or a Bluetooth analyzer. I need the actual packet capture. Required deliverable #2: operations performed.txt This file is mandatory. It should describe exactly what you did, with timestamps accurate to at least the second. For example: Device: ExampleCorp Smart Thing XYZ Phone: iPhone 17 Pro OS: iOS 20.0 App: ExampleCorp App 4.2.1 Device firmware: 1.8.3 Capture method: Apple PacketLogger Timezone: America/New_York 2026-08-09 14:03:12 - Started Bluetooth capture 2026-08-09 14:03:25 - Opened official app 2026-08-09 14:03:40 - Disconnected from device 2026-08-09 14:03:48 - Device shown as disconnected 2026-08-09 14:04:02 - Reconnected to device 2026-08-09 14:04:07 - App showed device connected 2026-08-09 14:04:20 - Turned device ON 2026-08-09 14:04:31 - Turned device OFF 2026-08-09 14:04:42 - Turned device ON 2026-08-09 14:04:55 - Set brightness to 25% 2026-08-09 14:05:07 - Set brightness to 50% 2026-08-09 14:05:19 - Set brightness to 100% 2026-08-09 14:05:34 - Changed color to red 2026-08-09 14:05:47 - Changed color to green 2026-08-09 14:05:59 - Changed color to blue 2026-08-09 14:06:18 - Selected Rainbow effect 2026-08-09 14:06:37 - Changed effect speed to 25% 2026-08-09 14:06:49 - Changed effect speed to 100% 2026-08-09 14:07:05 - Disconnected from device 2026-08-09 14:07:16 - Reconnected to device 2026-08-09 14:07:22 - Device state restored in app 2026-08-09 14:07:40 - Stopped Bluetooth capture The timestamps are important because I will use them to correlate actions in the app with individual Bluetooth packets. If you are running multiple capture methods simultaneously, please say so: Capture methods: - Android Bluetooth HCI snoop - nRF52840 + nRF Sniffer + Wireshark Exercise as many functions as possible Please try to exercise every meaningful Bluetooth-controlled operation exposed by the official app. Depending on the device, that might include: Connect Disconnect Reconnect Power on/off Read current status Change settings Change modes Change brightness Change colors Change speed/intensity Start/stop Set temperatures Set timers Trigger actions Read sensor values Enable/disable features Change configuration Send commands Sync data If a control has a continuous range, please choose several distinctive values rather than dragging it randomly. For example: Brightness: 0%, 25%, 50%, 75%, 100% Temperature: 100, 150, 200 Speed: 1, 3, 5 Color: red, green, blue, white This makes the protocol much easier to understand later. Please wait a few seconds between operations where practical. Initial connection / pairing Captures containing the following are especially valuable: Bluetooth advertising Scanning Device discovery Initial connection Pairing Bonding Authentication BLE service/characteristic discovery App initialization Firmware/version queries However, do not factory-reset or remove an important device from your account unless we agree on that first. A normal disconnect → reconnect sequence is required for the standard capture. Required device information Please include: Manufacturer Exact product name Exact model number Photo of the device Photo of model/serial label if available Phone model Android or iOS version Official app name Official app version Device firmware version, if visible Whether the device was already paired Whether the device uses BLE, Bluetooth Classic, or both, if known Capture method and hardware used Anything unusual that happened during the capture For nRF captures, please also include the hardware used, for example: Capture hardware: Nordic nRF52840 USB dongle Capture software: nRF Sniffer for Bluetooth LE + Wireshark Screen recording — strongly preferred If possible, also make a screen recording of the official app while performing the capture. This gives me another way to correlate UI actions with packet timestamps. Please still provide operations performed.txt even if you make a screen recording. Privacy Please avoid including sensitive information in the capture. Use a test account when practical. Bluetooth captures may contain information exchanged between your phone and the device. Do not send a capture containing information you are uncomfortable sharing. Payment / acceptance Payment is per accepted device. Before starting work, message me with: Manufacturer Exact model Photo showing you actually have the device Official app name Android or iPhone What Bluetooth capture method you will use What Bluetooth capture experience you already have Any other unusual Bluetooth/BLE devices you own For example: Device: FooCorp Model ABC-123 App: Foo Control Phone: Pixel 10 Capture: Android HCI snoop + nRF52840 BLE sniffer Experience: Have previously captured and analyzed BLE traffic in Wireshark Other devices: WeirdCorp heated socks, OldCo Bluetooth aquarium controller I will confirm which device(s) I want captured before you begin. Please do not purchase hardware specifically for this job without checking with me first. Multiple devices are welcome, and I’m especially interested in people who have collections of odd smart-home, appliance, automotive, fitness, lighting, toy, robot, or discontinued Bluetooth gadgets. What makes a capture acceptable An accepted capture should contain: A usable Bluetooth packet/HCI capture A clear disconnect → reconnect sequence Several seconds between major actions where practical Most or all meaningful app-controlled functions exercised operations performed.txt with accurate timestamps Device/app/OS/version information Capture-method information Enough information to identify exactly which hardware was tested Clean, carefully documented captures are much more valuable to me than protocol analysis. If you have a funky Bluetooth device that isn’t on my list, pitch it anyway.