- Tue Jul 25, 2017 11:03 am
#68552
Hello!
I went thru' the exact same exercise a few weeks back, and here are my observations.
The main obstacle is your Android app, unless you wrote it yourself.
The pic based product would be as happy to send data over bluetooth, or wifi (there's lua and arduino code for a simple UART to wifi bridge available at
http://www.roboremo.com/esp8266-tcp-to-serial.html). Simple enough, serial data in, TCP data over wifi out. And the other way.
Problem is the Android end; your app might expect the data in a different format.
In my case, the project worked beautifully with bluetooth, I created an ESp8266 to be a 'drop-n replacement' for that, confirmed it was doing its job using Blueterm. BUT, the app, if one chose Wifi instead of bluetooth, had a more elaborate preamble protocol.
Of course, if the app you mention is written by you, all the above is irrelevant, as you can make the app read your incoming data over wifi (Either TCP, or UDP) rather than bluetooth.
Regards,
Anand Dhuru