mirror of
https://github.com/safijari/openpuck.git
synced 2026-11-03 22:30:22 +00:00
[GH-ISSUE #45] steam controller 2015 support #22
Labels
No labels
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
safijari/openpuck#22
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tails101 on GitHub (Jun 16, 2026).
Original GitHub issue: https://github.com/safijari/openpuck/issues/45
welp everything is in the title,
since both controller are close
could you support the older controller too?
@safijari commented on GitHub (Jun 16, 2026):
I don't think they use the same wireless radio.
@uyjulian commented on GitHub (Jul 11, 2026):
The steam controller 2015 dongle uses NRF24LU1P.
Someone else managed to flash its firmware on an alternative board: https://im-just-lee.ing/steam-controller-d0ggle-54682aa4/
@safijari commented on GitHub (Jul 11, 2026):
Interesting. If it uses ESB I might be able to integrate it then. Won't know until I get back home and try with the original steam controller
@tails101 commented on GitHub (Jul 11, 2026):
yea i remember people was searching those dongles because they could be flashed with a special firmware.
i think they could support htc vives lightroom trackers, and they was able to handle multiples trackers at once without lag.
instead of needing a dongle by tracker.
simplifying a lot their full body vr setup.
@Inhibit commented on GitHub (Jul 14, 2026):
I'd be interested in Q/A'ing it if the will's there and the hardware's capable.
@27hectormanuel commented on GitHub (Jul 19, 2026):
+1 on this
@Vitnim commented on GitHub (Jul 24, 2026):
Another +1 here. Orig controller highly underrated.
@safijari commented on GitHub (Aug 20, 2026):
The protocol used by SC2015 is different and we would only be able to do either or, not both at the same time. I'm not going to implement SC2015 for OpenPuck but I do plan on doing that for picopuck (which would be Bluetooth based)