Supported Devices
Chastify connects to supported QIUI and Lockink devices over Bluetooth. Available lock, shock, and vibration controls depend on the physical model, your consent, and the app or browser you use.
Platform Support
| Platform | Connection and availability |
|---|---|
| Android app | Native Bluetooth with background-service controls. Android permissions and background restrictions affect reliability. |
| iOS app | Native Bluetooth is available in the TestFlight beta for eligible accounts. Follow the device selection flow on the iPhone; capabilities depend on the model and installed build. |
| Compatible web browser | Web Bluetooth requires browser support and device permission. Keep the page open and active for commands; background operation is unreliable. |
| iPhone or iPad browser | Do not assume the website has the native app's Bluetooth capabilities. Use the native beta's setup flow when available. |
See Android App and iOS App for installation and access. A Home Screen shortcut still uses browser capabilities.
Bluetooth Connectivity Support
Bluetooth depends on the phone, device battery, distance, permissions, and other apps using the connection. Start with the checks below. If the problem persists, report the exact failure and device details through Support; remote support cannot directly inspect your physical Bluetooth connection.
Troubleshooting
For a missing device, failed lock/unlock command, or connection that drops, see Device Connection Troubleshooting.
Supported Device Models
These are the main lock models shown in this guide. Shock capability is separate from lock/unlock support; check the controls offered for your specific device.
Cagink Pro 3QIUIShock
Cagink Metal ShakeQIUIVibration
Cagink MetalQIUI
KeypodQIUI
KeyPod MetalQIUIMetal lock safe
ThrillcageQIUIVibration and shock
Lockink BeestingLockinkShock
Lockink Electric EelLockinkShock
Lockink BlackboxLockink
Lockink Smart SubLockinkShockKeyPod Metal and Thrillcage availability depends on your account. Device Setup shows Coming soon when a model is not yet enabled for you.
Other Lockink AA-A10xx models depend on protocol compatibility. A similar name or Bluetooth discovery result does not establish that every function is supported.
Secondary Accessories
Device Setup also offers secondary accessories, including QIUI Pear Flower II and supported Lovense, We-Vibe, or Intiface connections. Follow the connection method offered for the accessory. Adding a vibration accessory does not make it a lock.
Pear Flower IIQIUIVibration and shock
HushLovenseVibration
FerriLovenseVibration
EdgeLovenseDual-motor vibration
We-VibeWe-VibeVibrationThe control panel shows whether shock requests or vibration are available and which device will receive them. When offered, a secondary vibration accessory can receive vibration as a fallback for a shock request if no primary shock device is connected. Check that routing before sending a command.
Pear Flower II shock limit
On the website and in the app, open Settings → General (or Safety & Release, depending on your settings layout), then Device Shock Settings → Pear Flower II Shock Settings after adding a Pear Flower II. Set Maximum shock level from 1 to 5 and save. The saved limit applies to all Pear Flower II devices on your account; the default is 5 until you choose a lower limit.
Chastify reduces higher shock requests to this limit, including manual, keyholder, and scheduled commands. The keyholder Allow Max policy does not override this limit. Vibration strength and shock mode are separate controls. Saving a lower limit does not stop a shock already running; use the stop control first.
As with other device shock settings, during an active shared keyholder session the limit can only be increased unless Allow shock setting changes during active sessions was enabled beforehand. Self locks do not impose this restriction.
QIUI Devices
The main QIUI models are Cagink Metal Shake, Cagink Metal, Keypod, KeyPod Metal, Thrillcage, and Cagink Pro 3. KeyPod Metal and Thrillcage must be enabled for your account before they can be selected in Device Setup.
QIUI setup includes binding the device to Chastify's platform connection. Returning to the official app may require successful unbinding; do not assume deleting browser data or uninstalling Chastify releases that binding.
Setup Options
- Android app: uses native Bluetooth and can run background controls when permissions and Android settings allow it.
- iOS app: uses native Bluetooth in the available beta. A device saved from another platform may need to be selected again on the iPhone.
- Website: uses Web Bluetooth in a compatible browser. Keep the page active; a browser connection is not a reliable background receiver.
Browser device IDs, Android Bluetooth addresses, and iPhone connection identities are different. Use the app's selection or rescan flow when switching platforms. Do not enable experimental browser flags as a routine pairing step.
Setup Steps
- Turn on Bluetooth and keep the device nearby. Close other apps connected to it.
- Open Device Setup in Chastify and choose the matching QIUI model.
- Follow the pairing and binding instructions, including any device identification requested.
- Allow the Bluetooth permissions requested by the app or browser.
- Confirm the saved device and its connection status before starting a lock session.
Unpairing a Device
Use the remove action on the device card and read its confirmation. For a QIUI device, Chastify attempts to release the platform binding before completing removal. The operation can fail or require manual help.
If removal fails, follow the retry delay shown in the app (normally 60 seconds). After repeated failures, the app can offer a manual removal request. Submit that request explicitly and follow its pending status; a failed attempt does not mean the device is already unbound.
An attached device cannot be removed through this flow during an active Hardcore session. Do not use removal and re-adding as routine troubleshooting while you depend on the device to unlock a session.
Shock and Vibration
- Cagink Metal Shake supports vibration.
- Cagink Pro 3 supports shock; Thrillcage supports vibration and shock.
- Cagink Metal, Keypod, and KeyPod Metal are lock devices without these output capabilities.
Shock or vibration needs the relevant consent and a compatible delivery path. Game actions such as shock cards or Shock on Red use the applicable game and device settings; they do not all imply maximum strength. Check the configured level, duration, and connection status.
Keyholder Shocks
A keyholder can open the wearer's available device controls from their dashboard. The panel shows device capabilities, consent, connection state, and the permitted strength and duration. A command request is not confirmation that the physical device has executed it.
If Queue undelivered shocks is enabled, commands can wait for a usable connection. The selected queue behavior decides whether they expire, wait for delivery, or must complete before normal timer unlock. Some queue settings can be locked for the session. Accepted commands can remain after a lock ends. See Shock Delivery & Queues for connection requirements, progress reports, and stopping behavior.
Closing a browser, putting the phone in the background, or disconnecting Bluetooth is not a reliable stop or cancellation action. Pending commands may be delivered later. Use the relevant stop control or Stop All Shocks, and check the device's actual state. A safety stop can leave persistent deliveries unfinished; inspect Recent shocks and use Pause queue to hold future delivery when needed.
Safety
Check which device will receive output before using its controls. Use the in-app stop controls when needed; do not infer that output has stopped solely because the app shows a lost connection. A command that has already reached the device may continue according to that device's behavior.
Lockink Devices
Lockink support depends on the model and its Bluetooth protocol. The models shown above include Beesting, Electric Eel, Smart Sub, and Blackbox. Beesting, Electric Eel, and Smart Sub have shock capabilities; Blackbox does not.
How Lockink Differs from QIUI
Lockink control uses direct Bluetooth commands rather than QIUI-style platform binding. The official Lockink app may still be able to control the device. Chastify cannot turn this connection model into exclusive server-side ownership.
Lockink App Blocker (Android)
Block Lockink App is an optional Android control that uses an accessibility service to block the official app on that phone. Persistent tampering protection adds Device Admin and overlay-based protection against uninstall or settings access. These protections apply to the configured Android phone; they do not bind the Bluetooth device against access from another phone.
When these protections are enabled during an active Hardcore session, their controls cannot be switched off for that session. Review the permissions and confirm the behavior before starting; do not rely on being able to temporarily disable the blocker.
Keep Alive System
On supported models, the device card offers keep-alive controls to help prevent sleep. These can send periodic background shocks or vibrations; they are not simply a silent connection check. Read the label and interval for your device before enabling them.
Availability and interval controls vary by model and native build. Where browser keep-alive controls are offered, they depend on that browser remaining able to run. Keep-alive does not guarantee an uninterrupted connection or prevent a device from powering off.
Battery Optimization Warning
Android battery optimization and manufacturer background restrictions can interrupt the native service. Review Chastify's battery settings and use the battery-optimization action shown in the device panel when needed. Reopen the app and check the connection after a phone restart or an app update.
Support
If keep-alive still fails, report the model, app version, phone/OS, selected interval, and whether the app was foregrounded or backgrounded. Include the time of the failure so logs can be matched to it.
Troubleshooting Keep Alive
- Check the device card's keep-alive setting, connection, next scheduled attempt, and last result where shown.
- Check Bluetooth permissions, device battery, and Android battery optimization.
- In the Android menu, open View debug logs and inspect the failure time. Auth Test checks native-service authentication; a successful result does not prove that Bluetooth is connected.
- Share relevant diagnostics through Support. Describe what physically happened as well as what the app displayed.
Exact log wording varies by build. A disconnected entry alone does not explain whether the cause was device sleep, range, another app, permissions, or the phone's background restrictions.
Shock Configuration
Device settings control the available strength and duration for game-triggered output. Keyholder controls also follow the configured keyholder policy; check whether it mirrors your settings or allows a separate level.
During an active session, enabling Allow Max allows maximum-strength keyholder output for the rest of that session. It cannot be switched back until the session ends. This setting is separate from consent and the delivery queue.
Driving Safety
The Android native service includes a motion check that can block output and request a stop when recent activity or speed readings indicate driving or cycling. It depends on permissions and usable sensor readings. Missing or stale readings do not automatically block shocks, so this is a best-effort safeguard, not a guarantee that driving will be detected.
Setup Steps
- Open Device Setup and choose the matching Lockink model.
- Keep the device nearby, close other apps using it, and select it in the scan.
- Complete any permission or connection-identity prompts.
- Confirm the saved device and available controls. Review consent, keep-alive, and blocker settings separately before using them.