-
Notifications
You must be signed in to change notification settings - Fork 0
Error Codes
If the application encounters an issue, it will display a specific error code. Use the table below to identify the problem and find a potential solution.
Most error codes will be caused by bugs or incompatibility with a newer firmware or something similar
These codes usually appear when the application is struggling to "see" or communicate with the hardware on your system.
| Code | Meaning |
|---|---|
| 640 | Could not update device list |
| 654 | Error occurred when checking controllers |
| 655 | Could not read controller (Raw HID data) |
| 656 | Error occurred when checking raw HID data |
These codes appear when the app detects a controller but cannot successfully get information from it.
| Code | Meaning |
|---|---|
| 771 | Exception error occurred when trying to wake controller |
| 772 | Could not open controller when trying to wake |
These errors relate to the specific data the controller is sending back regarding its battery status.
| Code | Meaning |
|---|---|
| 887 | Unknown error on battery side |
| 888 | Unknown controller report length |
| 889 | Unknown Bluetooth report length |
These codes are specific to Bluetooth connections where the controller is connected to Windows but in a "low power" or "sleep" state. These error codes are NOT serious and are a normal occurrence if they take less than 8 seconds to resolve.
| Code | Meaning | Suggestion |
|---|---|---|
| 1111 | Exception error occurred when trying to wake controller | Press any button on the controller |
| 1112 | Could not open controller when trying to wake | Press any button on the controller |
This wiki is written for release version 4.0.0+
DualSense Battery Monitor is an independent project and is not affiliated with Sony Interactive Entertainment.