Thing plus ble failure for one board but not another

Development Boards ESP32
1

I have been struggling to get the bluetooth on the thing plus working with an app. I bought a second thing plus as a spare while the other was integrated. All of a sudden things are working. I finalize the code go back to the integrated thing plus, load the code and now i’m getting strange ‘unknown characteristic’ messages.

I then load the exact same code on the two different boards. One works the other does not. Has anyone seen this? The failing board initially connects but once i try to retrieve data it throws what looks like coding errors so it’s very strange.

Is there a way to fully reset the thing plus somehow? wipe any data that might be saved outside of the standard arduino code?

2

could it be you use a different compiler / board library ?

can you share a sketch so we can try or provide some advice ?

3

I literally plug one board in, upload. Plug the other board in, change the name of the device (as a variable in the code) then upload again.

I’m using the BLE libraries (BLEDevice.h) libraries on the board side and flutter_reactive_ble libraries on the app side.

both thing plus boards say V2.0 on the backside.

If it’s not the board, my only thought would be to confirm that the BLE services behave appropriate on another app for IOS/Android. At least this could narrow it down to the arduino code or app code.

Happy to answer specific questions.

4

When you get “now i’m getting strange ‘unknown characteristic’ messages”, is that during compile or during running ?

If during compile, what happens if you do NOT change the name of the device ?

What happens if you try to connect to the ESP32 from your phone with the nRF Connect Client ?

5

the strange errors are once i connect to the blue tooth service and then try to access characteristics.

I was going to try connecting with my phone, but my red board now won’t take new code so i had to use the spare esp32 to run another program. I’m pretty sure it has nothing to do with the device name because i’ve tried multiple variations and have not always changed the name. (my only guess is that after updating the comm port for the thing plus the redboard is now not happy. didn’t have time to debug)