-
Notifications
You must be signed in to change notification settings - Fork 7.6k
SerialToSerialBT with PIN code enabled connects to smartphone withtout asking for PIN code #9599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello everyone, BluetoothSerial SerialBT; const char* pin="1234"; void setup() SerialBT.setPin(pin); } |
Unfortunately, this is not possible without compiling your own libraries, but you can set it up with Simple Secure Pairing (a random connect string). |
Hello, Due to the overwhelming volume of issues currently being addressed, we have decided to close the previously received tickets. If you still require assistance or if the issue persists, please don't hesitate to reopen the ticket. Thanks. |
Board
ESP32 Dev Module /Wemos D1 mini ESP32
Device Description
ESP32 dev board (WROOM 32D)
also tested with Wemos/Lolin D1 mini ESP32 Version
Hardware Configuration
nothing attached
Version
other
IDE Name
Arduino 1.8.13
Operating System
Windows 11
Flash frequency
80MHz
PSRAM enabled
no
Upload speed
921000
Description
Official ESP32 Version v2.0.16 installed via Arduino IDE Board manager
Sketch
Debug Message
Other Steps to Reproduce
Smartphone asks If i would like to pair and pairs with ESP32 without asking for a PIN and also doesn't show any PIN to compare...
Also you can use in core included example SerialToSerialBT.ino with uncommented
#define USE_PIN
, It doesn't asks for any PINs also.in #6061 was mentioned that PIN issue was fixed, but maybe only if connect ESP master to (ESP) slave?
In my case ESP32 is a slave and Smartphone (Samsung Galaxy S23) is a master.
My old issue was clossed, but I still don't have any solution: #4566
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: