Leap motion device not recognised by Leap motion software despite going through the troubleshooting

[poom]

Dear all,

I'm currently having trouble getting my leap motion device to work with my MBP (mid 2012 osx 10.13.4). I've had the leap motion working once or twice but for some reason it's not working anymore.

• The Green LED on the Leapmotion is on, the tray icon is not green and the software doesn't recognize that the device is plugged in.

• The Leap Motion works on other laptops (even on mine when running windows 10 in bootcamp(after reinstalling the drivers))

• OSX recognises the leap motion device that is plugged in (when checking the USB ports (There even is an OSX popup message in the right top corner)

• Reinstalling leap motion, rebooting, and rebooting in safe mode didn't work

• I've tried the firmware reset but even that did not work

I'm kinda running out of possible solutions that I can think of that could be a solution to this problem.
Can somebody help me out please?

I'm running Version: 2.3.0+31543

[jhung]

The latest version of the Leap Motion software on Macs is 2.3.1

Try updating to the latest version, either through the automatic update from the Leap Motion Control Panel or by downloading the latest version from the bottom of the download page at www.leapmotion.com/setup

If the issue persists, open up the software log from the Troubleshooting tab in the Leap Motion Cotrol Panel and send over the contents.

If it mentions something about the leap service not running, you can try manually restarting it by following the instructions here: https://support.leapmotion.com/hc/en-us/articles/223784008-How-to-Manually-Restart-Leap-Core-Services

[poom]

Thanks for your suggestions,

I've updated to the 2.3.1+31549 version.
I've relaunched the leapd manually and still no success

Software log:
[11:30:58] [Info] WebSocket server started
[11:30:59] [Info] Secure WebSocket server started
[11:31:47] [Info] Connected to Leap Daemon
[11:33:24] [Warning] Leap Daemon is not running
[11:33:31] [Info] WebSocket server started
[11:33:31] [Info] Secure WebSocket server started
[11:33:31] [Info] Connected to Leap Daemon

Still I can't get the device to work it's driving me crazy I hope there is a solution to this illogical problem.

[jdonald]

Starting with macOS 10.13 High Sierra or possibly earlier, the system process VDCAssistant has tended to lock up the Leap Motion controller. You'll thus see it among your USB devices but the Leap Motion daemon cannot talk to it during this period.

Often it eventually times out after a couple minutes and leapd gets ahold, but there is no guaranteed wait time and this can certainly be frustrating.

One workaround is to pause VDCAssistant with the command:

sudo killall -SIGSTOP VDCAssistant

and then plug in your Leap Motion controller. Please try that out and see if it at least gets more information to appear in the log.

Note that you won't be able to use your built-in webcam while VDCAssistant is paused. To resume when done using your Leap, run the same command except with SIGCONT (continue).

[poom]

I tried your suggestion but sadly it didnt change a thing.

[13:57:01] [Info] WebSocket server started
[13:57:01] [Info] Secure WebSocket server started
[14:00:29] [Info] Connected to Leap Daemon

I hope this information helps someone to find a solution to this problem.

Kind regards,

Pim

[orbitus007]

https://leapmotion.app.box.com/s/lw8j5c2erzj67e4eunlq69bzmlpa8er3

I just had the same issues.. try these steps:

1.Quit the leap motion controller app
2.install the app at the location above as tech support instructed me to.
3. Shutdown your computer completely, and then startup again. You can try just restart but I did full shutdown.
4. Before plugging in my device I used "sudo killall -SIGSTOP VDCAssistant" and now the device plugs in and the infrared lights turn on 250 ms after plugging in.

I am on the latest mac osx 10.13.5 beta 5

I got super responsive results after this!
!!!

[jhung]

This was a fix specific to your issue with the sharpness error and will most likely not resolve the other user's issue

[poom]

Yup even though I was sceptical I tried it, didn't work as Jhung expected.