-
@Robin please can you try and find a way to update your firmware before looking too much into this? I did post some advice in one of your other threads. 1v88 has known connection issues on some devices caused by it having too low an advertising interval, but literally hundreds of things have been changed/fixed since 1v88.
@LVangelis how are you actually accessing the 0x0003 service? From the Puck itself? If so, 0x0003 should never have worked (you needed the full 128 bit UUID) - it was a bug that got fixed in 1v93. Is there a reason you couldn't just use
Bluetooth.write? It should do the same thing, but in a way that won't conflict with Espruino's built-in code.Is there any chance the Android device you're using might be attempting to connect to the Puck as well? The Puck can only have one connection at a time, so if Android were trying to connect then that could really mess up the PC's connection as well.
You are reading a single comment by @Robin and its replies.
Click here to read the full conversation.
Gordon
@Robin
Thr 2017.08.03
I too am having the same issue intermittently thrice a day over a ten hour period with the Native WebIDE. Not running anything other than LEDn.write() and setInterval()
This is with 1v88 and I haven't poked my nose into the console yet. A minor difference is that I don't always get the 'connection failure' error, just a locked app.
Windows 10.0.15063 on HP laptop with a Insignia BLE dongle. I'll update here should there be any earth shattering msgs.
Note: Also having left pane not updating issue as explained in http://forum.espruino.com/conversations/308441/
Also, I've only ever had to pair the Puck one time. Disconnect-Connect is needed, but never get the pairing dialog on subsequent tries.