Skip to main content

QIUI Devices

QIUI devices use a high-security binding flow. When a device is bound in Chastify, the QIUI app cannot unlock it during an active session.

Supported devices: Cagink.metal.shake, Cagink.metal, Keypod 1, and Cagink Pro 3.

Setup Options​

You can add a device using the website (Web BLE) or the Android app.

  • Website: Stays connected for the command only or until JS execution stops when website tab goes into background
  • Android app: uses a persistent background connection unless the device enters power save mode (varies by model).

Website setup may require the MAC address because the browser exposes only a sandboxed ID. You can enable chrome://flags/#enable-experimental-web-platform-features and watch for manufacturer data advertisements that may include the Bluetooth MAC address, but devices do not always broadcast it.

Setup Steps​

  1. Open Device Setup in Chastify.
  2. Select your QIUI device.
  3. Follow the pairing instructions.
  4. Confirm the device status in the dashboard.

Device Unpairing​

To unbind a device and return to the QIUI app, click the remove icon on the device card. This process is semi-automatic because there is no official unpairing API, and it can fail in rare cases.

If it fails:

  • After the first failure, wait 60 seconds before trying again.
  • After the second failure, you can submit a manual admin task for handling.

Shock and Vibration​

Cagink.metal.shake supports vibration. Cagink Pro 3 supports shock.

Card game options include shock cards and Shock on Red. These trigger a maximum strength shock or vibration when a red or shock card is drawn, assuming the browser connection is approved or the Android app is connected. In the Android app, ensure the device is connected in the menu for reliable control.

Keyholder Initiated Shocks​

When the Android app connects or disconnects, it sends a socket event so the device appears in the keyholder dashboard. The keyholder can open the shock/vibration UI from the device avatar.

  • Shock duration: 30 seconds minimum, up to 10 minutes.
  • Duplicate commands are blocked and de-duplicated in Redis.
  • Device controls unlock again after the timer ends.

When the wearer Android app receives the command in the background service, shocks execute on the device.

Safety​

Wearers can stop shocks or vibration at any time by disconnecting the device in the menu or powering the device off.