Hi I’m playing around with BLE connection, and I can scan, find devices, and then connect. But afterwards, any use of the BLE transmit or receive causes the Thunkable app on my phone to “reset” (using a Pixel 6). I’ve tried all combinations on the UIUD string (dashes included, lower-case, upper-c…

Thanks, it looks like the issue now resolved with the June 2022 Live App update! You can directly read “Receive Byte Array” with the BTLE components and receive the correct bytes.

Welcome to Thunkable. Thunkable only reads from a characteristic UUID that has the read property active.

Interesting, so I’ve had multiple things going wrong: First, my experiments weren’t updating the live app (I had to start changing a label on the designer screen to get code changes). So I was making changes, but not testing new code. Second, it now appears it crashes using either Transmit/Receive…

[image] davew3q: my experiments weren’t updating the live app When using Thunkable mobile app you need to keep the app open with your project loaded and the mobile does not go in sleep mode (display off). You will notice whatever changes you do in the project will cause the project to reload …

Thanks for your help on the code updating, going back to the screen helped. The BLE TX is working now with the list, but I’m still debugging on the “Receive Byte Array” array in this post: [image] Why does BLE Receive String work, and BLE Receive Byte Array not work BLE / BlueToot…

Have you seen this? [image] [Solved] Bluetooth LE Transmit Byte Array Questions about Thunkable edit 1: attached screenshots edit 2: attached screenshot of the receiving blocks @Paolo_Tealdi & @shawnmccazl thanks to this comment by @gaston_fabbietti I have also solved h…

Yep, the GATT characteristic definitely has a READ property, I’ve confirmed the UIUD is marked as a READ with a separate BTLE utility on the phone.

is the characteristic UUID a 128-bit one? Not sure if this is mandatory, but my working example used this. Again, check things like dashes are in the right places etc. (not being patronising, just things to double check). Is the characteristic EXCLUSIVELY READ, or does it just include READ? I’v…

No problem! It’s sometimes the littlest things that trip you up. Yes, it’s a 128-bit UUID, I spent some time with the dashes to get the Receive stream version working [image] This characteristic is just a READ (no notify or indication possible either). Of course once this works, I want to mov…

Okay, well that’s not the issue then (could be good or bad news). My next thinking is what is the data type is the thing you’re reading? I can’t remember if I tested sending numbers as part of the receive string demo that I got working. Even if I did, it might be encoded differently (i.e. as ASCII c…

Thanks, I’m got a picture from your post on building a list from the output. In my case, the “Receive Byte Array” is throwing out an error before I can even get to the data.

[Resolved] Error in transmit/receive on BLE

Questions about Thunkable Issues / Bugs

tatiang April 13, 2022, 2:55pm 6

Have you seen this?

1 Like

Topic		Replies	Views
Issues with BLE read/write byte array blocks BLE / BlueTooth bluetooth	27	1884	September 9, 2022
[Solved] Bluetooth LE Transmit Byte Array Questions about Thunkable solved , bluetooth , crash	9	5426	November 8, 2024
Something wrong in my communication through BLE Questions about Thunkable	23	1410	November 8, 2024
Why does BLE Receive String work, and BLE Receive Byte Array not work BLE / BlueTooth	12	2448	October 1, 2022
[SOLVED] Difficulty Receiving Strings Over Bluetooth BLE / BlueTooth	4	91	April 21, 2025

[Resolved] Error in transmit/receive on BLE

Related topics