How to avoid reconnecting an already paired device via WebBluetooth on every page reload.

You are reading a single comment by @user128009 and its replies. Click here to read the full conversation.

•

Gordon

Hi! This is something I have been wondering about actually.

I think realistically to do it nicely, it could do with being integrated into the Puck.js/UART.js library itself (at https://github.com/espruino/EspruinoWebTools). I think long term the best thing would be to introduce the functionality to UART.js (which already has the ability to display a menu for >1 device), and then maybe just make Puck.js a stripped down version of UART.js that doesn't do Web Serial (it's getting stupid having two extremely similar libraries).

The WebIDE at https://www.espruino.com/ide/ can keep previous connection info and reconnect, however it is also lost when you reload the page. I think this is by design

Yes, I was wondering about that. On Web Serial it works totally as expected, but it seems it doesn't on Web Bluetooth.

Having said that, this example from the Chrome team themselves doesn't appear to remember devices: https://googlechrome.github.io/samples/web-bluetooth/watch-advertisements-and-connect.html

But this one does - at least for me: https://googlechrome.github.io/samples/web-bluetooth/watch-advertisements-and-connect-async-await.html

But apart from the usage of promises vs. async/await I'm having trouble figuring out why!

However if we can figure that out I'd love to get the changes into the IDE so it does remember, and maybe get the relevant stuff added to UART.js

•

user128009 in reply to @Gordon

Thanks for the link.

https://googlechrome.github.io/samples/web-bluetooth/watch-advertisements-and-connect-async-await.html also gives me the device is out of range error, however, adding a call to requestLEScan() or just requestDevice() seems to trigger advertisement packages, which will cause a reconnect without selecting a device in the dialog.

However, the scanning/request dialog is still shown (and it doesn't disappear when a device is connected). Is there any option to close the scanning/request dialog programatically? It does not support AbortController signals.

About

Avatar for user128009 @user128009 started