Web Bluetooth Won't Detect Devices That were Previously Connected

Multi tool use
Multi tool use












0















I'm using web bluetooth to connect to an ESP32 module.



My application is working perfectly on Linux and OSX, but on Windows I'm running into issues.



When doing the initial navigator.bluetooth.requestDevice call everything works fine -.. However, after a device has been connected and then disconnected web bluetooth fails to see the device again. I'm able to manually search for nearby BLE devices in the control panel and it recognizes the device (discoverable but not connected), but web bluetooth outright fails to see the device.



It seems to be just that Windows computer too -.. When I look for the device on my Mac it's discoverable.



Is there something going on with Windows where previously connected devices aren't discoverable by web-bluetooth?



My connection code is very simple:



    navigator.bluetooth.requestDevice(optionalServices:['0000ffe0-0000-1000-8000-00805f9b34fb']})
.then(device => {
console.log('Connecting...');
deviceName = device.name;
return device.gatt.connect();
})
.then(server => {
console.log('Getting Service...');
return server.getPrimaryService(serviceUuid);
})
.then(service => {
console.log('Getting Characteristic...');
return service.getCharacteristic(TXcharacteristicUuid).then( characteristic => {
myTXCharacteristic = characteristic;
return service.getCharacteristic(RXcharacteristicUuid);
})
})
.then(characteristic => {
myRXCharacteristic = characteristic;
return myRXCharacteristic.startNotifications();
})
.catch(error => {
console.log('NOOOO! ' + error);
});









share|improve this question























  • Is this issue permanent (once a device has been connected once it can never be found again) or is the device discoverable again after the browser or computer is restarted?

    – Reilly Grant
    Jan 2 at 22:17











  • It’s permanent we tried restarting the device, computer, emptying chromes cache, etc

    – Wezley
    Jan 4 at 1:29
















0















I'm using web bluetooth to connect to an ESP32 module.



My application is working perfectly on Linux and OSX, but on Windows I'm running into issues.



When doing the initial navigator.bluetooth.requestDevice call everything works fine -.. However, after a device has been connected and then disconnected web bluetooth fails to see the device again. I'm able to manually search for nearby BLE devices in the control panel and it recognizes the device (discoverable but not connected), but web bluetooth outright fails to see the device.



It seems to be just that Windows computer too -.. When I look for the device on my Mac it's discoverable.



Is there something going on with Windows where previously connected devices aren't discoverable by web-bluetooth?



My connection code is very simple:



    navigator.bluetooth.requestDevice(optionalServices:['0000ffe0-0000-1000-8000-00805f9b34fb']})
.then(device => {
console.log('Connecting...');
deviceName = device.name;
return device.gatt.connect();
})
.then(server => {
console.log('Getting Service...');
return server.getPrimaryService(serviceUuid);
})
.then(service => {
console.log('Getting Characteristic...');
return service.getCharacteristic(TXcharacteristicUuid).then( characteristic => {
myTXCharacteristic = characteristic;
return service.getCharacteristic(RXcharacteristicUuid);
})
})
.then(characteristic => {
myRXCharacteristic = characteristic;
return myRXCharacteristic.startNotifications();
})
.catch(error => {
console.log('NOOOO! ' + error);
});









share|improve this question























  • Is this issue permanent (once a device has been connected once it can never be found again) or is the device discoverable again after the browser or computer is restarted?

    – Reilly Grant
    Jan 2 at 22:17











  • It’s permanent we tried restarting the device, computer, emptying chromes cache, etc

    – Wezley
    Jan 4 at 1:29














0












0








0


1






I'm using web bluetooth to connect to an ESP32 module.



My application is working perfectly on Linux and OSX, but on Windows I'm running into issues.



When doing the initial navigator.bluetooth.requestDevice call everything works fine -.. However, after a device has been connected and then disconnected web bluetooth fails to see the device again. I'm able to manually search for nearby BLE devices in the control panel and it recognizes the device (discoverable but not connected), but web bluetooth outright fails to see the device.



It seems to be just that Windows computer too -.. When I look for the device on my Mac it's discoverable.



