For those still interested, I confirmed a good workaround, that one of my students found. Turns out the newer Mac OSs (like Monterey and Ventura) think the leap is a usb webcam, and a mac process grabs hold of the device, not allowing leapd to connect to it. That process is called UVCAssistant. You can find it if you grep for it:
ps -aex | grep UVCAssistant
You must kill this process to let leapd have a chance to connect to the leapmotion with:
sudo killall -9 UVCAssistant
There is a bit of a cat-and-mouse game here. As soon as you kill it, another will spawn. So you need to keep killing it quickly a few times in a row until you see the leap software connect (ie, icon in toolbar turns green).
I run the killall command and then up-arrow / return a few times quickly which seems to do the trick.