logitech / cpg-docs Goto Github PK

Hi,
thanks for publishing the HID++ 2.0 specs. I recently purchased a G533 gaming headset and would like to extend existing Linux tools for Logitech devices (e.g. Solaar) with support for that device. The headset reports to be using HID++ 4.2 protocol - please add the corresponding documentation to this repo.

I have already written some code for fetching the battery voltage using feature 0x1F20, but I have additional questions:

• is there a way to force the headset report its voltage without polling, the way it currently automatically reports changes in its charging state?
• how exactly is the battery percentage determined based on the voltage in Logitech's Window app? if a table conversion is used, please publish the table as well

Regards,
Kamil Domański

I don't know a better place to ask for this, hoping for an quite official answer.

Is there any possibility to detect an input device has been switched to another device inside my custom software?
Maybe is there even a possibillity to trigger a device switch from software?

Hi, i do not seam to find the documentation on the google drive about this feature 0x2110 SmartShift wheel. I had a problem using a third party software for Linux, Solaar and it changed the default value for smart shift in the mouse itself. That behaviour of the software was a bug (already reported and confirmed) but now there is no way to set it back to default. All I need about the documentation is to know the default value of smart shift at least for my mx master 3. Its just awful having the mouse like this and pls i just want to fix it back to normal.

There is partial information on these features, but having complete information would help in implementing it in Solaar.

These two features are listed as implemented for Solaar, but there is no way to change the information for them. Are these read-only? If not, if I get documentation I can try to implement changes for them as I have a mouse that has these features.

Solaar has a bug that could be fixed if we had documentation for REPORT RATE {8060}.

pwr-Solaar/Solaar#792

I'm going to try to implement REMAINING_PAIRING (0x1DF0) but I will need documentation.

pwr-Solaar/Solaar#788 reverse engineers KEYBOARD_DISABLE_KEYS and GESTURE_2 but it would be nice to have documentation to validate that the code works for other devices. Implementing GESTURE would be a nice addition so documentation for that would be useful.

I came across Set Report Rate (x8060), and the doc mentions that this function can be called only in host mode. Any clue what that means?

It seems like it prevents me from setting a new report rate, even when the request I issue is fully valid, Invalid Argument is returned.

Errors

• [InvalidArgument (2) Invalid reportRate, not in host mode]

Request for documentation to implement the PERSISTENT_REMAPPABLE_ACTION (0x1C00) feature for feature request pwr-Solaar/Solaar#832 as per pwr-Solaar/Solaar#582

in table 4 - short package structure and table 5 - long package structure, the byte 3 contains 16 bits

Although I've implemented support for BATTERY VOLTAGE in Solaar based on existing Solaar code and some information in the Linux kernel it would be useful to have official documentation on this feature, and maybe voltage vs capacity tables as well.

Some fields in receiver registers and notifications are marked as reserved in the HID++ documentation but appear to be used in later protocols and are important in pairing. Documentation on these fields would allow for the creation of better pairing tools. In particular fields r5, r6, and r8 of record B5 with nn looking like 0x2y and error type 0x04 and field r2 of notification 4A appear of interest.