-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Zalo documentation #68
Comments
BLE name: ZALO-King Tx prorocol: 0xAA 0xBB 0xCC
You can turn on just the oscillator by e.g. first sending I'm also attaching a log of all the things I was able to query via D-Bus. |
BLE name: ZALO-Jeanne Tx protocol: 0xAA 0xBB 0xCC
|
@TheHardew I picked up a King... because I have issues... (See blackspherefollower/IoSTIndex#716) I did some testing, and found that the vibrator on the King has a district tone difference between 4 and 8 (although the vibe's relativity weak so might not be noticeable to a real user). I think this probably makes the protocol easier to document, since the 1 vibe and multi-feature devices have consistent control commands. |
BLE name: ZALO-Queen
Servive UUID: 0000fff0-0000-1000-8000-00805f9b34fb
Tx Char UUID: 0000fff1-0000-1000-8000-00805f9b34fb
Tx prorocol: 0xAA 0xBB 0xCC
AA is mode:
BB controls the oscillator at the tip (values 01-08, 01 is off)
CC controls the vibrator (values 01-08, 01 is low, no off)
BB and CC should be 01, but doesn't seem to matter
BB is the pattern (01-08)
CC is the intensity (01-08)
I suspect that the same protocol applies for all Zalo devices, but I only have the Queen.
The text was updated successfully, but these errors were encountered: