Incompatible with Dualsense Edge on PC

[NicNamed]

I've tested the software with a regular Dualsense, works as intended.

Using my Dualsense Edge, either plugged in or wireless, with a low battery or by manually pressing the PS button, no overlay appears.

Happy to help with testing or development if I can get some direction of what needs to be done to fix!

[PixelIndieDev]

I personally don't own a Dualsense Edge, making testing difficult.

Important

When sending the information, don't forget to label the text / screenshots / video's with USB or Bluetooth, so that I know to what version the information belongs to.

I would like to ask you for some information:

Can you check if this website sees your Dualsense Edge correctly?

If the website sees your Dualsense edge correctly (vendor id, product id, ps button inputs show up)
It should display the Vendor and Product ID and the input report. I have this video, that shows where you can find some of the information that I need.

Tip

When switching from USB to Bluetooth or otherwise, first remove the connection on the website to your controller. Otherwise the website will try to read USB and Bluetooth at the same time, causing faulty data. There should always only be 1 controller connected to the website.

This is the information I need:

• The Vendor and Product ID (for USB and Bluetooth)
• The PS button input offset (for USB and Bluetooth)
  • The offset in the video and on the following image is 11.
  • On the following image you can see how you should count the offset. At place 11, the 00 switches to a 01 when pressing the PS button on the controller.

• The Input report (for USB and Bluetooth)

For the Vendor and Product ID, you can just copy and paste the value next to it.
For the PS button offset, you can send the offset, or send a video where the PS button checkbox and input report box are both visibly in frame, then I can count it myself.
For the input report, you can copy the whole Input report box, or preferably video the input report box for a couple of second.

If the website does not see your Dualsense Edge correctly
Then find the hardware ids in Windows like this:
You can find the hardware ids by doing this in WIndows: Device manager -> Sound, video and game controllers / Bluetooth -> then right click your dualsense edge controller -> properties -> details -> property: Hardware ids

Here is how the hardware ids look like for a normal dualsense controller.

You can then copy and paste the hardware ids for USB and Bluetooth, or send a screenshot of them.

This is kinda a long message, but as I don't own a Dualsense Edge, I can't gather the information myself.

[NicNamed]

The DualSense Explorer website did not find the Edge correctly initially, but I pulled the HTML page and changed the variable PRODUCT_ID_DUAL_SENSE from the regular DualSense Product ID to the Edge one found in the Windows Device Manager.

Bluetooth & USB Vendor ID: 0x054C
Bluetooth & USB Product ID: 0x0DF2

USB PS Button Offset: 11
Bluetooth PS Button Offset: 12

DualSense.Explorer.Edge.mp4

Hope this helps, let me know if you need more info!

Edit: Formatting

[PixelIndieDev]

Thank you

I have created a test version: https://github.com/PixelIndieDev/DualSenseBatteryMonitor/releases/tag/VBeta3.2

I would be very surprised if I fully fixed the compatibility issue with the DualSense Edge. It should now detect your DualSense Edge controller, you pressing the PS button and it should display the correct value for the battery level, but it is just a test.
I would like to know if it detects your edge controller, detect you holding down the PS button and if it displays the battery level correctly.

You also managed to make the website work, If the website sees your battery level like you pressing the PS button, then you might be able to check if the battery level gets correctly detected by the test version.

[NicNamed]

Sorry for the later response!

With vBeta3.2, PS button is working while plugged in via USB and connected via Bluetooth! 🎊

I need to do more testing to verify if it is accurately showing battery level.

