-
Notifications
You must be signed in to change notification settings - Fork 8
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
Unable to establish a connection: NotFoundError..... #22
Comments
After enabling web bluetooth in the browser (see: https://reelyactive.github.io/pareto-anywhere/enable-web-bluetooth-scanning/ ) the error message remains unchanged. |
I'm assuming this is Android. We haven't been able to get WebBluetooth on Android working reliably yet. |
OK, thanks ! If it isn't Chrome on Android, where should I use it
preferably?
Op za 26 jun. 2021 00:24 schreef Paulus Schoutsen ***@***.***
…:
I'm assuming this is Android.
We haven't been able to get WebBluetooth on Android working reliably yet.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGII3TXJLO6RS6AVC7NTZOLTUT63JANCNFSM47KPZEQA>
.
|
@balloob, to prevent misunderstandings: I used Chrome on my Android mobile. So I use the JS solution (SDK-js) . For my own understanding: is it right that iffff all things worked like you have intended, would it be possible when I did not run my own web page running the code but any page? Such as now, that I used the button on your page in the documentation? |
@balloob Curious if there's been any progress getting Improv to play nicely with Android WebBluetooth? |
Nope |
@goofy2k , you wrote:
Can you tell me which component you integrated into your firmware? I already integrated https://github.com/[improv-wifi/sdk-cpp](https://github.com/improv-wifi/sdk-cpp) for serial communication and this works fine. But now i want to use esp-web-tools via BLE |
Hi @tobiasfaust,
Unfortunately I can't remember. It is 3 years ago and I haven't done
anything since then with bluethooth.
I looked in my repos and see an old project with NimBLE. But I don't see a
reference to activities with improv.
In my Faust(!)-Synth-MIDIBLE I see an esp-nimble-cpp component.
I took that from https://github.com/h2zero/esp-nimble-cpp/release/tag/v1.4.1
Goodluck with your project!
Op za 16 nov 2024 12:15 schreef tobiasfaust ***@***.***>:
… @goofy2k <https://github.com/goofy2k> , you wrote:
Hi, I want to test Improv on a ESP32 NodeMCU board. I added the component
to the firmware. Selected 'none' for authorization. The code compiles OK
and the logs show that the BLE serve is up.
Can you tell me which component you integrated into your firmware? I
already integrated
https://github.com/[improv-wifi/sdk-cpp](https://github.com/improv-wifi/sdk-cpp)
for serial communication and this works fine. But now i want to use
esp-web-tools via BLE
—
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGII3TXZTC4QGRZDBYPL4O32A4SO3AVCNFSM6AAAAABR4XFP4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBQGUZDMNZYG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi, I want to test Improv on a ESP32 NodeMCU board. I added the component to the firmware. Selected 'none' for authorization. The code compiles OK and the logs show that the BLE serve is up. I want to test using the Connect device to Wi-Fi button on your imrov-wifi.com site. I access the site on my mobile phone with BT on.
I see an icon that measures signal strength from my ESP32 device. When I press the button to connect a popup apperears, telling:
An error ocurred. Unable to establish a connection: NotFoundError: No Services matching UUID 00467768-6228-2272-4663-277478268000 found in Device.
As there are no other required settings involved, I would expect that trying to connect from any device and any site (including yours) would be OK.
Am I wrong?
Do you have any suggestions on how to proceed?
The text was updated successfully, but these errors were encountered: