add usage_page parameter to specify device more precisely

[glyph]

fixes #200

This may be specific to the Rival 650, or it might be something more general to all SteelSeries mice; I don't have any way to test. Perhaps it should be part of the device profile? All I can say is that without this patch, rivalcfg interacting with my mouse is the luck of the draw; with it, I can reliably get the battery percentage.

I can say that at least it works with both wired & wireless devices.

[flozz]

On which operating system have you tested? macOS?

I will need some time to understand what the usage_page is exactly and if it is also required on other OS and other devices.

I have the Rival 650 so I will be able to test on my own on Linux. :)

[glyph]

On which operating system have you tested? macOS?

Yep, macOS only so far. I do have a Windows & Linux VM, and … maybe I can pass through the device on there? Clearly I have not adequately prepared this PR though :)

[flozz]

I think this PR will break Rivalcfg on Linux: usage page is always "0", at least with the hidraw driver :/

#200 (comment)

[flozz]

I will not be able to merge your PR as it breaks Rivalcfg on Linux. But thanks to your PR I have enough information to think about a fix.

I tried something in the 200-macos-ventura-endpoint branch. Can you test if it work?

more: #200 (comment)

[glyph]

Yeah this PR was more of a sketch anyway; I appreciate your prompt investigation here and I'm glad that my poking around helped a little bit!