sam detweiler

so, it doesn't look like discover is THE culprit (altho it adds 3/4 second to each device cycle) charts of the processing for each device     ...

@NunoSav the devices are advertising at 100ms interval.

yeh, I think there is a problem in IOS locationservices with concurrent connects. I haven't tried to build this on android.

here is the trace (captured over socket.io to my desktop) ```text client sent=1632068833020 start scanning client sent=1632068833022 scan for BluetoothLE client sent=1632068833034 Scanning for devices (will continue to scan until...

so, I changed all my promise ```javascript .then( ()=>{} // resolve handler ) .catch( ()=>{} // error handler ) ``` to ```javascript .then( ()=>{}, // resolve handler ()=>{} // reject...

still seeing occasional connect not returning. is there a timeout option?

i put the .catch back on to see if the promise is failing and get the weird error ``` client sent=1632333894495 second promise failed=TypeError: undefined is not a function (near...

i am back to trying to deal with connect not returning.. never mind, i re-read the doc, and it clearly says this will happen AND you the developer using this...

nor on Android 11 production (Samsung 8+ S20 FE 5G)

never mind, docker restart BlueIris