Skip to content

Add Teevolution Terra Pro with/without RapidSync Dongle support - #26

Merged
snekxs merged 2 commits into
OpenMouse-Project:devfrom
dwei30:add-teevolution-terra-pro
Aug 4, 2026
Merged

Add Teevolution Terra Pro with/without RapidSync Dongle support#26
snekxs merged 2 commits into
OpenMouse-Project:devfrom
dwei30:add-teevolution-terra-pro

Conversation

@dwei30

Copy link
Copy Markdown

Adds support for the Teevolution Terra Pro (including the RapidSync 8K dongle).
Tested with Terra Pro (Batch 2 with firmware 2.21) with and without the RapidSync 8K dongle
Protocol details were reverse-engineered from Teevolink web app: https://www.controlhub.top/teevolink/
Implementation work was assisted with Cursor

Terra ProRapidSync

dwei30and others added 2 commits August 5, 2026 04:05
Co-authored-by: Cursor <cursoragent@cursor.com>
Corrected formatting of vendor list in README.
@dwei30dwei30 changed the title Add Teevolution Terra Pro & RapidSync Dongle supportAdd Teevolution Terra Pro with/without RapidSync Dongle supportAug 4, 2026
@snekxs
snekxs merged commit 7707b7a into OpenMouse-Project:devAug 4, 2026
Pochiiko added a commit to Pochiiko/openmouse that referenced this pull request Aug 17, 2026
DO NOT MERGE AS-IS. This pins 06997e4, the head of mouse-protocol OpenMouse-Project#26,
which is not on that repo's main yet. Regenerate against main's tip once
OpenMouse-Project#26 merges, then take this out of draft.
Draft so the integration is reviewable alongside OpenMouse-Project#26. Class 0x02 button
mapping is confirmed over the Viper V3 Pro's cable (0x00c0) in that PR;
openmouse builds against an exact protocol commit, so the Buttons tab
stays hidden over the cable until this pin moves.
Rebased onto dev after mouse-protocol main moved to 4f56cdc and dev's
pin followed it. OpenMouse-Project#26 was rebased onto that same main first, so 06997e4
contains the Fantech driver as well as the wired flag. Pinning the
previous head would have reverted Fantech -- a dependency downgrade
wearing the costume of a merge conflict.
No source change is needed or made. availability.ts computes
razerButtons from status.razerButtonMappings and never looks at the
transport.
npm run check: 83/83, tsc clean, against this pin.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@dwei30@snekxs