Skip to main content

Device Connection Troubleshooting

Bluetooth reliability depends on the phone or computer, app or browser, permissions, battery, distance, and whether another app is already connected. Start by identifying whether you are using the Android app, iOS beta, or website; their connection methods differ.

Device Connection Troubleshooting

Stop and check pending commands first

Closing a browser or disconnecting Bluetooth does not reliably stop physical output or cancel queued shocks. Use the relevant stop control or Stop All Shocks before troubleshooting, and check the physical device. A safety stop can leave persistent work pending; use Pause queue to hold upcoming deliveries while investigating. See Shock Delivery & Queues.

Quick Checks​

  1. Check whether Chastify shows a connection error, permission error, or pending command. Note the exact message.
  2. Move the phone or computer close to the device and check that the device is awake and sufficiently charged.
  3. Make sure Bluetooth and Chastify's Bluetooth/Nearby Devices permission are enabled.
  4. Close other apps or browser tabs connected to the device, including its official app.
  5. Retry the connection from Chastify. If it still fails, toggle the phone's Bluetooth or power-cycle the device using its normal controls, then reconnect.

A displayed battery percentage does not prove there is enough power to operate the lock mechanism. Do not delete a device record, clear app data, or factory-reset hardware as a first troubleshooting step.

Android App​

The Android app uses a native service for background device control. If it cannot connect:

  1. Open Chastify and confirm that the correct device is selected.
  2. Check Bluetooth/Nearby Devices permissions and the saved Bluetooth address.
  3. Reconnect from the device card if that action is available.
  4. If foreground control works but background control fails, review Chastify's battery optimization and the phone manufacturer's background restrictions.
  5. Open View debug logs in the menu and press Auth Test to check whether the native service can authenticate with the server. This tests server access, not the physical Bluetooth connection.
  6. After stopping output and checking queued commands, restart Chastify or the phone if the connection remains stuck. Reopen the app and confirm reconnection afterward.

For installation and native updates, see Android App.

iOS App​

The iOS TestFlight beta uses a native Bluetooth identity that differs from an Android address or browser device ID.

  1. Check Bluetooth and Chastify's Bluetooth permission in iOS settings.
  2. Open the saved device in Chastify. If Select your device to finish iPhone setup appears, use Select device and choose the matching physical device.
  3. Finish that selection; scanning alone does not save the connection identity.
  4. Keep the app open while confirming the first connection. Close other apps using the device.
  5. Check TestFlight for a newer native build if setup or supported controls fail.

When reporting a problem, say whether it occurs with Chastify open, after backgrounding it, or after reopening it. Do not assume every Android control is available in the installed iOS build.

Web BLE Browser​

Web Bluetooth needs a compatible browser and permission for the selected device. Browser background suspension can interrupt control.

  1. Keep the Chastify tab open and active while connecting and sending commands.
  2. Start pairing from a fresh button click; the browser picker requires user interaction.
  3. If permission was lost or site data was cleared, select the device again in Chastify's pairing flow.
  4. Close other connected tabs and apps. After checking output and queues, reload the page or restart the browser if the picker is stuck.
  5. If Web Bluetooth is unavailable in that browser, use an available native app. A Home Screen shortcut does not add native Bluetooth support.

See Chrome's Web Bluetooth documentation for browser requirements. Browser pairing permission is separate from the device record saved on your Chastify account.

Device Picker Does Not Show the Device​

  • Confirm the physical model matches the setup option you selected.
  • Wake the device, move it close, and check its battery.
  • Close the official app and disconnect any other phone using it.
  • Check Bluetooth and app permissions, then scan again from Chastify.
  • If needed, restart the app or power-cycle the device before retrying.

Discovery does not prove that every function of a similarly named device is supported. Check Supported Devices.

Command Starts but Fails​

  1. Check battery, distance, and whether another app took the connection.
  2. Read the command result and check the physical lock state. Do not treat a timeout as proof that the lock did not move.
  3. Reconnect and retry once only after checking the current state and any pending commands.
  4. If browser control repeatedly fails, try the available native app with the correct device identity.
  5. Report repeated failures with the exact action and time instead of repeatedly submitting commands.

A queue entry, connection indicator, and physical execution are different states. For a pending shock, inspect its delivery status and queue settings before submitting another one.

Moving Between Website and Native Apps​

A browser's Web Bluetooth ID may work only in that browser. Android native control needs the real Bluetooth address, while iOS stores its own connection identity.

If a device works on the website but not on Android:

  1. Open its device card in Android and use the wrench / Rescan Bluetooth address action if shown.
  2. Follow the model-specific scan and select the matching physical device. For an address prompt, use the real Bluetooth address identified by the setup instructions.
  3. Close the website and official device app, then retry the Android connection.
  4. If Chastify still has only a browser ID or rescan is unavailable, contact Support with the setup error. Do not remove a device needed for an active session just to replace its address.

For iPhone, use the Select device flow described above. For a new browser, grant pairing permission in that browser and keep the page active during commands.

Reinstalling Chastify does not necessarily remove the saved account device or release a QIUI binding. Prefer repairing the saved connection identity to removing and re-adding the device.

Still Not Working?​

If native Auth Test reports an authentication problem, confirm internet access and that you can use your account in Chastify. Record the error and app version. Follow the app's sign-in prompt if one appears; avoid repeated reinstalls or clearing app data while a lock or Device Control session is active.

When to Contact Support​

Contact Support if the checks do not resolve the problem, especially for repeatable setup failures, incorrect status, or commands that report success without the expected result.

Include:

  • Device brand and exact model.
  • Phone/computer model, operating system, and Chastify app build or browser version.
  • Whether the failure is in Android, iOS, or Web Bluetooth, and whether it occurs in the background.
  • The action, exact error, and approximate time.
  • Whether connection, lock/unlock, and shock/vibration fail separately.
  • Relevant debug logs and the Auth Test result when available.

Support can investigate app behavior and logs, but cannot directly test the radio connection or hardware at your location.