Repository navigation
Device request: Lamzu Paro Aurora (0x37b0: 0x000d / 0x0001 / 0x0007) #167
Description
Device Support / Protocol Request: Lamzu Paro Aurora
Device Overview:
- Product Name: Lamzu Paro Aurora (8K wireless gaming mouse, released mid-2025)
- Vendor ID (VID): 0x37b0 — Lamzu's own vendor id, the same one the Inca 8K uses
- Product IDs (PID): 0x000d, 0x0001, 0x0007 — mouse on cable, 1K receiver, 8K receiver (exact role mapping of each PID still unconfirmed)
- USB product strings: "LAMZU LAMZU PARO", "LAMZU LAMZU PARO 1K Receiver", "LAMZU LAMZU Aurora 8K Receiver"
- Connection Type: 2.4 GHz wireless + USB-C wired (8K and 1K dongles ship in the box)
- Hardware: PixArt PAW3950 sensor, up to 30,000 DPI, Nordic nRF52840 MCU, 48 g
Why it may be cheap to add:
- The existing
@openmouse/protocol/lamzucatalog covers Maya X, Inca 8K, CRDRAKO KO-ONE and Attack Shark models, but not the Paro Aurora. - It enumerates under 0x37b0 like the Inca 8K, so it likely speaks the same CompX feature-report page/command protocol — it may only need catalog entries in
LAMZU_INCA_PRODUCTS. - This is not the older "Paro" of the Atlantis generation (0x3554), which shares IDs with Atlantis OG V2 / Mini / Mini Pro / Thorn / Maya. Different hardware.
Evidence:
- VID/PID and USB strings come from community udev rules: passionofcrisis/lamzu-webdriver-aurora-linux-fix, commit "Add Paro Aurora" (passionofcrisis/Lamzu-Webdriver-Aurora-Linux-fix@7dac9fb) — not yet confirmed against a live capture.
- Specs from retailer listings (AusModShop: PAW3950, 30k DPI, nRF52840, 8K polling).
Hardware verification: not done yet. I'm happy to test on real hardware and provide lsusb output / WebHID enumeration details if a driver build becomes available.
Activity
Skilux commentedon Oct 5, 2026
PID correction — I pulled Lamzu's official Aurora web configurator device table (https://www.lamzu.net/Config/env-models.json, ModelEN: PARO), which gives the exact roles:
So the 8K dongle is 0x000e, not 0x0001 (0x0001 appears in the table only as _8KDongleIDVD). Rate lists from the table: wired 125–1000 Hz, 1K dongle 125–1000 Hz, 8K dongle 500–8000 Hz; DPIMax 30000. Bootloader identities to keep excluded: 0x0008 (mouse DFU), 0x0004 (1K dongle DFU); 0x0002 (8K dongle DFU) is shared with the Inca 8K and already excluded. The protocol flags match the Inca 8K entry exactly (IsNewProtocol: 1, IsCompx: 0), so the Paro Aurora should work with the existing lamzu driver via catalog entries alone. None of the three PIDs has been exercised on hardware yet — I can test on a real unit and report back.
snekxs commentedon Oct 6, 2026
Fixed in #172 — catalogued the Paro Aurora under Lamzu's own vendor id
0x37b0:0x0007wired and0x000d1K dongle at 125-1000 Hz,0x000e8K dongle at 500-8000 Hz, with0x0008/0x0004/0x0002bootloader ids excluded. Thanks for the PID correction from the official configurator table — it's what made this a catalog-only change. None of the three has been exercised on hardware yet, so a wrong rate list is the failure mode rather than a dead device.github-actions commentedon Oct 6, 2026
🎉 This issue has been resolved in version 0.26.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
feat(lamzu): catalogue the Paro Aurora