Regarding the website with my modified copy, the battery level was indicating 125% (while I believe I was fully charged although I'm not positive). So if you're currently using the same offset, we'll have to figure out the new one for the Edge. I'll try to connect to the website occasionally this weekend after gaming sessions and see if I can't figure out the right value.

[PixelIndieDev]

I don't mind a late response.

It is possible for the battery level to be above 100%, when fully charged. Most software cap it to 100%.

To check if the battery levels checks out, it's best to use the controller until the battery level starts dropping. If everything is correct, the website (and other software) should start seeing the battery level at ~118,5% -> 100% -> etc.

It is easiest to check if the battery level matches when the battery level is below 100%, as then the percentage capping is no longer active.

I don't fully know why the battery can get above 100%. It probably has something to do with voltages of the lithium battery as that can affect the raw data that gets read as its battery level. If I'm not mistaken.

[Vinnare12345]

Hi! First of all, thank you for creating this app, it’s been really useful. I also appreciate that you added support for the DualSense Edge as i primarily use it with that. I understand this is still a beta version, and overall everything works exactly as intended on my end.

The only small issue I’ve noticed is related to the low battery warning. The flashing icon in the top right corner seems to trigger correctly when the battery gets low, but it doesn’t go away on its own afterward. It only disappears once I actually plug the controller in and start charging it.

Apart from that, everything works perfectly. I’m not very tech savvy, so I’m not sure if this is something I could adjust myself in the downloaded files, or if it would require a small change in the .exe file itself. I just wanted to ask whether there’s an easy way for me to fix it locally, or if you’re considering addressing it in a future update.

Thanks again for your work and for sharing this, really appreciate it.

Edit:

just wanted to add a quick clarification after doing some further testing.

Earlier I mentioned that the low battery icon disappears once the controller starts charging. After testing more carefully, that doesn’t seem to be the case. Plugging in the charger alone does not clear the low battery icon.

The icon only disappears if I first plug in the charger, disconnect the controller and then reconnect it. Charging + reconnecting works, but charging by itself does not.

I also noticed that every time I reconnect the controller, the battery icon briefly changes to “Error 1111”, which seems to happen consistently on initial connection before the controller status updates. I was wondering if this is expected behavior, or if there’s any way to avoid or fix it, or if it’s simply unavoidable because the app needs to fetch the controller information first before it can display the correct state.

Thanks

[PixelIndieDev]

Hi! First of all, thank you for creating this app, it’s been really useful. I also appreciate that you added support for the DualSense Edge as i primarily use it with that. I understand this is still a beta version, and overall everything works exactly as intended on my end.

The only small issue I’ve noticed is related to the low battery warning. The flashing icon in the top right corner seems to trigger correctly when the battery gets low, but it doesn’t go away on its own afterward. It only disappears once I actually plug the controller in and start charging it.

Apart from that, everything works perfectly. I’m not very tech savvy, so I’m not sure if this is something I could adjust myself in the downloaded files, or if it would require a small change in the .exe file itself. I just wanted to ask whether there’s an easy way for me to fix it locally, or if you’re considering addressing it in a future update.

Thanks again for your work and for sharing this, really appreciate it.

Edit:

just wanted to add a quick clarification after doing some further testing.

Earlier I mentioned that the low battery icon disappears once the controller starts charging. After testing more carefully, that doesn’t seem to be the case. Plugging in the charger alone does not clear the low battery icon.

The icon only disappears if I first plug in the charger, disconnect the controller and then reconnect it. Charging + reconnecting works, but charging by itself does not.

I also noticed that every time I reconnect the controller, the battery icon briefly changes to “Error 1111”, which seems to happen consistently on initial connection before the controller status updates. I was wondering if this is expected behavior, or if there’s any way to avoid or fix it, or if it’s simply unavoidable because the app needs to fetch the controller information first before it can display the correct state.

Thanks

About your issue, the application is made to always show the battery overlay when a battery is low and that controller is not charging. When all batteries are full or when the low battery controller is charging, the battery overlay should not be visible by itself.

I need some further clarification.
When your battery level gets low, and you start charging it, the battery overlay should dissappear and when stopping the charging when the battery level is no longer low, the battery level should not appear again. Is that how it works in your case?

Does the flashing battery animation stop by itself when charging or when reaching a not low battery level when no longer charging?

With the low battery icon, do you mean the triangle that appears next to the battery?

About the 'working as intended', does the application correctly show the battery level and if it's charging when using a DualSense Edge? I personally don't own a DualSense Edge, so I can't personally test it. I would like to have as much conformation about thing working or not.

The Error 1111 is normal behavior. Dualsense controllers (I don't know about if other controller also do this) don't start sending all data to your pc when first connected. They mostly wait for a game or other application to ask for that information. My application does that, but as my application only updates the state every couple of seconds, the Error 1111 displays for a couple of seconds before getting the actual battery level. I made it display Error 1111, just so I know what the application is doing in the background.

[Vinnare12345]

Thanks for the detailed explanation, that helps a lot. I’ll answer each point clearly and also add one clarification based on some further testing.

1. Expected behaviour when charging after low battery
   After testing a bit more carefully, I can confirm that the behaviour does eventually match what you described.

When the battery level gets low and I start charging the controller:

• The battery icon correctly changes to the charging icon (the “flash” symbol appears), and
• The flashing animation stops as expected, and
• After letting the controller charge for a certain amount of time, the battery overlay does disappear on its own.

My earlier conclusion was based on stopping the charging too quickly, in that case, the overlay stays visible. So from a technical standpoint, it does work as you intended.

That said, from a user experience perspective, the overlay can remain visible for quite a while during that in between period. When gaming or doing productivity work, having the overlay constantly active in the corner can be distracting and it does take up screen space.

2. Flashing battery animation behaviour
   Yes, the flashing animation stops by itself as soon as charging starts, which works correctly.

3. Low battery icon clarification
   Regarding the low battery indicator: the triangle icon does not appear consistently. Sometimes it shows next to the battery, and other times the low battery state is indicated without the triangle. I’m not sure what determines when it appears.

4. “Working as intended” / DualSense Edge confirmation
   Aside from the overlay timing behaviour, everything else works correctly with the DualSense Edge:

• Battery percentage displays correctly
• Charging vs not charging state is shown correctly
• Connection status updates correctly

So overall, functionality seems solid on the DualSense Edge.

5. Error 1111 explanation
   Thanks for explaining this, that makes sense. From my side, Error 1111 consistently appears for a few seconds on every reconnection before the battery info updates, which aligns with your explanation.

6. Settings suggestion
   Even though the current behaviour is mostly correct, having an optional setting that lets us adjust some timing behaviour (for example, how long the overlay stays visible before disappearing) would make the app feel much better in day to day use, especially for gaming or full screen productivity work.

I've researched a bit and for reference, playstation's own low battery overlay typically appears for around 5 seconds and then disappears. It doesn’t continue to warn you or indicate exactly when the controller will die, it simply notifies you once and then lets it happen if the warning isn’t acted upon. A similar optional behavior here would make it feel more natural.

[PixelIndieDev]

Thanks for the detailed explanation, that helps a lot. I’ll answer each point clearly and also add one clarification based on some further testing.

1. Expected behaviour when charging after low battery
   After testing a bit more carefully, I can confirm that the behaviour does eventually match what you described.

When the battery level gets low and I start charging the controller:

• The battery icon correctly changes to the charging icon (the “flash” symbol appears), and
• The flashing animation stops as expected, and
• After letting the controller charge for a certain amount of time, the battery overlay does disappear on its own.

My earlier conclusion was based on stopping the charging too quickly, in that case, the overlay stays visible. So from a technical standpoint, it does work as you intended.

That said, from a user experience perspective, the overlay can remain visible for quite a while during that in between period. When gaming or doing productivity work, having the overlay constantly active in the corner can be distracting and it does take up screen space.

2. Flashing battery animation behaviour
   Yes, the flashing animation stops by itself as soon as charging starts, which works correctly.

3. Low battery icon clarification
   Regarding the low battery indicator: the triangle icon does not appear consistently. Sometimes it shows next to the battery, and other times the low battery state is indicated without the triangle. I’m not sure what determines when it appears.

4. “Working as intended” / DualSense Edge confirmation
   Aside from the overlay timing behaviour, everything else works correctly with the DualSense Edge:

• Battery percentage displays correctly
• Charging vs not charging state is shown correctly
• Connection status updates correctly

So overall, functionality seems solid on the DualSense Edge.

5. Error 1111 explanation
   Thanks for explaining this, that makes sense. From my side, Error 1111 consistently appears for a few seconds on every reconnection before the battery info updates, which aligns with your explanation.

6. Settings suggestion
   Even though the current behaviour is mostly correct, having an optional setting that lets us adjust some timing behaviour (for example, how long the overlay stays visible before disappearing) would make the app feel much better in day to day use, especially for gaming or full screen productivity work.

I've researched a bit and for reference, playstation's own low battery overlay typically appears for around 5 seconds and then disappears. It doesn’t continue to warn you or indicate exactly when the controller will die, it simply notifies you once and then lets it happen if the warning isn’t acted upon. A similar optional behavior here would make it feel more natural.

Thank you.

I might be able to add an option to use Playstation's own low battery level duration or to make it show continuously.

I'll probably update the readme or add a wiki to this github that explains the exact meanings of the different errors code and icons that can be displayed. I think that will be generally helpful for new users.

I will add a new comment when I've released a new version.

[PixelIndieDev]

I have released a Beta v2

Also I've added this issue that suggest the setting suggestion, for visibility.

Edit: Sorry, I uploaded the debug test version with static values. I have uploaded the correct version right now.

[Vinnare12345]

Thanks a lot for the update, the new timer setting works great on my end and behaves exactly as intended. It’s a really nice improvement and makes the overlay much less intrusive during normal use.

I did notice one new behaviour after updating, though. When I disconnect the controller and then reconnect it, the battery overlay appears and then stays visible indefinitely, even when the battery level isn’t low and the controller isn’t charging.

To clarify how I’m disconnecting:

• I’ve tested disconnecting by pressing and holding the dualsense PS button for about 5 seconds, and
• I’ve also tested disconnecting directly through Windows’ Bluetooth settings.

In both cases the result is the same, the overlay disappears when disconnecting, but after reconnecting, the overlay stays visible and doesn’t auto clear unless I restart the app.

Aside from that, everything else still works correctly, and the timer setting itself behaves exactly as expected.

[PixelIndieDev]

I would be very honest, on my end I couldn't get the bug consistently (happened around 60% of the time on my end). Therefore I cannot be sure if I've fixed the issue.

I made some modification which made the bug not appear again on my end. But as I couldn't get it consistently , it might be just "lucky" tries.

I've uploaded a Beta V3 with possibly the Bluetooth reconnect bug fix.

[Vinnare12345]

Just a quick update with the new version.

With the latest update, the behavior seems to have flipped for me. Now when I disconnect the controller, the overlay stays on screen with Error 654 and doesn’t disappear on its own. The only way I’ve found to clear it is to reconnect the controller, after which everything works normally again.

So now reconnecting the controller kind of acts as the “reset” for the overlay state. Aside from this, everything else still seems to work great on my end.

Just wanted to share this in case it helps with the disconnect logic.

[PixelIndieDev]

Just a quick update with the new version.

With the latest update, the behavior seems to have flipped for me. Now when I disconnect the controller, the overlay stays on screen with Error 654 and doesn’t disappear on its own. The only way I’ve found to clear it is to reconnect the controller, after which everything works normally again.

So now reconnecting the controller kind of acts as the “reset” for the overlay state. Aside from this, everything else still seems to work great on my end.

Just wanted to share this in case it helps with the disconnect logic.

Are you connecting/disconnecting/reconnecting a DualSense or DualSense Edge controller?