#hardware #usb #max #toy #lovense #nora #lush

bin+lib lovesense

Rust library for accessing Lovense Hardware (Max, Nora, Lush, Hush, etc...)

1 unstable release

Uses old Rust 2015

0.1.0 Jul 23, 2016

#29 in #max

BSD-3-Clause

13KB
125 lines

lovesense

lovesense is a library for controlling Lovense sex toys, such as the Max, Nora, and Lush. The library allows users to control all aspects of the toy (vibration/rotation/inflation, depending on the toy), as well as retrieving information like device type, status, battery level, and accelerometer readings.

The library is currently available in the following languages:

If you need an implementation in a language not currently supported by lovesense, please file an issue on the github tracker of the relevant project.

Please note that this project has no direct relation to the Lovense company. These drivers have been developed/supported by the open source community. Lovense has had no direct participation in this project and most likely will not be able to answer questions or provide support for any of the Lovesense drivers.

If you require commercial support for programming for Lovense products, it is recommended you go through the Official Lovense Developer Program.

Rust Library

The Rust version of lovesense requires the serial-rs library, which is listed in the Cargo file.

C Headers

Once the Rust library is compiled, C headers are included that allow the library to be linked and used from C/C++. See in the "include" directory.

Protocol Explanation

Lovense toys connect via bluetooth, and then use the Serial Port Profile (SPP) to communicate with the host. This means that the toys are exposed as either COM Ports (windows) or tty devices (posix/bsd/etc).

Protocol Rules

  • Commands and replies are strings, using semicolons to mark their end.
  • All commands start with a command identifier word, then possibly either specifiers or levels, delimited by colons. e.g. "Vibrate:5;" would set vibration to 5.
  • Replies are in the context of the command (i.e. sending "Battery;" will just return a number, like "85;"), but can still be colon delimited lists.

Command Table

The following is the known command table for all toys. Anything send or received over the serial port is in quotes to denote communication, but should not be sent using quotes if you are implementing your own version of this protocol. Commands with ":x" mean that the x should be replaced with a number, the range of which is mentioned in the description.

Command Description Expected Return
"DeviceType;" Returns toy type (A: Lush, B: Max, C: Nora), Firmware version, and bluetooth MAC address, as a colon delimited list String, e.g. "C:11:0082059AD3BD;"
"Battery;" Returns battery level of toy Number, e.g. "85;" meaning 85% battery left
"PowerOff;" Powers the device off "OK;"
"Status:1;" Shows device status. 2 is "normal" "2;"
"StartMove:1;" Starts accelerometer data stream. String, that always starts with 'G', followed by 3 16-bit little-endian numbers e.g. "GEF008312ED00"
"StopMove:1;" Stops accelerometer data stream "OK;"
"RotateChange;" Changes the direction of rotation for the stimulator on the Nora toy. "OK;"
"Vibrate:x;" Sets vibration level for toy. Range seems to be 0-20. "OK;"
"Rotate:x;" Sets rotation speed for Nora toy. Range seems to be 0-20. "OK;"
"Air:Level:x;" Sets absolute air level for Max toy. Range seems to be 0-5; "OK;"
"Air:In:x;" Sets relative inflation level, i.e. if currently inflation level is 3, and "Air:In:1" is sent, will inflate to 4 "OK;"
"Air:Out:x;" Sets relative deflation level, i.e. if currently inflation level is 3, and "Air:Out:1" is sent, will inflate to 2 "OK;"

Thanks

Thanks to PenTest Partners for doing most of the heavy lifting and documenting it in their blog. This library is mostly just an implementation of the information found in that post.

License

tl;dr: BSD License

Copyright (c) 2016, Metafetish Project All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  • Neither the name of the authors nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY The Authors ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL The Authors BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE

Dependencies

~2MB
~30K SLoC