Most recent activity
-
@daphtdazz Hey, it looks like application cache isn't supported... Is that right?
any hint about changing this in the future? Looks like Safari is a little ways off from a replacement right now...
https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache
https://jakearchibald.github.io/isserviceworkerready/ -
-
Hey! I did some more testing and found the error using this remote console tool called JS Console... https://jsconsole.com/?%3Alisten
Here's the error every time the standard 2 byte heart rate monitor value is sent to Web BLE...
"Unexpected characteristic value notification for device 810058E3-27E6-4D1A-A9A8-FC8C4C357D84 and characteristic 2a37"
.... let me know what else I can provide...
-
-
-
@Gordon... thanks I think that works... off to the races...
-
hmmmm... I guess I need to develop my ble device attributes a little better... they come up as 'undefined' when I call them in chrome browser
navigator.bluetooth.requestDevice(options1) .then(device => { console.log('> Services: ' + device.services); console.log('> namePrefix: ' + device.namePrefix); console.log('> Name: ' + device.name); //console.log('> Id: ' + device.id); //console.log('> Connected: ' + device.gatt.connected); })
-
@daphtdazz Hey, there's an issue with the way webble resolves this address. Seems to work on safari, ios, and chrome. Give it a try!... smarteggdrop.omsi.edu
"Fail Provisional Navigation: An SSL error has occurred and a secure connection to the server cannot be made."