Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Aerox 5 Wireless #184

Closed
aknotek opened this issue Aug 21, 2022 · 11 comments
Closed

Request: Aerox 5 Wireless #184

aknotek opened this issue Aug 21, 2022 · 11 comments

Comments

@aknotek
Copy link

aknotek commented Aug 21, 2022

Device identification wireless: 1038:1852
Device identification wired mode: 1038:1854

Product URL: https://steelseries.com/gaming-mice/aerox-5-wireless

Hey there! I have an Aerox 5 wireless. I was able to get it working using the existing Aerox 3 wireless code, just changing the device ID in aerox3_wireless_wireless.py. All the features for for Aerox 3 appear to work on the Aerox 5. Please let me know if there's any testing you need me to do!

@flozz
Copy link
Owner

flozz commented Aug 22, 2022

Hello,

There is a difference between the Aerox 3 and 5: the buttons. So button mapping may not work correctly.


I started working on this device on the aerox-5-wireless branch. Can you check everything is working in both wireless and wired mode:

  • --sensitivity
  • --polling-rate
  • --top-color
  • --middle-color
  • --bottom-color
  • --reactive-color
  • --sleep-timer
  • --dim-timer
  • --rainbow-effect
  • --battery-level (if possible test with battery fully charged and with battery low to see if there is no negative number or level > 100%)

For buttons, I will try to find some more information and I add here a screenshot I found on the web that show the buttons in the GG engine (for later reference):

image

@flozz
Copy link
Owner

flozz commented Aug 22, 2022

I implemented button mapping:

  -b BUTTONS_MAPPING, --buttons BUTTONS_MAPPING
                        Set the mapping of the buttonsX (default: buttons(button1=button1;
                        button2=button2; button3=button3; button4=button4; button5=button5;
                        button6=dpi; button7=disabled; button8=disabled; button9=disabled;
                        scrollup=scrollup; scrolldown=scrolldown; layout=qwerty))

I need someone to check it works too :)

@aknotek
Copy link
Author

aknotek commented Aug 22, 2022

Thanks for your work, Flozz! I will get these tested today, probably after dinner.

@aknotek
Copy link
Author

aknotek commented Aug 23, 2022

I was able to test everything on the list in wired and wireless mode.
--battery-level looks fine from 20%-100%. Can let it drop below 20% tomorrow and report back if needed.
--sleep-timer works fine on wireless mode but on wired the mouse doesn't appear to go to sleep. Maybe this is because it's plugged in?

Everything else on the list works as expected.

Will test the buttons either tomorrow or the next day let you know how it goes.

@flozz
Copy link
Owner

flozz commented Aug 23, 2022

Thank you for your feedbacks :D

--sleep-timer works fine on wireless mode but on wired the mouse doesn't appear to go to sleep. Maybe this is because it's plugged in?

Yes, the sleep mode can be configured in both mode but is active only in wireless :)

@aknotek
Copy link
Author

aknotek commented Aug 25, 2022

Alrighty, I was able to test the button remapping for all the buttons in wired and wireless modes. They all worked as they should.

@aknotek
Copy link
Author

aknotek commented Aug 26, 2022

Was able to get the battery to report a negative number. It was about 80% then I saw this. -5%
image

@flozz
Copy link
Owner

flozz commented Aug 26, 2022

It goes from 80 to -5 instantly? oO'

@aknotek
Copy link
Author

aknotek commented Aug 26, 2022

Yes, but I don't think rivalcfg is to blame. Messed with this a bit and I believe the wireless receiver was acting up as everything went back to normal once I unplugged and plugged it back in to the USB.

@flozz
Copy link
Owner

flozz commented Aug 26, 2022

Ok, good to know :)

@flozz
Copy link
Owner

flozz commented Sep 3, 2022

The support of this device has been merged to master, it will be released with next Rivalcfg version (v4.7.0). Thank you for your help! :)

@flozz flozz closed this as completed Sep 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants