Logitech G522 LIGHTSPEED support

[sfu69]

Description

I will try gather as much information as possible via the wiki on the weekend.

I've already tried adding the deviceId towards the cpp code in the logitech G535 file with no effect, will try out some others on the weekend first before going the wireshark route.

Headset Name

Logitech G522 LIGHTSPEED

Device information

Detailed Device Information

headsetcontrol --dev -- --list

Device Found
 VendorID:  0x046d
 ProductID: 0x0b18
 Path: /dev/hidraw5
 Serial: 0000000000000000
 Manufacturer: Logitech
 Product: G522 LIGHTSPEED - Wireless Mode
 Interface: 3
 Usage-Page: 0x000c  Usage-ID: 0x0001

Device Found
 VendorID:  0x046d
 ProductID: 0x0b18
 Path: /dev/hidraw5
 Serial: 0000000000000000
 Manufacturer: Logitech
 Product: G522 LIGHTSPEED - Wireless Mode
 Interface: 3
 Usage-Page: 0xff13  Usage-ID: 0x0001

Device Found
 VendorID:  0x046d
 ProductID: 0x0b18
 Path: /dev/hidraw5
 Serial: 0000000000000000
 Manufacturer: Logitech
 Product: G522 LIGHTSPEED - Wireless Mode
 Interface: 3
 Usage-Page: 0xffa0  Usage-ID: 0x0001

New Device Implementation Checklist

• I acknowledge that implementing a new device requires direct access to the device and familiarity with capturing and analyzing its communications. I have access to the device and am willing to contribute by capturing necessary data and/or attempting implementation.
• I have already attempted to capture device communications using WireShark or similar tools and am including my findings (successful or not) with this issue to assist in implementation efforts.
• I am seeking guidance on how to begin this process and am willing to collaborate with the community to add support for this device. I understand where to find resources (refer to the WIKI).

[github-actions]

Thank you for requesting support for a new headset!

To implement support for a specific headset, we need to reverse-engineer and test on that device. Only people who own the headset can implement support for it.

Want to help?

1. Check our Development Wiki to get started
2. Use Wireshark to capture USB traffic from the official software
3. Post your findings (screenshots, data) here - we're happy to help!

See ADDING_A_DEVICE.md for detailed instructions.

[ChrisLauinger77]

#477 seems like the lightspeed series made significant changes ...
Did you try "headsetcontrol -o json" after you updated the ID ?

[sfu69]

Same issues likely as in #477
I did update the firmware this week via the g hub on my macbook.

Tested with LogitechG533 this time. The test with G535 is similar.

{
  "name": "HeadsetControl",
  "version": "continuous-23-g8d16611-modified",
  "api_version": "1.4",
  "hidapi_version": "0.14.0",
  "device_count": 1,
  "devices": [
    {
      "status": "partial",
      "device": "Logitech G533",
      "vendor": "Logitech",
      "product": "G522 LIGHTSPEED - Wireless Mode",
      "id_vendor": "0x046d",
      "id_product": "0x0b18",
      "capabilities": [
        "CAP_SIDETONE",
        "CAP_BATTERY_STATUS",
        "CAP_INACTIVE_TIME"
      ],
      "capabilities_str": [
        "sidetone",
        "battery",
        "inactive time"
      ],
      "battery": {
        "status": "BATTERY_UNAVAILABLE",
        "level": -1
      },
      "errors": {
        "battery": "Operation timed out"
      }
    }
  ]
}

It seems to allow sidetone adjusting, though!

headsetcontrol -s 50
Found 1 supported device(s):
 Logitech G533 (G522 LIGHTSPEED - Wireless Mode) [0x046d:0x0b18]

Successfully set sidetone!

[mryll]

With the help of Claude Code + Wireshark, I recently reverse-engineered the battery command for the PRO X 2 and posted the full protocol details in PR #478. The G522 exposes the same usage page pattern (0xffa0) so the same protocol likely applies.

[sfu69]

I just checked and the battery did not work sadly. Sidetone and inactive time worked according to the console. I could test the inactivity and it was not successful. I've set it to one minute and it did not shut off after even 5 minutes.

The changes I made to test it were the 2 for the array length as well as the Product ID within the LogitechGProX2Lightspeed class.
And from the merged PR you've sent me, I don't think I've missed any other configuration I should have done.

static constexpr std::array<uint16_t, 2> SUPPORTED_PRODUCT_IDS { 0x0b18, 0x0af7};

headsetcontrol -o json

{
  "name": "HeadsetControl",
  "version": "continuous-25-gabfb248-modified",
  "api_version": "1.4",
  "hidapi_version": "0.14.0",
  "device_count": 1,
  "devices": [
    {
      "status": "partial",
      "device": "Logitech G PRO X 2 LIGHTSPEED",
      "vendor": "Logitech",
      "product": "G522 LIGHTSPEED - Wireless Mode",
      "id_vendor": "0x046d",
      "id_product": "0x0b18",
      "capabilities": [
        "CAP_SIDETONE",
        "CAP_BATTERY_STATUS",
        "CAP_INACTIVE_TIME"
      ],
      "capabilities_str": [
        "sidetone",
        "battery",
        "inactive time"
      ],
      "battery": {
        "status": "BATTERY_UNAVAILABLE",
        "level": -1
      },
      "errors": {
        "battery": "Operation timed out"
      }
    }
  ]
}

headsetcontrol -b

Found 1 supported device(s):
 Logitech G PRO X 2 LIGHTSPEED (G522 LIGHTSPEED - Wireless Mode) [0x046d:0x0b18]
Battery:
	Status: BATTERY_UNAVAILABLE
Error: [battery] Operation timed out

I'm not sure how much my device differs, but I currently sync configurations towards the headset via the logitech hub and they stay even if I switch operating systems or turn off the device. Thus I didn't have any issues in that regard.

I will try to find some time on this weekend to help out with gathering wireshark data for the battery/inactivity/sidetone.

[AdrianoCahete]

Any update on this?