Is there something going on with Windows where previously connected devices aren't discoverable by web-bluetooth?



My connection code is very simple:



    navigator.bluetooth.requestDevice(optionalServices:['0000ffe0-0000-1000-8000-00805f9b34fb']})
.then(device => {
console.log('Connecting...');
deviceName = device.name;
return device.gatt.connect();
})
.then(server => {
console.log('Getting Service...');
return server.getPrimaryService(serviceUuid);
})
.then(service => {
console.log('Getting Characteristic...');
return service.getCharacteristic(TXcharacteristicUuid).then( characteristic => {
myTXCharacteristic = characteristic;
return service.getCharacteristic(RXcharacteristicUuid);
})
})
.then(characteristic => {
myRXCharacteristic = characteristic;
return myRXCharacteristic.startNotifications();
})
.catch(error => {
console.log('NOOOO! ' + error);
});









share|improve this question














I'm using web bluetooth to connect to an ESP32 module.



My application is working perfectly on Linux and OSX, but on Windows I'm running into issues.



When doing the initial navigator.bluetooth.requestDevice call everything works fine -.. However, after a device has been connected and then disconnected web bluetooth fails to see the device again. I'm able to manually search for nearby BLE devices in the control panel and it recognizes the device (discoverable but not connected), but web bluetooth outright fails to see the device.



It seems to be just that Windows computer too -.. When I look for the device on my Mac it's discoverable.



Is there something going on with Windows where previously connected devices aren't discoverable by web-bluetooth?



My connection code is very simple:



    navigator.bluetooth.requestDevice(optionalServices:['0000ffe0-0000-1000-8000-00805f9b34fb']})
.then(device => {
console.log('Connecting...');
deviceName = device.name;
return device.gatt.connect();
})
.then(server => {
console.log('Getting Service...');
return server.getPrimaryService(serviceUuid);
})
.then(service => {
console.log('Getting Characteristic...');
return service.getCharacteristic(TXcharacteristicUuid).then( characteristic => {
myTXCharacteristic = characteristic;
return service.getCharacteristic(RXcharacteristicUuid);
})
})
.then(characteristic => {
myRXCharacteristic = characteristic;
return myRXCharacteristic.startNotifications();
})
.catch(error => {
console.log('NOOOO! ' + error);
});






google-chrome web bluetooth esp32 web-bluetooth






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 28 '18 at 21:21









WezleyWezley

1081113




1081113













  • Is this issue permanent (once a device has been connected once it can never be found again) or is the device discoverable again after the browser or computer is restarted?

    – Reilly Grant
    Jan 2 at 22:17











  • It’s permanent we tried restarting the device, computer, emptying chromes cache, etc

    – Wezley
    Jan 4 at 1:29



















  • Is this issue permanent (once a device has been connected once it can never be found again) or is the device discoverable again after the browser or computer is restarted?

    – Reilly Grant
    Jan 2 at 22:17











  • It’s permanent we tried restarting the device, computer, emptying chromes cache, etc

    – Wezley
    Jan 4 at 1:29

















Is this issue permanent (once a device has been connected once it can never be found again) or is the device discoverable again after the browser or computer is restarted?

– Reilly Grant
Jan 2 at 22:17





Is this issue permanent (once a device has been connected once it can never be found again) or is the device discoverable again after the browser or computer is restarted?

– Reilly Grant
Jan 2 at 22:17













It’s permanent we tried restarting the device, computer, emptying chromes cache, etc

– Wezley
Jan 4 at 1:29





It’s permanent we tried restarting the device, computer, emptying chromes cache, etc

– Wezley
Jan 4 at 1:29












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53964412%2fweb-bluetooth-wont-detect-devices-that-were-previously-connected%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53964412%2fweb-bluetooth-wont-detect-devices-that-were-previously-connected%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







5 fMKUPN79ekIUpg,Z45fgOR,i4U,fQ2Ythqv3ayR17Asn7qkralOB4idXi37dpGteyxVZg,o7jhFsCIQRj,W
0dJZai epwfO9gEj

Popular posts from this blog

Monofisismo

Angular Downloading a file using contenturl with Basic Authentication

Olmecas