(This feedback was written by Claude, but I guarantee it’s real)
Device: Kisstoy Lost (Insert version)
BLE Advertisement Name: QCPW
Peripheral ID: 8E:C5:FE:C2:BB:D8
Intiface Central: v3.0.4 (Android, Google Play latest)
Tested on: Android phone (Redmi, SDK 36) + Android tablet — same result on both
What happens:
Intiface Central scans and finds the device (QCPW), identifies it via the galaku protocol, but connection fails every time with:
Device errored while trying to connect: DeviceSpecificError(“HardwareSpecificError”)
It retries automatically several times, all failing with the same error. The device is found repeatedly (Device QCPW (PeripheralId(...)) found.) but never successfully connects.
Manufacturer Data from scan:
- Company: 1494, Data: [8, 0, 74, 76, 65, 73, 83, 68, 75]
- Company: 22358, Data: [142, 197, 254, 194, 187, 216]
- Advertised services: none
What works:
The Kisstoy official app connects and controls the device without any issues on the same phone.
Notes:
- Kisstoy Lost (Insert) was added in buttplug 9.0.7 (commit 0e2ca552 by @blackspherefollower), so the device should be supported.
- STPIHKAL has no dedicated Kisstoy protocol page — the device appears to be handled under the Galaku protocol.
- Bluetooth was restarted, Kisstoy app was force-killed, and the device was verified to be in pairing mode before each attempt.
Any ideas on what might be going wrong with the GATT handshake? Happy to provide BLE logs if needed.