OEM Ecosystem
The Huepar app isn’t just for Huepar devices - it’s a white-label platform supporting multiple brands and manufacturers. This page explains the ecosystem.
The Hidden OEM: Longshuo Technology
Section titled “The Hidden OEM: Longshuo Technology”The APK contains manufacturer identification strings:
| Device Type | Manufacturer URL | Service UUID |
|---|---|---|
| LDM_M1 | www.longshuo-tech.com.cn | 0xAE30 |
| LDM_M2 | www.sndway.com | 0xFFF0 |
| LDM_M3 | xintong | 0x1000 |
| laserLevel_M1 | www.levelsure.com | 0xFFF0 |
| laserLevel_M2 | www.levelsure.com - 603BT | 0xFFA0 |
| laserLevel_M3 | www.levelsure.com - DP | 0xFFE0 |
The S120 uses LDM_M1 with service UUID 0xAE30, identifying it as Longshuo hardware.
Multiple Brands, Same App
Section titled “Multiple Brands, Same App”The APK is configured to build for multiple app store listings:
| Package Name | Brand | Notes |
|---|---|---|
com.pairlink.futian.huepar | Huepar | Primary listing |
com.insona.laser.levelsure | Levelsure | Laser levels |
com.pairlink.leiwo.lasercontroller | Leiwo | iOS variant |
com.ancoratools.laser | Ancora Tools | Rebranded |
dk.elma.laser | Elma | European market |
Architecture Diagram
Section titled “Architecture Diagram” ┌─────────────────────────────────┐ │ app.huepar.com │ │ (Shared Backend) │ │ - User accounts │ │ - Forum posts │ │ - Device telemetry │ └─────────────────────────────────┘ ▲ │ REST API ┌───────────────────┼───────────────────┐ │ │ │ ┌──────┴──────┐ ┌──────┴──────┐ ┌──────┴──────┐ │ Huepar App │ │ Levelsure │ │ Elma App │ │ (Android) │ │ App │ │ (Android) │ └─────────────┘ └─────────────┘ └─────────────┘ │ │ │ │ BLE │ BLE │ BLE ▼ ▼ ▼ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ Longshuo │ │ SNDway │ │ Longshuo │ │ Hardware │ │ Hardware │ │ Hardware │ │ (0xAE30) │ │ (0xFFF0) │ │ (0xAE30) │ └─────────────┘ └─────────────┘ └─────────────┘Device Type Detection
Section titled “Device Type Detection”The app identifies devices by matching BLE service UUIDs during scanning:
// From decompiled APKconst DEVICE_CONFIGS = { LDM_M1: { serviceUUID: '0xAE30', manufacturer: 'longshuo' }, LDM_M2: { serviceUUID: '0xFFF0', manufacturer: 'sndway' }, LDM_M3: { serviceUUID: '0x1000', manufacturer: 'xintong' }, // ... laser levels use different UUIDs};When connecting, the app selects the appropriate protocol based on the detected device type.
Protocol Variations
Section titled “Protocol Variations”Different manufacturers use different protocol versions:
| Manufacturer | Protocol | Key Differences |
|---|---|---|
| Longshuo (S120) | LDMv1 | Commands start with F1 |
| SNDway | LDMv1 variant | Similar but different UUIDs |
| Levelsure | LaserLevelV1/V2/V3 | Fan control, horizontal/vertical modes |
Why This Matters
Section titled “Why This Matters”Understanding the OEM ecosystem helps explain:
- Protocol similarities - If you reverse engineer one Longshuo device, others likely work the same way
- App behavior - The app contains code for devices you don’t own
- Privacy concerns - Your data may be associated with multiple brand ecosystems
- Support quality - Huepar support may not have deep hardware knowledge (they’re a reseller)
Finding Your Device’s OEM
Section titled “Finding Your Device’s OEM”To identify which OEM made your device:
- Scan for BLE services - The service UUID indicates the manufacturer
- Check the app logs - Device type is logged during connection
- Compare protocols - The command format reveals the protocol family
| Service UUID | Likely OEM |
|---|---|
| 0xAE30 | Longshuo Technology |
| 0xFFF0 | SNDway or Levelsure |
| 0x1000 | Xintong |
| 0xFFA0 | Levelsure (603BT series) |
| 0xFFE0 | Levelsure (DP series) |
Related Pages
Section titled “Related Pages”- Security & Privacy Analysis - Privacy implications of this ecosystem
- BLE Service Reference - Service UUID details