Big Sur

Posted on
  • Anyone having issues with connecting after upgrading to macOS Big Sur?

  • I can't connect at all at this point...

  • @user121853 Ah, so it is not me... Urgh...

  • And I have a puck that isn't working either, so I imagine it's something in the espruino ecosystem...

  • so I imagine it's something in the Espruino ecosystem...

    Honestly, I doubt it. The Espruinos work on every other Mac, Windows, Linux, Android, iOS, Chromebook device, and they worked on your Mac before you updated. So the one thing that's changed here is the Mac OS version and I think that's probably the best place to start.

    Have you tried just restarting your Mac? Sounds stupid but sometimes the Bluetooth adaptor can get confused.

    Can you tell me what exactly happens when you try to connect? Do you get any error messages? What if you look at the Chrome dev console after trying to connect?

    Also, if you go to https://www.espruino.com/ide, click the 'connect' icon up the top left, then the 'status' link, does it say anything other than 'Ok' next to 'Web Bluetooth'?

  • I just had a quick search and found this: https://apple.stackexchange.com/question­s/407338/why-does-chrome-need-access-to-­bluetooth

    Is it possible that when that window appeared you told Mac OS that you didn't want to give Chrome access to Bluetooth?

  • I am using Espruino on Mac OS X now for over 5 years and all trouble after OS X upgrade have never been based on Espruino.

  • @MaBe are you on Big Sur now, and is it working for you?

  • Not yet, but planed next week end.

  • Ok, an update on this: This post from a few minutes ago shows that at least on some Big Sur machines, it works fine: http://forum.espruino.com/comments/15677­861/

    So could you try:

    • If you blocked Chrome from accessing Bluetooth devices in a window like this, try unblocking it
    • Enabling the#experimental-web-platform-featuresflag inchrome://flags`
  • Here goes,

    When I go to:
    https://www.espruino.com/ide

    I click on connect and I get a pop-up, Web Bluetooth or Bangle Simulator, I click status and the bottom and get:

    ⚠	Web Audio	"Connect over Audio" disabled in settings
    ✓	Web Bluetooth	Ok
    ✖	Web Serial	Chrome currently requires chrome://flags/#enable-experimental-web-­platform-features to be enabled.
     	Websocket Relay	Unknown Status
    ✓	Emulator	Ok
    

    I go back and hit "Web Bluetooth" and 15 minutes later I give up and press cancel...

    Matt

  • Hi Matt,

    It looks like you haven't yet tried what was in the last post?

    But given that, it all looks as expected. So you click Web Bluetooth and absolutely nothing happens? Please could you take a look in Chrome's Settings -> More Tools -> Developer Tools then click on Console and see if there are any error messages shown?

  • Also, it looks like some people are having general bluetooth connectivity issues with Big Sur - see https://www.imore.com/how-fix-bluetooth-­connectivity-problem-macos for a fix for those.

  • Ah, so I got connected, but it is a bit of a "trial"...

    Open the banglejs app loader
    Hit Connect
    Go to the Mac's Bluetooth Widget (in the toolbar)
    Click it, scroll down to the bottom, and pick "Bluetooth Preferences"
    Remove the banglejs from the list of devices (don't disconnect it, remove it).
    The banglejs will appear as a option in the app loader connect window... Pick it and connect...

  • Great, glad it's sorted! Had you paired it in the OS beforehand?

    Or do you think it was some configuration left over from before you upgraded to Big Sur?

    I guess the https://www.imore.com/how-fix-bluetooth-­connectivity-problem-macos advice might do it - but it seems a bit heavy-handed if your method works.

  • I had not, it looks like Big Sur is a "little proactive" in connecting to devices....

  • Interesting - is it possible that you'd modified the Bangle.js Bluetooth settings to enable HID?

    I know on some OSes, once they think a device is a Bluetooth Keyboard the OS just grabs it. Having said that on Mac OS I believe Chrome tries to detect the devices that the OS is connected to - but maybe that's something that has broken in Big Sur.

  • It looks like the HID being on is an issue, it looks like that if that is on Big Sur "loves" to connect...

  • Thanks - I'll update the troubleshooting to mention that.

  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview
About

Big Sur

Posted by Avatar for user121699 @user121699

Actions