Hello All,
I hope to be at the right place. This is my 1st topic...
I do have a Compagnon crash as soon as I connect to ESP32.
This happens only when I use "Call bluetooth.RegisterStrings" ! When I use "Call bluetooth.ReadStrings" My app works like a charm. Obviously, I would have prefered to Register the datas coming from BME280 sensor : Temperature, Pressure, humidity and battery voltage.
Sorry, I clicked the wrong button. I must add the ble extension is 20240822. My phone is Android 14UKQ1 + Xiaomi HyperOS 1.0.9.0.
Thank you for you time.
AppIventorError.txt (1.1 KB)
In the error we can read that the UUID string is too long.
Thank you for replying so quickly.
I have shorten the UUID name, but unfortunately get the same error with the "Register" bloc. The UUIDs themselve are generated with the right lenght (I hope). I copied and pasted from Thonny to App Inventor blocs The "Read" bloc runs fine with the previous "too long" UUID name. How to understand the "Caused by: java.lang.IllegalArgumentException: UUID string too large
at java.util.UUID.fromString1(UUID.java:299)" error ?
Try this test companion. Maybe it's a problem with Companion. Do you have the ble extension in the latest version?
Also check if the uuid does not contain any invisible characters, e.g. spaces.
the ble extension is 20240822. I guess it's the latest. I will try new Compagnon version, but first I will try to build the App with "Register" blocs and install it on the mobile phone... Let see
Hello Patrick,
That issue is related to Compagnon, you are true. I built and installed the apk on my Xiaomi and it works perfectly now. Thank you very much for your help
ith kind regards
Jacques
Me again,
1 more remark concerning the different behaviours between"Read" and "Register" :
With Read bloc, strings are displayed as soon as connection is established (which is nice)
With Register bloc, strings are displayed in the label box after the 2nd post from ESP32. This means I have to wait for 2 mins before to read my first values (because I send datas each 2 minutes). The following datas are well refreshed each 2 minutes.
It should be nice to have registred strings available as soon as connected, like Read bloc behaves.
Best regards