dualshock-tools/dualshock-tools.github.io
1
0
Fork 0
mirror of https://github.com/dualshock-tools/dualshock-tools.github.io.git synced 2026-03-01 11:19:54 +03:00
Code Issues 9 Packages Projects Releases Wiki Activity

NotAllowedError: Failed to open the device while attempt to calibrate Dualsense #61

New Issue
Closed
opened 2026-02-10 18:44:48 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-10 18:44:48 +03:00
Owner
Copy Link

Originally created by @Felixoid on GitHub (Nov 27, 2025).

Hey-hey.

I am using Version 142.0.7444.175 (Official Build) Arch Linux (64-bit) and Arch Linux.

I connected a controller to the host and pressed Connect on the site, chosen the controller

Image

And it says only:

Error: Failed to open the device.
Details
Main Error Stack:
NotAllowedError: Failed to open the device.

Do I miss some permissions?

Originally created by @Felixoid on GitHub (Nov 27, 2025). Hey-hey. I am using `Version 142.0.7444.175 (Official Build) Arch Linux (64-bit)` and Arch Linux. I connected a controller to the host and pressed `Connect` on the site, chosen the controller <img width="791" height="786" alt="Image" src="https://github.com/user-attachments/assets/525a2be7-4e52-45f5-8eab-c552751bf7f9" /> And it says only: ``` Error: Failed to open the device. Details Main Error Stack: NotAllowedError: Failed to open the device. ``` Do I miss some permissions?
OVERLORD commented 2026-02-10 18:44:50 +03:00
Author
Owner
Copy Link

@Felixoid commented on GitHub (Nov 27, 2025):

Tested Chrome as well, it has the same issue.

Here, I tried to create a udev rules file:

SUBSYSTEM=="usb", ATTR{idVendor}=="054c", ATTR{idProduct}=="05c4", MODE="0777"  
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", ATTR{idProduct}=="09cc", MODE="0777"  
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", ATTR{idProduct}=="0ce6", MODE="0777"  
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", ATTR{idProduct}=="0df2", MODE="0777"

The controller is visible in lsusb:

Bus 003 Device 028: ID 054c:0ce6 Sony Corp. DualSense wireless controller (PS5)

@Felixoid commented on GitHub (Nov 27, 2025): Tested Chrome as well, it has the same issue. Here, I tried to create a udev rules file: ``` SUBSYSTEM=="usb", ATTR{idVendor}=="054c", ATTR{idProduct}=="05c4", MODE="0777" SUBSYSTEM=="usb", ATTR{idVendor}=="054c", ATTR{idProduct}=="09cc", MODE="0777" SUBSYSTEM=="usb", ATTR{idVendor}=="054c", ATTR{idProduct}=="0ce6", MODE="0777" SUBSYSTEM=="usb", ATTR{idVendor}=="054c", ATTR{idProduct}=="0df2", MODE="0777" ``` The controller is visible in `lsusb`: `Bus 003 Device 028: ID 054c:0ce6 Sony Corp. DualSense wireless controller (PS5)`
OVERLORD commented 2026-02-10 18:44:51 +03:00
Author
Owner
Copy Link

@Felixoid commented on GitHub (Nov 27, 2025):

Ok, here how the udev file must look to work with /dev/hidraw* files:

> cat /etc/udev/rules.d/99-dualshock.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666"
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", MODE="0666"

It's not the safest one, a group can be used for the write mode. But it works

@Felixoid commented on GitHub (Nov 27, 2025): Ok, here how the udev file must look to work with `/dev/hidraw*` files: ``` > cat /etc/udev/rules.d/99-dualshock.rules SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666" KERNEL=="hidraw*", ATTRS{idVendor}=="054c", MODE="0666" ``` It's not the safest one, a group can be used for the write mode. But it works
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dualshock-tools/dualshock-tools.github.io#61
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?