-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specific Lovense LUSH3 causing exception (and Hush and Lapis) #601
Comments
the one which doesn't work also has a couple of extra generic type characteristics, like the manufacturer name |
Maybe the "questionable assumptions" are not valid, although i don't know enough about Bluetooth to know:
|
I note that the required service is the right one (starting 553000001) and the characteristics that it finds are also the right ones. |
Now i've seen a similar thing happen with the one that works. I am on a MacBook Air 7.2, running MacOS 10.15.7 It seems unlikely but could the machine be failing to service something in time? nevertheless, the newer toys (including my Hush as well) all cause the problem during connection, while the older one does not. |
Ok hmm. I guess we've got some sort of race issue down in btleplug. I'll try to check it out soon. |
Not sure why this got closed? It's not fixed yet. I've at least made a followup on btleplug. |
Describe the bug
I have 2 Lovense Lush 3 devices. One works well with buttplug.io, but the other one causes an exception when it is scanned.
Sadly I cannot remember which I bought recently. One has the device string LVS-Lush, and the other LVS-Lush352.
The one with 352 works with your system, the other one does not.
the 352 one has one service, starting 53300001
the non working one has two services, one as above, and one starting 984227f3. this one still only advertises the 53300001 service, but that service is the second in the enumerated list of services if that makes any difference.
Expected behavior
Both should function identically.
Actual behavior
When scanning one, an exception occurs in some worker thread and the system stops.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: