While it’s not the best Bluetooth module out there, it’s also not the worst. Connecting it to a micro controller is straightforward. Connect
VCC to a
5V power source, the
TX to the controller
RX. For the
RX of the
HC-08, you must watch out, as it requires
3.3V. If your controller uses
5V logic, then you must adapt your voltage to 3.3 (you can use the schematic below).
(the 1kOhm resistor is between the RX-TX line and the 2kOhm resistor connects back to the ground)
I used the following code to send messages and commands to turn an LED on and off.
By using a BLE Terminal App I was able to detect my device, connect to it and communicate both ways. I was unable to do the same from macOS, but more on this later.
You can send special commands over serial to your bluetooth module. Some devices may require special pins to be powered in a certain way. Check the datagram of your device for more information. In AT mode you can send string with the prefix
AT+. To test wether your devices supports and is in AT mode, sending the string
AT will return an
For a list of available AT commands check your modules manual. Some devices have a mini-AT mode. Commands can be used to query data (
AT+NAME=?) will return the name of the device. The same command can be used to set the name (
The idea behind my project was controlling different devices from my terminal (because I use it more than anything else and I always have a terminal window open somewhere) using BLE.
When scanning for Bluetooth devices on macOS my
HC-08 wouldn’t show up, but my iPhone and Raspberry Pi were able to pick it up. I checked the hardware on my Mac and the Bluetooth is
LMP Version: 4.0 (0x6). Which means it has BLE support.
I thought to myself that maybe normal users have no need for ALL random micro controllers with Bluetooth to show up in their discovery menu, so maybe the underlaying software was hiding something from me (as Apple software normally does >.>). So i tried this tool blueutil. But scanning for my device or even trying to directly connect using its address didn’t work.
This is when my journey to the deep corners of Apple’s IOKit drivers and Bluetooth. Their developer documentation mentions some different frameworks. Most apps and devices use the common IOBluetooth Framework. For BLE devices you must use CoreBluetooth
While searching for people who found a way to access the Bluetooth API without using Swift or Objective-C, I found this repo. It’s a NodeJS library that uses XPC connections to communicate with the Bluetooth service/daemon. This is a nasty workaround because Apple changes the inner-workings of their software with each major update and without notice. This will result in breaking changes and having to patch your library with every update, resulting in a big library full of duct-tape.
I will be using my Raspberry Pi to controller any Bluetooth device. Maybe even setup a web server or basic API to not require me to be connected over SSH or something else.
In my endless search for a solution I did stumble upon some interesting tools developed by Apple for Apple and other interested developers.
One of these tools is a Bluetooth Explorer which is able to scan for BLE devices, display them and even connect. If I had to guess all these apps were developed using their APIs and would have loved to have a command line interface that does the very same thing. I hate GUIs.