JS 2 connected and stuck getting device info

Recently setup my Bangle JS2 and everything connected in Chrome Web Bluetooth fine.

Now when I try to refresh my apps its stuck on getting device info. Any suggestions? I tried restarting the watch and the computer.

1 Attachment

Have it started working?

Otherwise, connect the watch to the web ide: https://espruino.com/ide (info here: https://www.espruino.com/Web%20IDE)

Then in another tab or window, try the app loader again.

In the web ide console field (the one on the left) see if any messages appear that could help explain your problem.

Opening the Chrome devtools in the web browser (F12 or Ctrl+Shift+C) and looking at the 'Console' for any messages shown may help too - if you could copy/paste them here we might be able to help figure out what's gone wrong.

Another thing to try is to restart the watch in recovery mode: https://www.espruino.com/Bangle.js2#recovery-menu

While still in recovery mode try and connect with the App Loader, and that should work regardless of what's installed on the watch

Thank you for your suggestions @Ganblejs and @Gordon. I'm going to try both suggestions today after I finish work and will follow up with the results.

Ok I'm able to connect again thanks to @Ganblejs's https://espruino.com/ide suggestion, thank you!

It looks like the Bangle js App Loader loses track of which Web Bluetooth connection is active or cannot resume the last active connection after disconnecting or closing Chrome. Very frustrating.

Pairing again with the Bangle js App Loader just sits at 'getting device info' despite apparently trying to initiate a new Web Bluetooth connection.

With the https://espruino.com/ide app I can pair and create a new active connection and then switch back to the Bangle js App Loader where its connected correctly and loads the device info normally.

Even the https://espruino.com/ide app will throw errors if you select one of the existing dead Web Bluetooth connections but at least you can create a new connection there and get a working connection.

Thanks @Gordon for the recovery mode tip. If the watch ever gets really stuck I will try that option.

Now back to picking clocks and browsing the apps. Thank you @Ganblejs and @Gordon!

Glad you got it sorted! Very surprising about the app loader connection issues - they both use the same code and API to connect.

However maybe some app on the Bangle is outputting something when the connection first starts, and that's throwing off the App Loader (which tries to find out what apps are installed when it connects).

Maybe you could open DevTools for the App Loader, type Puck.debug=3 in the console, then try and connect and paste up what's printed to the console?