Skip to main content

Lovense

Introduction​

Lovense has been manufacturing toys since 2011.

Bluetooth Details​

While all lovense toys use the same protocol, they can communicate over bluetooth differently, depending on when they were released.

Bluetooth 2.0 Toys​

The first toys released by Lovense used both Bluetooth 2.0 SPP (emulating a serial port) and Bluetooth LE. This was most likely due to the sparse mobile support of BTLE when they were released.

These toys include:

  • Max
  • Nora

When paired with a system via Bluetooth 2.0, these toys identify as a serial port. These toys are also capable of using Bluetooth 4.0, as outlined in the next section.

Bluetooth LE Toys​

Starting with the Lush, all toys released by Lovense use only Bluetooth LE.

These toys have GATT characteristics to mimic the RX/TX setup of the serial port style control of the old toys. The GATT service and characteristic IDs differ between different toy firmware versions.

It's difficult to keep a current list of exact Lovense device names and service/characteristic UUIDs, as they tend to change rapidly on firmware updates. The following rules can be used for finding and connecting to Lovense toys.

Lovense toy names always start with "LVS-". What comes after that varies depending on when the toy was released. Early toys used names involving the single character identifier, like "LVS-A011", while newer toys use the full product name, like "LVS-Edge36". The last 2 numbers denote the firmware version the toy is running.

Lovense toys usually have one of 3 service ID formats:

0000fff0-0000-1000-8000-00805f9b34fb
6e400001-b5a3-f393-e0a9-e50e24dcca9e
XY300001-002Z-4bd4-bbd5-a6920e4c5653

The first two service IDs are static, and represent the service IDs used by first and second generation Lovense toys. The 3rd service ID can vary, with

  • X usually being 0x4 or 0x5
  • Y being any number 0x0-0xf
  • Z usually being 0x3 or 0x4

While some bluetooth APIs can wildcard services, others like WebBluetooth require an exact service UUID to connect. For these instances, it's recommended to just generate out all 32 variations of the last service, for a total of 34 services, to use with the optionalServices portion of a WebBluetooth connection filter.

To identify the type of toy after connecting, it is recommended to use the DeviceType; message, outlined below. This will return a device model identifier.

Protocol​

Commands for Lovense toys follows these 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.
  • Commands that do not return a context specific value will return "OK;" on success, "ERR;" on error.

Command List​

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.

Get Device Information​

Returns toy model type, firmware version, and bluetooth MAC address, as a colon delimited list

Availability: All toys

Command Format

DeviceType;

Return Example

C:11:0082059AD3BD;

Denotes Nora toy, running v1.1 firmware, BT Addr of 00:82:05:9A:D3:BD

Model Types:

ModelType Letter
NoraA or C
MaxB
AmbiL
LushS
HushZ
DomiW
EdgeP
OsciO

Get Battery Level​

Returns the battery level of the toy as an integer percentage from 0-100.

Availability: All toys

Command Format

Battery;

Return Example

85;

Denotes 85% battery remaining.

Turn Off Power​

Turns off power to the toy.

Availability: All toys

Command Format

PowerOff;

Return Example

OK;

Device Status​

Retreive the status of the toy.

Availability: All toys

Command Format

Status:1;

Return Example

2;

Status Codes:

  • 2: Normal

Set Vibration Speed​

Changes the vibration speed for the toy. Takes integer values from 0-20.

Availability: All toys

Command Format

Vibrate:10;

Sets vibration speed to 10 (50%).

Return Example

OK;

Configure Toy Settings​

There are settings configurable through the Lovense Remote application which have read and write commands.

AutoSwith​

Configures options labelled as follows in Lovense Remote:

  • Turn off the toy when there is an accidental bluetooth disconnection
  • Toy will go to last level when it reconnects

Note both options are marked Beta. "Turn off" appears to mean disable vibration.

The read command returns 0 or 1; the write command accepts "Off" and "On".

Availability: All toys? Confirmed: Domi, Hush, Lush 2

Command Format

GetAS;

Read "AutoSwith" options.

Return Example

AutoSwith:0:1;

Indicates "turn off on disconnect" disabled; "last level on reconnect" enabled.

Command Format

AutoSwith:On:Off;

Set AutoSwith features to On and Off, respectively.

Return Example

OK;
Light​

Labelled "Enable/Disable LED" in Lovense Remote. Not shown in Lovense Remote for Domi.

Controls power/connection LED.

The read command returns 0 or 1; the write command accepts "off" and "on".

Availability: All toys? Confirmed: Domi, Hush, Lush 2

Command Format

GetLight;

Read Light setting.

Return Example

Light:1;

LED enabled

Command Format

Light:off;

Disable power/connection LED

