Multiple Controllers outstanding issues and experience.

[petegordon]

1. There is zero trackpads in Wireless Controller (DS4 or spoof)
2. Steam Controller Puck can be used with up to 4 controllers, so this does not track the specific Steam Controllers as of yet.
3. I don't know what the # column all the way to the right means.
4. I still have not integrated haptics into the overlay to display and test
5. I have not done any testing with XBox controller (I've only been testing gyro controllers)
6. Just note that Windows holds the Bluetooth connection open to the DualSense controllers so they do not properly disconnect. It may be because of the PlayStation Accessory application.

FYI. The DS4Windows application creates an XInput Controller that becomes visible here when the application is launched.

[petegordon]

Triage of the items above (from the multi-controller inventory work in #34):

1. 0 trackpads on Wireless Controller (DS4/spoof) — should show 1. The device dictionary sets trackpadCount: 1 for DS4/GameSir-DS4 entries, and even the fallback is touchpad ? 1 : 0 (= 1). A row that reads 0 is almost certainly a stale localStorage record created before capabilities were resolved → Clear history + reconnect re-resolves it. If it persists after that, it's a real bug worth filing.
2. Puck tracks the dongle, not the 4 paired Steam Controllers — real limitation / future work. The Puck presents a single HID identity (its own serial FXB99…); identifying the individual paired controllers would require parsing the Steam Input protocol.
3. "#" column = connectCount (number of times the controller has connected). Trivial relabel to "Connects" is queued (1-line).
4. Haptics not wired into the overlay — separate from the inventory. The table shows the haptics spec from the device dictionary (e.g. "2 dual ERM rumble"); live rumble output is 3D-overlay work, not inventory.
5. No Xbox testing yet — note. See Steam Controller 2026 visualizer (Valve CAD → optimized GLB) #6 / the DS4Windows insight below: real Xbox hardware is still genuinely untested.
6. DualSense won't disconnect — this is Windows holding the Bluetooth HID handle open (likely the PlayStation Accessory app), not an app bug. Even Scan/Refresh (and a native node-hid poll) would see the device as present while Windows keeps the handle open. Not app-fixable.

Key insight on the DS4Windows screenshots: the Controller (XBOX 360 For Windows) rows (045e:028e, serial 01/02) are almost certainly DS4Windows' virtual XInput pads (ViGEm) — created when DS4Windows launches — not physical Xbox controllers. That's why they appear/disappear with the app and look like duplicates.

Background that informed the design (for the record):

• Genuine PlayStation pads carry a Foxconn (Hon Hai) MAC OUI, not Sony's; the GameSir clone OUIs aren't in any public registry. So OUI→vendor "genuine/clone" detection was evaluated and dropped as unreliable. The full MAC is kept as the per-unit identity (distinguishes identical pads over Bluetooth).
• Per-unit serial is Bluetooth-only for DS4-family — over USB the OS exposes no serial.