Can not connect to WeDo 2.0 with Scratch-Link on macOS 10.13.6

[swolff20]

Expected Behavior

Please describe what should happen

Actual Behavior

No connection possible

Steps to Reproduce

install and start (!) scratch link 1.3.67
use we do 2.0, try to connect using

• scratch from Safari
• standalone Scratch App 3.18.1
• connect to we do from scratch
• connection is no found (it is searching the whole time)

interesting:

• Lego Wedo App can connect to the Hub instantly from the same computer.

Operating System and Browser

macOS 10.13.6
Safari 13.1.2
scratch link 1.3.67

[swolff20]

Want to dd that Scratch 3.19.2 shows the same behavior. It is stuck in "I connect..."

Question: I have 2 Bluetooth modules on the system, the internal is deactivated (because it does not support bluetooth 4) while an external USB Bluetooth module is plugged in and chosen as the default one. Could this be a reason ?

[letsgoawaydev]

This also happened to me here but with a micro:bit. #180

[arivero]

In my case I got a random success connecting both to WeDo and Boost, but only after I accidentally also started the old Device Manager. I have been unable to reproduce :-(

[sycamedia]

I'm suddenly having trouble connecting WeDo 2.0 on macOS 11.6. I'm using Scratch 3.27.0 for desktop and Scratch Link 1.3.67. After pressing "Start searching," Scratch skips immediately to the "Check Bluetooth/Scratch Link" screen. Same problem in the browser version of Scratch (Firefox 96.0.3). Scratch Link is on, Bluetooth is on, WeDo hub is able to connect to other devices. I've tried re-installing Scratch Link and restarting the computer.

I have been able to connect WeDo successfully with this computer several times in the past, on both the standalone app and Firefox; I'm not sure what has changed.

[apple502j]

@sycamedia The TLS certificate used in Scratch Link is revoked due to terrible design flaw. This is not good, but is better than someone abusing it to intercept browser cookies.

[ZeroTech-SM]

scratch.link.wedo.2.0.mov

I attached what happed with macOS 10.13.6.
I hope this will helpful to solve the problem.