Dear Blynk team,
I tried BT classic and BLE with the current Beta version (on 16/2/2019), but it doesn’t work at all.
The last weeks I have spent a lot of time investigating the Bluetooth classic & BLE implementation in Blynk, and hopefully I helped you with it by sending log files. However, I do no longer understand what you are doing, I even start doubting if the Android code is actually tested on real BT classic hardware.
a) Android+Library: login protocol
The login protocol problems started with the introduction of Blynk library 0.6.0 in which some incompatible changes were introduced. As a result
- in the Android app, some changes were done to handle this in 2.27.2 beta
- in the Blynk library some changes were done to handle this (in github, not yet in the official release)
I noticed that the changes in the Android app, made the situation even worse. And by changing the library, the protocol in the Android app even didn’t had to be changed.
My conclusion: it would be better to revert all changes in the Android app related to the login protocol. The 2.27.1 app connects to the github version of the Blynk library
b) Android: - ping problem
In the version 2.27.1, the app nicely reacts on ping messages 06 00 xx 00 00 with 00 00 xx 00 c8. Please revert the changes in the Android app that made 2.27.2 beta no longer react to ping messages
c) Android: - pull data
When combining version 2.27.1 with the current github version of the library, there is a problem with pull data, which I guess was fixed in 2.27.2 beta
d) Example browser
A lot of people are already complaining for months that BT/BLE doesn’t work when they start with the example code generated in the example generator, because of lacking
please fix this.
Some time ago, I had a perfect working solution (100% login, 0% packet loss, 100% automatic reconnection after disconnection) with BT classic running on ESP32. But it is no longer the case …