Failing to connect from espruino command line

You are reading a single comment by @mozz100 and its replies. Click here to read the full conversation.

•

mozz100
On one Mac (recent Macbook pro), from the espruino command line tool, with noble installed, I can see/connect to puck.js about 50% of the time. (I updated the firmware recently to improve this). For example:
```
>$ espruino --list
Espruino Command-line Tool 0.0.30

PORTS:
  cd:47:aa:41:44:2d (Puck.js 442d)
  /dev/cu.Bluetooth-Incoming-Port
```
On another Mac (Mac mini) in the same room, running the same software, I can't ever seem to connect, and I get this when scanning (see "unknown" below) with what feels like a less than 50% success rate:
```
$ espruino --list
Espruino Command-line Tool 0.0.30

PORTS:
  unknown (Puck.js 442d)
  /dev/cu.Bluetooth-Incoming-Port
```
Why is espruino on the mac mini able to "see" puck but not work out its address, or connect to it?

I've had such limited success connecting to the thing, even with updated firmware, I'm starting to lose faith... can anyone help me understand how this might happen, and how I can fix it? I'd like to use the Mac mini (permanently on) to talk to the puck and have it control things in the real world...

About

Avatar for mozz100 @mozz100 started