Best Smartphone for Bluetooth Blynk Communication

Dear Forum,

I am currently using the Blynk app on an LG Aristo smartphone and communicating with an Arduino Pro Mini (3.3V) using an HC-06 Bluetooth module. This works GREAT!!!

I gave my friend the physical circuit with the Arduino Pro Mini connected to the HC-06 Bluetooth module. I provided him with shared access to the Blynk app. I toggled shared access to “ON” and then clicked on “Generate Link”. I e-mailed the link and QR code to him.

My friend is not able to establish and/or maintain the Bluetooth connection with the device for more that 1-2 seconds. He has tried a couple of different Android smartphones including a Cricket smartphone and a Motorola smartphone…not sure which models.

Can anybody suggest the BEST smartphone(s) for connecting to the HC-06 Bluetooth Module and used with the Blynk app? (in addition to the LG Aristo)


I don’t use Bluetooth with Blynk, but personally I just can’t get my head around the concept of shared access to a Bluetooth device in the way you’ve described.

Normally, with a Wi-Fi or Ethernet connected device, the communication route is that the device talks to the Blynk server across an internet connection, and the mobile device (phone/tablet) also talks to the Blynk server across an internet connection.
For the sake of this discussion, let’s say that the devices are located in your home.
When you share this project, the people you share this with have access to see the data that comes from the devices that are located in your home, and control them - regardless of where they are themselves.
The sharing process is there to give other people (and this is generally non-technical members of your household) the ability to control these Blynk connected devices without also giving those people the ability to edit the app project settings. That privilege is reserved for you as the account owner.

With Bluetooth, the connection is local because of the nature of the communication method, and the phone/tablet can act as a bridge between the Bluetooth device and the Blynk server (although I think this is optional, depending on whether an internet service is available and whether the direct connect option is used - I think).
When you share a Bluetooth project, I can’t see how the Bluetooth device(s) located in your home can be operated by the shared user, unless your phone is connected to that device.
What you’ve described is something very different, and it seems to me that what was actually needed was a clone of the project, and the Bluetooth device running a sketch with a different Auth code rather than the same one that your device uses.


Dear Pete,

Thank you for your reply.

I am not quite sure which scenario is correct.

If I gave my friend the device and then shared the link with him, then shouldn’t he be able to run the device on his smartphone with the shared link and from his WiFi network? I was able to operate the circuit from a different WiFi network from the “originating” Android smartphone. So shouldn’t my friend be able to use the shared link to run the device from his WiFi network?


I don’t understand where the WiFi network of this statement comes in to play, or why sharing is involved.
Also, if WiFi is available then why are you using Bluetooth?


Dear Pete,

I misunderstood your original comment. I thought that you were suggesting that WiFi had something to do with this. My mistake.

The device that I created is a Bluetooth controlled motor. I use a smartphone running the Blynk App to control the motor (on/off, speed, pulses, etc…).

The question is really which smartphone(s) running the Blynk App can pair to an HC-06 Bluetooth module?


Okay, I’ll respond once more then leave you to figure it out yourself.

I don’t believe that the connection issues your friend is experiencing is because of the type of smartphone that he is using, I believe that it’s because you are using a shared Blynk project.

I may be entirely wrong, but if you re-read my rather long explanation about why I think this is the case them maybe you’ll see why I think this.