Add New Fluffer Devices
I need to access the buttplu platform. When I scan my Bluetooth device using the Intiface Central app, it can be detected, but it cannot be recognized. How can I add my new device (Fluffer)? The information related to my device is as follows:
Fluffer Playmate: defaults: name: Fluffer Playmate features: - feature-type: Vibrate actuator: step-range: - 0 - 100 messages: - ScalarCmd - feature-type: Rotate actuator: step-range: - 101 - 200 messages: - RotateCmd communication: - btle: names: - MB Controller - MBO - MB Link 201 - MBB manufacturer-data: - company: 0x4A69 data: - 74 - 104 services: 53300031-0060-4BD4-BBE5-A6920E4C5663": tx: 53300032-0060-4BD4-BBE5-A6920E4C5663 rx: 53300033-0060-4BD4-BBE5-A6920E4C5663 txdata: 53300034-0060-4BD4-BBE5-A6920E4C5663 3345C2F0-6F36-45C5-8541-92F56728D5F3: rxotaversion: 3345C2F1-6F36-45C5-8541-92F56728D5F3 rxotastate: 3345C2F2-6F36-45C5-8541-92F56728D5F3 txotadata: 3345C2F3-6F36-45C5-8541-92F56728D5F3 rxotapubkey: 3345C2F4-6F36-45C5-8541-92F56728D5F3 Fluffer Toy: defaults: name: Fluffer Toy features: - feature-type: Vibrate actuator: step-range: - 0 - 100 messages: - ScalarCmd - feature-type: Rotate actuator: step-range: - 101 - 200 messages: - RotateCmd communication: - btle: names: - Fluffer 1 - Fluffer 2 manufacturer-data: - company: 0x4A69 data: - 74 - 105 services: 53300031-0060-4BD4-BBE5-A6920E4C5663": tx: 53300032-0060-4BD4-BBE5-A6920E4C5663 rx: 53300033-0060-4BD4-BBE5-A6920E4C5663 txdata: 53300034-0060-4BD4-BBE5-A6920E4C5663 3345C2F0-6F36-45C5-8541-92F56728D5F3: rxotaversion: 3345C2F1-6F36-45C5-8541-92F56728D5F3 rxotastate: 3345C2F2-6F36-45C5-8541-92F56728D5F3 txotadata: 3345C2F3-6F36-45C5-8541-92F56728D5F3 rxotapubkey: 3345C2F4-6F36-45C5-8541-92F56728D5F3 Fluffer Massager: defaults: name: Fluffer Massager features: - feature-type: Vibrate actuator: step-range: - 0 - 255 messages: - ScalarCmd - feature-type: Rotate actuator: step-range: - 0 - 255 messages: - RotateCmd communication: - btle: names: - MB Controller services: FFF0: tx: FFF6 rx: FFF6
It's something we're working on right now.
It's something we're working on right now.
I need to change the relevant information of the device, thank you.
Fluffer Playmate:
defaults:
name: Fluffer Playmate
features:
- feature-type: Vibrate
actuator:
step-range:
- 0
- 100
messages:
- ScalarCmd
- feature-type: Rotate
actuator:
step-range:
- 101
- 200
messages:
- RotateCmd
communication:
- btle:
names:
- FDPLAYMATE
- PLAYMATE
- RELAY
- BT-FDRELAY
manufacturer-data:
- company: 0x4A69
data:
- 74
- 104
services:
53300031-0060-4BD4-BBE5-A6920E4C5663":
tx: 53300032-0060-4BD4-BBE5-A6920E4C5663
rx: 53300033-0060-4BD4-BBE5-A6920E4C5663
txdata: 53300034-0060-4BD4-BBE5-A6920E4C5663
3345C2F0-6F36-45C5-8541-92F56728D5F3:
rxotaversion: 3345C2F1-6F36-45C5-8541-92F56728D5F3
rxotastate: 3345C2F2-6F36-45C5-8541-92F56728D5F3
txotadata: 3345C2F3-6F36-45C5-8541-92F56728D5F3
rxotapubkey: 3345C2F4-6F36-45C5-8541-92F56728D5F3
Fluffer Toy:
defaults:
name: Fluffer Toy
features:
- feature-type: Vibrate
actuator:
step-range:
- 0
- 100
messages:
- ScalarCmd
- feature-type: Rotate
actuator:
step-range:
- 101
- 200
messages:
- RotateCmd
communication:
- btle:
names:
- MB Controller
- MBO
- MB Link 201
- MBB
- G2G
- FDG2G
- FDPR
- GTHING
- FDGTHING
manufacturer-data:
- company: 0x4A69
data:
- 74
- 105
services:
53300031-0060-4BD4-BBE5-A6920E4C5663":
tx: 53300032-0060-4BD4-BBE5-A6920E4C5663
rx: 53300033-0060-4BD4-BBE5-A6920E4C5663
txdata: 53300034-0060-4BD4-BBE5-A6920E4C5663
3345C2F0-6F36-45C5-8541-92F56728D5F3:
rxotaversion: 3345C2F1-6F36-45C5-8541-92F56728D5F3
rxotastate: 3345C2F2-6F36-45C5-8541-92F56728D5F3
txotadata: 3345C2F3-6F36-45C5-8541-92F56728D5F3
rxotapubkey: 3345C2F4-6F36-45C5-8541-92F56728D5F3
Fluffer Massager:
defaults:
name: Fluffer Massager
features:
- feature-type: Vibrate
actuator:
step-range:
- 0
- 255
messages:
- ScalarCmd
- feature-type: Rotate
actuator:
step-range:
- 0
- 255
messages:
- RotateCmd
communication:
- btle:
names:
- MB Controller
services:
FFF0:
tx: FFF6
rx: FFF6
Huh, do you have the control protocol for the device? That's what we're missing and still working on.
Huh, do you have the control protocol for the device? That's what we're missing and still working on.
control protocol for the device? What does it look like? Can you give an example or something?