Logitech G522 LIGHTSPEED support #488

Activity

1. sfu69

   added

   device-request

   on Feb 17, 2026
2. github-actions commented on Feb 17, 2026

   

   github-actionsBot

   on Feb 17, 2026 – with GitHub Actions

   More 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.
3. ChrisLauinger77 commented on Feb 18, 2026

   

   ChrisLauinger77

   on Feb 18, 2026

   Last edited by ChrisLauinger77

   Contributor

   More actions

   #477 seems like the lightspeed series made significant changes ...
   Did you try "headsetcontrol -o json" after you updated the ID ?
4. sfu69 commented on Feb 20, 2026

   

   sfu69

   on Feb 20, 2026

   Last edited by sfu69

   Author

   More actions

   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!
5. mryll commented on Mar 2, 2026

   

   mryll

   on Mar 2, 2026

   More actions

   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.
6. sfu69 commented on Mar 4, 2026

   

   sfu69

   on Mar 4, 2026

   Author

   More actions

   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.
7. AdrianoCahete commented on Mar 16, 2026

   

   AdrianoCahete

   on Mar 16, 2026

   Last edited by AdrianoCahete

   More actions

   Any update on this?
8. thanosk commented on Oct 3, 2026

   

   thanosk

   on Oct 3, 2026

   Contributor

   More actions

   Hello there. I've obtained this headset a few days ago and I think I can help improve current support for G522.

   I've already captured a number of packets with wireshark and done some tests with sending raw packets with headsetcontrol --dev, all successful so far.

   Before any coding, PRs and stuff, I'm planning with Claude and he made some (imho reasonable) suggestions, so let me quote him:

   The protocol is "Centurion", the same one the repo already uses for the G PRO X 2.

   ghub-startup.json shows G HUB discovering the headset's features, and the packet layout is what lib/devices/protocols/logitech_centurion_protocol.hpp already implements. The only difference is the framing: the G522 uses 0x50 0x23 where the G PRO X 2 uses 0x51.

   Suggested split

   1. PR 1: lights on/off, voice prompts, and possibly reading sidetone back, all in the existing G522 driver style. Small and easy to review.
   2. PR 2: EQ presets (replaying the captured bytes) and parametric EQ, once the gain encoding is confirmed.
   3. Optional refactor: move the G522 onto LogitechCenturionProtocol with the 50 23 framing, so feature numbers are discovered rather than hardcoded and can't break if a firmware update reorders them. That's worth raising with the maintainer before starting.

   ghub-startup.json contains (as it's name spills) the captured packets when launching G Hub.

   What Claude proposes for a refactor and re-using the LogitechCenturionProtocol sounds interesting from an engineering/organising perspective. Do you have any feedback on this perhaps ?

   Splitting these improvements into multiple/smaller PRs is my own idea, but if you'd like me to first extensively wireshark all I can and then send over a much bigger PR containing everything, let me know. Some things on the G522 don't 100% match the current headsetcontrol philosophy (for example preset light effects, custom light zones, effects that do not support brightness vs effects that do support it, etc), so if I let Claude run loose he proposes much larger modifications, which I suspect is perphaps not (yet) desirable.

   Also, running make format in a freshly cloned project as is, produces several modifications, should these belong to the same PR or the PR should contain only G522-related stuff ?
9. ChrisLauinger77 commented on Oct 3, 2026

   

   ChrisLauinger77

   on Oct 3, 2026

   Last edited by ChrisLauinger77

   Contributor

   More actions

   I think porting the G522 to centurion is the way to go here. Can only be done by a guy who owns the headset. So go for it
10. Sapd commented on Oct 3, 2026

    

    Sapd

    on Oct 3, 2026

    Owner

    More actions

    I agree