Device Info
- Device: Sistalk MonsterPub Magic Kiss
- BLE Name: MonsterPub
- BLE Address: C3:54:4C:02:C8:34
- Manufacturer Data: company 9490, data [2, 0, 7, 0, 99, 0, 0, 0, 0, 0]
- Intiface Central: v3.1.0+42, Device Config v5.3
Problem
The device is detected as monsterpub protocol, but cannot be controlled. Vibration commands have no effect.
Root Cause (from nRF Connect scan)
The device exposes completely different BLE services than what the monsterpub protocol expects:
Actual services on device:
- 0xFE59 (Secure DFU)
- 0x1800 (Generic Access)
- 0x180A (Device Information)
- 0x9000 (Unknown) ← only custom service
- 0x9001: NOTIFY, READ, WRITE
- 0x9002: NOTIFY, READ, WRITE NO RESPONSE
Expected by monsterpub protocol:
- 0x6000 (tx, txmode, txvibrate, generic0) ❌ missing
- 0x6010 (rxblemodel) ❌ missing
- 0x8000 (rx for auth) ❌ missing
Since service 0x6010 is missing, rxblemodel read fails and identifier becomes "Unknown". Since service 0x8000 is missing, authentication is skipped. Since service 0x6000 is missing, no vibration commands can be sent.
This appears to be a newer firmware revision that uses a different BLE service layout (0x9000 series instead of 0x6000 series).
Device Info
Problem
The device is detected as monsterpub protocol, but cannot be controlled. Vibration commands have no effect.
Root Cause (from nRF Connect scan)
The device exposes completely different BLE services than what the monsterpub protocol expects:
Actual services on device:
Expected by monsterpub protocol:
Since service 0x6010 is missing, rxblemodel read fails and identifier becomes "Unknown". Since service 0x8000 is missing, authentication is skipped. Since service 0x6000 is missing, no vibration commands can be sent.
This appears to be a newer firmware revision that uses a different BLE service layout (0x9000 series instead of 0x6000 series).