Kisstoy Lost (Insertable) - ScalarCmd returns Ok but device does not vibrate

[jiangxi1129]

Device Info

• Device: Kisstoy Lost (Insertable)
• BLE Advertised Name: QCPW
• Matched Protocol: galaku
• BLE MAC: E5:7E:98:C4:F7:84
• Manufacturer Data: company 1494, data [8, 0, 74, 76, 65, 73, 83, 68, 75]; company 22358, data [229, 126, 152, 196, 247, 132]

Environment

• Intiface Central: 3.0.4+40 (Windows desktop + Android)
• Device Config Version: 4.189
• OS: Windows 10 / Android

Problem

The device connects successfully (vibrates briefly on BLE connection), and appears in the device list with two Vibrate actuators and a Battery sensor. However:

1. ScalarCmd with any Scalar value (0.1 to 1.0) returns Ok but the device does not vibrate
2. Dragging the vibrate slider in the Intiface Central UI also has no effect
3. StopDeviceCmd and StopAllDevices also return Ok but obviously nothing to stop
4. Battery sensor reads 0% but the Kisstoy official app shows 96% — so the sensor read is also incorrect
5. The device does vibrate once during the initial BLE connection, proving the hardware works fine
6. Tested on both Windows desktop and Android versions of Intiface Central — same issue on both (Android also showed HardwareSpecificError during connection attempts)

Steps to Reproduce

1. Open Intiface Central, start engine
2. Turn on Kisstoy Lost, start scanning
3. Device appears as "Kisstoy Lost (Insertable)", protocol "galaku"
4. Send any ScalarCmd → returns Ok, device does nothing

Expected

Device should vibrate when ScalarCmd is sent.

Notes

The Kisstoy official app can control the device without issues, so BLE communication works. It seems the galaku protocol config may have incorrect BLE characteristic UUIDs or write format for this specific Kisstoy model.