ev3dev / vscode-ev3dev-browser

Visual Studio Code extension for browsing ev3dev devices
https://marketplace.visualstudio.com/items?itemName=ev3dev.ev3dev-browser
MIT License
36 stars 11 forks source link

Bluetooth connection not working #85

Open octavmarius opened 5 years ago

octavmarius commented 5 years ago

Describe the bug I cannot connect from vs code to ev3 brick - device is not listed.

To Reproduce Steps to reproduce the behavior:

  1. start vs code
  2. boot up ev3 brick from sd card
  3. enable bluetooth (check "Powered")
  4. pear the brick with the computer
  5. in vs code - ev3dev device browser - click on "Click here to connect to a device"

Expected behavior expected to have my ev3 brick listed

Desktop (please complete the following information):

Additional context i can pear the device (ev3 brick) with my computer. i also removed (uninstalled) the ev3 brick from my computer and paired the device again with success.

image

haiyongsong1921 commented 4 years ago

@dlech Hi David, I have the same bluetooth connection issue in Mac OS. Does the ev3-browser extensions of the VSCode support for bluetooth connection. Because when I try to connect my ev3dev brick via bluetooth in VSCode, it will always throw out the handshake timeout error: "Failed to connect to ev3: Timed out while waiting for handshake." But the connection works fine via usb cable. Would you mind to share some info for this? thanks a lot

netanelbardavid commented 4 years ago

@dlech Hi David, having the same issue with windows 10. Pairing works fine but the EV3 does not appear on the device list. Tried to connect it also by its IP address but VS Code shows the "Failed to connect to ev3: Timed out while waiting for handshake" error. Thanks man

jaffarspace commented 4 years ago

@dlech Hi David, having the same issue with windows 10. Pairing works fine but the EV3 does not appear on the device list. Tried to connect it also by its IP address but VS Code shows the "Failed to connect to ev3: Timed out while waiting for handshake" error. Thanks man

Same here. Windows 10, Paired without any issue. but the device is not listing when I try to do ">ev3dev:Connect to a device" in Command Pallet. Any updates on this issue?

dlech commented 4 years ago

macOS and Windows 10 are not the same as the original issue (Windows 7), so please open a new issue with the exact steps to reproduce the problem and we will see if we can figure it out. Windows 10 and macOS are both working for me, so I need to know all of the details to see what is different.

jyouturner commented 4 years ago

FYI, I had the same problem on my Mac, but after I restarting Visual Code, I was able to connect to ev3dev from the extension/device list.

jaffarspace commented 4 years ago

macOS and Windows 10 are not the same as the original issue (Windows 7), so please open a new issue with the exact steps to reproduce the problem and we will see if we can figure it out. Windows 10 and macOS are both working for me, so I need to know all of the details to see what is different.

Thanks! reported as new issue as you suggested >> https://github.com/ev3dev/vscode-ev3dev-browser/issues/97

dlech commented 4 years ago

Because when I try to connect my ev3dev brick via bluetooth in VSCode, it will always throw out the handshake timeout error: "Failed to connect to ev3: Timed out while waiting for handshake." But the connection works fine via usb cable.

In v1.1.0, the timeout is increased from 20 to 30 seconds. It is also now configurable via a setting if that is not long enough.

vincentmohiuddin commented 4 years ago

Hi, I was having the same issue. Pairing worked but the device would not show up in VSCode. It showed up in VSCode after I went to Wireless and Networks > All Network Connections > {PC-Name} > Connect on the brick.

crucialfelix commented 1 year ago

I am able to pair from Mac (Ventura) to ev3dev, and ev3dev shows that it's connected to my mac.

But still VSCode EV3DEV DEVICE BROWSER shows it can't connect.

Oh wait ... I tried to reconnect (for like the 20th time today) and mysteriously it found a newly labelled ev3dev and it works!

Oh I wish I could tell you why it works now and didn't before. Bluetooth is a mess

solved: it was because I also had the USB connected. That always works.