buttplug
buttplug copied to clipboard
Use Vibrate:X instead of VibrateN:X when Lovense gets VibrateCmd with same speeds
This is an optimization bug more than anything, and it's only for the Edge at the moment.
Lovense "Vibrate:X" causes all motors to vibrate, while "Vibrate1X:", "Vibrate2:X", etc cause single motors to vibrate. If we get a VibrateCmd with 2 subcommands, each of which have the same speed, we can just send Vibrate:X over. Saves us a bluetooth exchange.
Moving from buttplug-csharp to buttplug-rs just to make sure I check for this in that code base.
We have a nice way to test this now so it'd be nice if we can get it in.