Device Support Request: metaXsire Venus (sold as "Boa") — BLE name LLWNS
Device Info
Brand/App: metaXsire / Sexverse (Sciencinfinity LTD)
Device name in app: Venus
Retail/marketing name: Boa
Capabilities: Vibration + undulation/oscillation (2-3 actuators)
App: metaXsire (iOS/Android)
BLE Advertisement
Bluetooth name: LLWNS
What we tried
Connected the device using the sexverse-v3 protocol via user device config (UDCF). Intiface Central successfully connects over BLE, but the device does not respond to sexverse-v3 commands (tested vibrate at 100% intensity — no physical output). This suggests the Boa uses a different command format than existing Sexverse devices (Tay, Nolan, etc.), despite sharing the same companion app.
The existing sexverse-v3 devices use service 0000FFF0 with tx 0000FE02. The Boa uses entirely different service UUIDs (see below), which may indicate a newer protocol revision.
Services & Characteristics (via nRF Connect on Android)
Standard services: Generic Access (1800), Generic Attribute (1801)
Service 1: 0000FFAA-0000-1000-8000-00805f9b34fb
Characteristic UUID (short) Properties Notes
AA01 0000AA01-... Read Read value: BB01 1000 0000 0000 0000 0000 0000 0000 0000 00
AA02 0000AA02-... Write Without Response Likely TX
AA03 0000AA03-... Write
AA04 0000AA04-... Notify Read value: BB02 0115
Service 2: 0000FFA0-0000-1000-8000-00805f9b34fb
Characteristic UUID (short) Properties
FFA1 0000FFA1-... Write Without Response
FFA2 0000FFA2-... Read, Notify
Service 3: 0000AE00-0000-1000-8000-00805f9b34fb
Characteristic UUID (short) Properties
AE01 0000AE01-... Write Without Response
AE02 0000AE02-... Notify
Additional service observed
24F508AB-983B-D03D-B933-63D7B1A1727B (custom UUID, possibly firmware/OTA)
Notes
Device has at least two physical functions (vibrate + undulate/oscillate). Three custom BLE services may correspond to separate actuators or one may be firmware/config.
All three custom services follow the same pattern: Write Without Response (TX) + Notify or Read/Notify (RX).
BLE name confirmed by connecting through the metaXsire app and checking Android system Bluetooth settings.
Device is not on the IoST Index.
Successfully connects via Intiface Central using sexverse-v3 protocol with custom UDCF, but does not respond to sexverse-v3 commands — likely needs protocol analysis of the actual command bytes the metaXsire app sends.
Device Support Request: metaXsire Venus (sold as "Boa") — BLE name LLWNS
Device Info
Brand/App: metaXsire / Sexverse (Sciencinfinity LTD)
Device name in app: Venus
Retail/marketing name: Boa
Capabilities: Vibration + undulation/oscillation (2-3 actuators)
App: metaXsire (iOS/Android)
BLE Advertisement
Bluetooth name:
LLWNSWhat we tried
Connected the device using the
sexverse-v3protocol via user device config (UDCF). Intiface Central successfully connects over BLE, but the device does not respond to sexverse-v3 commands (tested vibrate at 100% intensity — no physical output). This suggests the Boa uses a different command format than existing Sexverse devices (Tay, Nolan, etc.), despite sharing the same companion app.The existing sexverse-v3 devices use service
0000FFF0with tx0000FE02. The Boa uses entirely different service UUIDs (see below), which may indicate a newer protocol revision.Services & Characteristics (via nRF Connect on Android)
Standard services: Generic Access (1800), Generic Attribute (1801)
Service 1:
0000FFAA-0000-1000-8000-00805f9b34fbCharacteristic UUID (short) Properties Notes
AA01
0000AA01-...Read Read value:BB01 1000 0000 0000 0000 0000 0000 0000 0000 00AA02
0000AA02-...Write Without Response Likely TXAA03
0000AA03-...WriteAA04
0000AA04-...Notify Read value:BB02 0115Service 2:
0000FFA0-0000-1000-8000-00805f9b34fbCharacteristic UUID (short) Properties
FFA1
0000FFA1-...Write Without ResponseFFA2
0000FFA2-...Read, NotifyService 3:
0000AE00-0000-1000-8000-00805f9b34fbCharacteristic UUID (short) Properties
AE01
0000AE01-...Write Without ResponseAE02
0000AE02-...NotifyAdditional service observed
24F508AB-983B-D03D-B933-63D7B1A1727B(custom UUID, possibly firmware/OTA)Notes
Device has at least two physical functions (vibrate + undulate/oscillate). Three custom BLE services may correspond to separate actuators or one may be firmware/config.
All three custom services follow the same pattern: Write Without Response (TX) + Notify or Read/Notify (RX).
BLE name confirmed by connecting through the metaXsire app and checking Android system Bluetooth settings.
Device is not on the IoST Index.
Successfully connects via Intiface Central using
sexverse-v3protocol with custom UDCF, but does not respond to sexverse-v3 commands — likely needs protocol analysis of the actual command bytes the metaXsire app sends.