There are many reasons, but the most common are:

1. Ensure your proxy machine (VM or other) has a bluetooth adapter attached to it and managed by the system (use hciconfig to check it out, you may paste the result here for further analysis)
2. Your bluetooth adapter is not enabled. Check its status with hciconfig and enable it if it was previously disabled.

from btlejuice.

Still having the same issue, proxy adapter output below:

hciconfig

hci0: Type: BR/EDR Bus: USB
BD Address: 00:19:0E:18:53:01 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:978 acl:0 sco:0 events:52 errors:0
TX bytes:2477 acl:0 sco:0 commands:52 errors:0

hci1: Type: BR/EDR Bus: USB
BD Address: 00:22:43:F8:75:85 ACL MTU: 1021:8 SCO MTU: 64:1
DOWN
RX bytes:511 acl:0 sco:0 events:23 errors:0
TX bytes:339 acl:0 sco:0 commands:23 errors:0

btlejuice-proxy

[i] Using interface hci0
[info] Server listening on port 8000
[info] Client connected
[i] Stopping current proxy.
Configuring proxy ...
[status] Acquiring target 00:0b:57:0c:61:c7

from btlejuice.

Additional info on the device:

hciconfig-hci0.txt

from btlejuice.

Okay, can you describe exactly how you start both btlejuice and btlejuice-proxy and your machines setup please ? I need more info to try to solve this problem.

from btlejuice.

I have two laptops connected via a single switch. The proxy is using the on board Bluetooth and the client is using an external Bluetooth adapter.

Output from both devices is below:

client.txt
proxy.txt

Is that output enough for you?

from btlejuice.

I managed to reproduce this bug and found the root cause: noble library de-duplicates detected devices by default so they would not be detected again during target acquisition.

I fixed the problem in the master branch but haven't made a new release yet. Is it possible for you to try this fix with a fresh install from the master branch (git clone then sudo npm install -g) or should I issue a new release through npm ?

from btlejuice.

I released two more versions since then, I hope the latest (v1.1.3) will fix your problem ;). I tested it intensively with the same setup that allowed me to reproduce this behavior.

from btlejuice.

Currently re-setting up a couple of machines as there was an issue with one of them.

Should be able to test and confirm today with any luck (assuming install works on a PI)

from btlejuice.

Looks good. :) - may have another issue now with remote device disconnects, but will do some more testing before raising it.

from btlejuice.

Great, feel free to file a new issue ;)

from btlejuice.

The issue still persists. I am getting stuck at Acquiring target line

I am using 1.1.11 version and using 2 laptops with ubuntu VMs running on both. I run the proxy in one system and run btlejuice command in the another system where I can see the list of bluetooth devices, but I don't see output in localhost:8080 page once I get connected. Can you please help me in fixing this issue

from btlejuice.