Connect By Name With EZ-B V3

You’re correct: EZB Connect By Name is for EZ-B WiFi broadcasts like the EZ-B v4 / WiFi controllers, not for EZ-B v3 Bluetooth serial. The v3 does not advertise the same network broadcast, so that skill won’t detect it.

What you can do with an EZ-B v3

For EZ-B v3 over Bluetooth, ARC ultimately connects through a COM port, so the practical options are:

1) Use a fixed COM port in Windows

If you can keep the Bluetooth SPP port assigned consistently on each laptop, that’s the simplest workflow.

In Windows Bluetooth settings / Device Manager, you can sometimes reassign or keep the COM pair stable by:

• removing the device
• re-pairing it
• checking the incoming/outgoing COM ports under Ports (COM & LPT)
• making sure no other app is holding the port open

2) Use a small startup script to detect the EZ-B COM port

ARC can’t directly connect to an EZ-B v3 by Bluetooth device name the way it can by WiFi broadcast name, but you can write a script that:

• scans available COM ports
• tries the most likely one(s)
• then issues the connection command once the correct port is found

ARC’s scripting has COM.availablePorts() and related COM functions, so you can build a little auto-detect routine. The exact implementation depends on how your ARC project is set up and whether the EZ-B v3 exposes a recognizable response on the port.

Recommended workflow

If you want plug-and-play across two laptops, I’d suggest one of these:

Best simple option

• Keep the v3 paired on each laptop
• Use the same COM assignment on both machines if possible
• Save the ARC project with that COM configured

Better automation option

• Add a startup/Init script that checks available COM ports
• If your project only ever uses one Bluetooth robot controller, the script can try each port until it finds the EZ-B v3

Important limitation

There isn’t a built-in ARC feature that will resolve an EZ-B v3 by Windows Bluetooth device name and automatically bind it to the Connection skill. That name exists in Windows Bluetooth, but ARC’s connection is still COM-based for v3.

Relevant docs

• Connection troubleshooting:
  https://synthiam.com/Support/troubleshooting/Connection-Troubleshooting
• ARC port selection overview:
  https://synthiam.com/Support/ARC-Overview/port-selection
• EZ-B v3 hardware page:
  https://synthiam.com/Support/Hardware/EZ-B-v3

If you want, I can help you build the auto-COM detection script

If you tell me:

1. whether the v3 shows up as one outgoing COM port or two ports in Windows, and
2. what the exact ARC Connection skill is named in your project,

I can draft a JavaScript init script for ARC that tries the available COM ports and connects automatically.

Also, for this kind of scripting, the built-in ARC AI Assistant can be handy because it can help rewrite the script right inside ARC:
https://synthiam.com/Products/AI-Assistant