DualSense controller not recognised correctly on Linux host unless also paired to the host

[lyubomirv]

Is there an existing issue for this?

• I have searched the existing issues

Is your issue described in the documentation?

• I have read the documentation

Is your issue present in the latest beta/pre-release?

This issue is present in the latest pre-release

Describe the Bug

Running a Ubuntu 24.10 host with Moonlight on a chromecast-with-google-tv.
Everything explained here was done with restarts of sunshine and moonlight between sessions/tests, even done in different days with system restarts in the meantime.

I initially had the controller paired to the host, then started using it paired to the client. DualSense was recognised correctly in Steam and in games. (tested with Baldur's Gate 3) ✅

Then I decided to remove the DualSense from the known Bluetooth devices on the host. To my surprise, when using the controller connected to the client, Steam started to recognise it as an XBox Series S controller. ❌

I paired the controller once again to the host, then again to the Chromecast, and using it through the client. Steam once again correctly recognises it as a DualSense. ✅

As you know, it is not possible to connect the controller both to the client and the host at the same time. So at all successful tests, it was only connected to the client. However, it seems that it does matter that the controller is paired to the host in order to be recognised correctly.

Expected Behavior

Expected for the controller to be recognised as DualSense even if the host never knew about its existence.

Additional Context

I think I've also never seen the gyro to work when the controller is used paired to the client. Not sure if this is related but mentioning nevertheless.

Host Operating System

Linux

Operating System Version

XUbuntu 24.10 (x11, xfce)

Architecture

amd64/x86_64

Sunshine commit or version

v2025.531.135549

Package

Linux - deb

GPU Type

AMD

GPU Model

RX 7900 XT

GPU Driver/Mesa Version

Mesa 24.2.8-1ubuntu1~24.10.1

Capture Method

KMS (Linux)

Config

address_family = both
origin_web_ui_allowed = wan

Apps

Relevant log output

None that I think matters but tell me if it does.

[lyubomirv]

More additional information:

I've also setup Sunshine on another computer at home, which is very different in terms of hardware - Intel + NVidia, running XUbuntu 22.04. This one doesn't even have a Bluetooth adapter and so has never been paired with the controller.

Testing with the same Moonlight client (DualSense controller paired to the Chromecast), I'm running RetroArch on this host and there I can see that RetroArch also recognises the controller as XBox Series S, which I guess is just the default type of controller.

[ReenigneArcher]

You can change the controller type in the Sunshine settings. There is an auto mode, but I don't know if all moonlight clients support that.

[lyubomirv]

I am using it in Auto mode. I have tried multiple times switching to DS5 mode but then the controller is not recognised at all (not even as XBox One S controller). This is again tested on both host computers, and this time with different clients, too - the Chromecast and also the Moonlight client for Linux. Also tested with a different controller - a third-party PS3 controller with USB dongle connector (correctly recognised by lsusb locally as a Playstation 3 controller).

If I'm doing something wrong then I'd like to know what. I can try doing more testing with other versions or OSes if you think that would help.

[ReenigneArcher]

Can you open this (https://app.lizardbyte.dev/gamepad-tester) on your host and connect from moonlight? Is it recognized correctly here?

[lyubomirv]

Ok, testing with the provided website. I didn't have a chance to test all possible cases but it shouldn't matter in my opinion. Here are the results:

1. DualSense + Chromecast client -> main host (where DS is still in the Bluetooth devices)

This works both with Auto and with DS5 emulation. The website shows it as a "Sunshine DualSense (virtual)" controller. Either way I see all axes (including the triggers) but no gyro axes. Also, there is a message that vibration is not supported by the controller or browser (firefox - installed via snap, in case it matters).

2. Third-party PS3 controller + linux client -> other host (which never knew DS existed)

When in Auto mode: website shows it as "Sunshine XBox One (virtual)"
When in DS5 mode: website doesn't show anything (just sits on the message that the XBox One controller was disconnected)
When in Switch Pro mode: website shows it as "Sunshine Switch (virtual)"
When in XBox mode: website shows it again as "Sunshine XBox One (virtual)"

By the way, I've previously done the same test 2 but with checking how it's recognised in RetroArch instead of on this website and the results were exactly the same - no controller when in DS5 mode and XBox or Switch in the other cases.

---

It looks like only the DS5 emulation is not working for some reason.

[koen-benne]

Same exact issue on NixOS (linux). DS5 controller automatcally gets recognised as Xbox Series S controller and when i set gamepad = ds5 it does not work at all.

i also get the following log:
[2025-06-09 12:05:57.025]: Warning: Unable to create virtual DualShock 5 controller: Permission denied

Seems like #2906 might be necessary, because it works after I run sudo setfacl -m g:input:rw /dev/uhid

[lyubomirv]

I looked into what @koen-benne said and followed the chain of github issues further, until I reached this comment.

It is essentially the same but done to start at boot. I did that and the issue was fixed for the combination of third-party PS3 controller + linux client + the host that never knew about the DualShock. I assume other cases would be fixed too.

In that case this issue should probably be closed as duplicate of #3758.