Repository navigation
Many devices, (SteelSeries, Razer, Corsair) #56
Description
Gonna attached the diagnostics.txt file bellow but the devices i would to be added if possible at all would be:
Razer Razer BlackWidow V3 Pro
SteelSeries Arctis Pro Wireless
SteelSeries Arctis GameBuds
Corsair CORSAIR DARK CORE RGB PRO SE Gaming Dongle
Activity
ahmedkhursheed23 commentedon Sep 26, 2026
Hi @KKiruano, two of your devices are in #60 (not merged yet):
1038:1290): the app sends41 aa(is the headset on?) and then40 aa(battery level 0–4) on interface 0.1038:230A): the app sends00 b0on interface 3. It shows the lower level of the buds that are out of the case.Your diagnostics show the collections that #60 expects:
1290has its vendor collectionFF00on interface 0, and230AhasFFC0on interface 3. So the requests go to the correct place.I do not have these devices, so the reply layout is not tested yet. When #60 is in a release, please send a new Diagnostics… report. The SteelSeries section shows each request and the raw reply, so it will confirm (or correct) the layout.
Your diagnostics also show a second device,
1038:1294"Arctis Pro Wireless" on interface 5. No source that I checked documents it, so #60 does not send anything to it.ahmedkhursheed23 commentedon Sep 27, 2026
@KKiruano, there is now a test build that contains #60 (Arctis Pro Wireless and GameBuds) and #43 (Arctis Nova Pro Wireless): https://github.com/ahmedkhursheed23/HaloBattery/releases/tag/v1.11.0.2
If you can, please start it with the headsets on, and attach the Diagnostics… report. The SteelSeries lines show each request and the raw reply, so one report confirms or corrects the layout for both headsets. Use the official releases again when they include these changes.
KKiruano commentedon Sep 27, 2026
Hey @ahmedkhursheed23 , just tried and indeed it showed the lower earbud battery and also showed the arctis bro battery.
One thing i might add is that i needed to fully close the app and reopen for it to detect the arctis pro not sure if there's a timer that scans every X minutes or if its a bug.
diagnostics.txt
ahmedkhursheed23 commentedon Sep 27, 2026
@KKiruano, thank you for testing. Good to know that both work.
About the restart: the app looks for new devices at every poll (every minute by default, sooner when a device is plugged in). A new device should get its icon without a restart. There is a known bug where the first "show" of a new icon can be lost if the icon's window is not ready yet. The icon then exists but is not visible until the app restarts. PR #99 fixes that: an icon is now shown only after its window is ready.
HeyOkay commentedon Sep 27, 2026
Halo Battery 1.12.0 ships the Arctis Pro Wireless and the GameBuds (#60), confirmed on your headsets, thanks! The restart you needed should be fixed too (#99). Still missing: the Corsair Dark Core RGB Pro SE mouse and the Razer BlackWidow V3 Pro keyboard, so keeping this open for those.
KKiruano commentedon Sep 27, 2026
If there's anything i can provide to help add especially the mouse into just let me know.
And thanks for the awesome work
casparas123 commentedon Sep 28, 2026
Both of #56's remaining devices are implemented, from the references your comment names. They are open as PRs:
1532:025C) has a battery; OpenRazer's class for the wired1532:025Alists noget_battery, so that id stays out - a wired keyboard's answer to the battery command is a meaningless value anyway. The keyboard answers the same class0x07commands the mice do, so it is one table row; it has noff00collection, and its0059:0001control collection is already reached by the probe order, which a test pins.CMD_GET 0x0e+FIELD_BATTERY 0x50on the dongle1B1C:1B7F, answered with an index into a five-step table{0, 15, 30, 50, 100}. That is a gauge, not a percentage, so it shows as "about 50%" - the same treatment the app gives other coarse values. The status byte's meaning is not written down in either source, so no charging state is reported. The wired1B1C:1B7Eis left out until something proves it answers.@KKiruano, both are marked Unverified in the PR, the README and the changelog: they are built from the references and have not run against the devices. If you can install from the PRs and send a Diagnostics report with each device connected, the two new sections print every request and its reply - that settles the collection choice and the transaction id of the keyboard, and the dongle's reply layout, in one go. If a number is wrong, that report is what corrects it.
BlackWidow V3 Pro: drop an unattributable collection claim (review)
KKiruano commentedon Sep 28, 2026
Will glady test anything but i look at both PR and have no ideia where i can get the .exe to test it.
Also i was searching and found out that SignalRGB is able to get the mouse actual percentage? or maybe they are just guessing its weird that icue doesnt show it but they do.
casparas123 commentedon Sep 28, 2026
Good news on both fronts.
Getting a .exe: both of your remaining devices now have a test build - download it here:
https://github.com/casparas123/HaloBattery/releases/tag/v1.12.0.8
Under "Assets", take HaloBattery-1.12.0.8.zip, extract it anywhere and run HaloBattery.exe. It is a portable test build - nothing gets installed and it does not touch your current setup. Windows may show a SmartScreen warning for the unsigned build: "More info" -> "Run anyway".
What is in it:
Please start it with both connected, press Diagnostics... and attach the report here. It shows what the app asked each device and what came back, so one report confirms or corrects both devices. Use the official releases again once they include these two.
About SignalRGB and the percentage: good find, and it is worth a check. iCUE only ever shows low/medium/high for this mouse, and the dongle's own battery command reports the same coarse steps - that is everything any program can currently get from it. If SignalRGB shows a real percentage, it found something finer, and we would love to have it. One small test - watch the SignalRGB number while the mouse sits and drains a little:
Either way that answers it, and it tells us what your mouse here should show.
KKiruano commentedon Sep 28, 2026
Image above from signalrgb, is does move "normally". Attaching two diagnostics cause i saw differences and maybe an incompatibility with SignalRGB also the mouse only showed briefly in both instances and showed at 0%
diagnostics.txt
diagnostics_without_SignalRGB.txt
11 remaining items
KKiruano commentedon Sep 30, 2026
Hello again, I just ran the probe here is the output
probe-output.txt
casparas123 commentedon Sep 30, 2026
This is the one we were waiting for - thank you! Your probe output shows exactly how your dongle wants to be asked, and it even shows the number: about 55%. That also settles the SignalRGB question - your mouse really does report a real percentage, and now we know how to read it.
I've fixed the app and there's a test build for you:
https://github.com/casparas123/HaloBattery/releases/tag/corsair-darkcore-test1
The fix is also open as a pull request: #170
Once you confirm it reads correctly, it goes into the next official release and we'll mark it as confirmed. Thanks again for all the runs - this one did it.
KKiruano commentedon Sep 30, 2026
Attached two screenshots and both are showing the same value so this is success :D
Corsair Dark Core RGB Pro SE: confirmed on hardware (KKiruano, HeyOka…
casparas123 commentedon Sep 30, 2026
That is the confirmation we were hoping for - thank you! Two screenshots showing the same value is exactly the result we needed, and the old 0 % mystery is gone for good.
What happens now: the fix goes into the next official release, and you get credited in the changelog as the person who confirmed it on real hardware. The pull request has been updated the same way.
One small thing the two screenshots cannot show - over the next few days, keep half an eye on the number:
If either of those looks off, a Diagnostics report like before tells us everything, and we will take another look. But otherwise - enjoy the working battery, and thanks again for all the probe runs and the patience. The last stretch of this was mostly your hardware doing the talking.
Corsair Dark Core: a time window, two equal answers, a per-dongle bud…
HeyOkay commentedon Oct 5, 2026
Thank you @KKiruano for all the probe runs. The Dark Core RGB Pro SE fix you confirmed is in #170 and is planned for the next release (1.15.0). Keeping this open until it ships.
Generated by Claude Code
Corsair Dark Core RGB Pro SE: the battery over the dongle's routed ex…
Corsair Dark Core RGB Pro SE: confirmed on hardware (KKiruano, HeyOka…
Corsair Dark Core: a time window, two equal answers, a per-dongle bud…
HeyOkay commentedon Oct 12, 2026
Halo Battery 1.15.0 ships the Corsair Dark Core RGB Pro SE fix (#170) that you confirmed against SignalRGB. With it, all four devices from this request are supported. Thank you @KKiruano!
Generated by Claude Code