Hello to everything. I Have problem to pair the Thunkable app with ESP32 BLE
Can some one tell me where is the bug?
Can some one tell me where is the bug?
Hi franco.demei, welcome to Thunkable! 
Be sure to check out How to ask Great Questions v2.0, the Community Guidelines, and our Getting Started Guide to make the best of your Thunkable Community experience!
It is always best to use the green error block and attach it to a label to see what the specific error is in these cases. It will be impossible for us to help otherwise. I am also assuming there is no UUID in the blocks for security reasons (you don’t want to show us) but if not, that characteristic UUID is required anytime you connect with or transmit data to and from a BLE device.
Hi Matt, thank you for answer. I’m Beginner in ThunKable programming. I reached ThuneKable site because I Need to realize one app for iOS smartphone. . I already built same app for android with MIT App Inventor, almost similar to Thunekable. The blocks are quite same, but It doesn’t ask for any UUID and It work fine. To be honest, I don’t know how calculate the UUID. I have idea to upgrade account to PRO line , but before I would like understand how the system work. One question, If I use the “LIVE Test On Device” On my Android device I can see the app working ?
Below working blocks of Mit App Inventor.
Thank You Again Matt.
Hi @franco.demei apologies here. We have found an issue with the Connect To BLE blocks and working as quickly as possible to resolve the issue. We will reach out to you here as soon as we know more.
@franco.demei This issue has been resolved and we put out a fix for it earlier today.
Please keep in mind that you may need to do a hard refresh of your browser for the changes to take effect in your project. If you experienced any of these issues on the Thunkable Live app, you will need to update to the latest version through the App Store and/or Google Play Store before any changes will occur. If your downloaded or published app is affected by any of these issues, you will need to re-download or re-publish your app for these changes to take effect.
Hi MatT, Thank you for reply. I removed all chronology from my browser, and I reinstalled ThunKable live to my Phone, but still. with live test the app doesn’t work, also I reach already n. 2 download. I tried also to change phone but result is the same. I tried with scan function and the small app read anki n. 2 device (unused) below Scan blocs
and app screen shot
doesn’t see ESP32 device below bluetooth device
Is the ESP32 already connected to a different device via BLE? Our scan will only display devices that are available for connection.
No Esp32 isen’t connected to other device. other app done with MIT APP Inventore work fine
That is a separate issue. There is no device ID entered and so it will never be able to connect.
Does that simple list scroll? Can you scroll down the simple list and see if the device is on one of the other lines?
No Matt, It doesn’t scroll down.
It may just be a Simple List issue and nothing to do with scanning. Can you set your scan up this way and see if more items show?
I tried to do as you suggested, but it’s still the same, I only see one device as you can see in the screenshots
One is the app screenshot and one is what my phone Bluetooth see.
I’m very sorry for the inconvenience, it is very hard to tell what is going on here. Is that simple list not scrollable now? I see some device at the bottom, you should be able to scroll more now to see it and any others.
I used the app to test locally and all the BLE devices in my home are showing. DSD TECH is the bluetooth controller for my Arduino board. What BLE controller are you using?
Hello Franco, perhaps my experience with esp32 and BLE can be of use to you.
Before I also had an app with app inventor that connected with ESP32.
The difference with thunkable is that app inventor only uses the old version of bluetooth while in thunkable BLE is used.
You need to modify the programming of your esp32 board to be able to connect with your new app.
Hi Matt.
Perhaps this error that you mentioned with the BLE (connect to device name) block prevented you from being able to connect to the BLE device by name? A few weeks ago my tunkable app stopped being able to connect to my BLE hardware with the name and I had to modify it so that it could connect by MAC