Return Example

OK;
ALight​

Labelled "Enable/Disable Lights" in Lovense Remote.

Availability: Domi

Controls ring of white LEDs on Domi.

The read command returns 0 or 1; the write command accepts "Off" and "On".

Command Format

GetAlight;

Read ALight setting.

Return Example

Alight:1;

Lights enabled

Important: note different capitalization between read and write commands

Command Format

ALight:Off;

Disable lights or power LED

Return Example

OK;

Preset Levels​

The Domi allows customization of the low, medium, and high levels selectable using the hardware buttons. The raw levels are the same integer values used for the Vibrate command.

Availability: Domi

Command Format

GetLevel;

Fetch configured levels.

Return Example

1,9,20;

Vibration levels. Indicates 1 for low, 9 for medium, 20 for high. This is the factory default.

Command Format

SetLevel:3:16;

Set High to level 16. 1, 2, and 3 as the first argument refer to low, medium, and high, respectively.

Return Example

OK;

Start Accelerometer Data Stream​

Starts a stream of accelerometer data. Will send constantly until stop command is sent. Incoming accelerometer data starts with the letter G, followed by 3 16-bit little-endian numbers.

Availability: Max, Nora

Command Format

StartMove:1;

Return Example

GEF008312ED00;

Denotes [0x00EF, 0x1283, 0x00ED] accelerometer readings.

Stop Accelerometer Data Stream​

Stops stream of accelerometer data.

Availability: Max, Nora

Command Format

StopMove:1;

Return Example

OK;

Change Rotation Direction​

Changes the direction of rotation for the toy.

Availability: Nora

Command Format

RotateChange;

Return Example

OK;

Set rotation speed​

Changes the rotation speed of the Nora toy. Takes integer values from 0-20.

Availability: Nora

Command Format

Rotate:10;

Sets rotation speed to 10 (50%).

Return Example

OK;

Set Absolute Air Level​

Changes the inflation level of the Max toy. Takes integer values from 0-5.

Availability: Max

Command Format

Air:Level:3;

Sets air level to 3 (60%).

Return Example

OK;

Set Relative Inflation Level​

Inflates relative to current level, i.e. if currently inflation level is 3, and "Air:In:1;" is sent, will inflate to 4.

Availability: Max

Command Format

Air:In:1;

Sets air level to 1 level more inflated than it was.

Return Example

OK;

Set Relative Deflation Level​

Deflates relative to current level, i.e. if currently inflation level is 3, and "Air:Out:1;" is sent, will deflate to 2.

Availability: Max

Command Format

Air:Out:1;

Sets air level to 1 level deflated than it was.

Return Example

OK;

Get Production Batch Number​

Returns the production batch number for this device. This digits appear to correspond to a YYMMDD date during manufacture.

Availability: All toys? Confirmed: Lush 2, Hush, Domi.

Command Format

GetBatch;

Return Example

190124;

Count Programmed Patterns​

List the indexes of the patterns that are currently programmed into the device. The maximum number of patterns in 10, so each index will always be a single digit.

Availability: Lush 2, Domi

Command Format

GetPatten;

Return Example

P:01234;

This return tells us that there are currently five patterns programmed on the device, with indicies 0 through 4.

View Programmed Pattern​

Returns a pattern that is currently programmed into the device.

Each pattern is represented as a series of digits from 0 to 9, each indicating the vibration level for one half-second of the pattern. (This is different than the 0-20 scale used by the Vibrate command.)

The response is split into multiple messages, each containing up to 12 digits (6 seconds). Each response has a prefix indicating the pattern index, the number of parts in the response, and the index of the response.

For the Domi, the pattern length must be between 5 and 50 seconds, so the response will use a maximum of 9 messages, so the part count and indicies will always be a single digit.

For the Lush 2, the part count and indicies are padded to always use two digits.

Availability: Lush 2, Domi

Command Format

GetPatten:4;

Domi response using one-digit part indices:

Return Example

P4:1/5:000042003720;
P4:2/5:000002436658;
P4:3/5:997339993001;
P4:4/5:291111115111;
P4:5/5:1110000000;

Lush 2 response using two-digit part indices:

Return Example

P4:01/01:346797643;

Run Programmed Patern​

Starts running a programmed pattern on a loop. Takes an positive integer pattern index to start running it, or 0 to stop running the pattern.

While Domi is able to take any pattern index, from 0 to 10, Lush 2 only seems to be able to take indices from 0 to 4. Other toys have not been tested.

Availability: Lush, Hush, Ambi, Domi, Edge, Osci

Command Format

Preset:8;

Return Example

OK;

The applications and repositories below contain implementations of the Lovense communications protocol, or have relevant information about the hardware/firmware.