The bluetooth devices don't display correctly

[paulverbeke]

On the Steam Deck, since the last decky loader breakage, the devices in the list doesn't display or are overflowing out of the right of the screen

[Outpox]

Do you have a screenshot of this issue by chance?

[paulverbeke]

yes I've added it to the OP.

[Outpox]

Thanks I'll see what I can do.

[paulverbeke]

Also I was only using this plugin to easily connect/disconnect the steam deck to my Google pixel 8 pro phone. But now it seems like the phone isn't shown at all in the list

[Outpox]

I've just updated my Deck to the latest stable version + updated decky (curl -L https://github.com/SteamDeckHomebrew/decky-installer/releases/latest/download/install_release.sh | sh via the terminal) and I can not reproduce your error.

Regarding your issue I'm leaning toward and outdated Decky version please check via Decky settings menu page that you're running the latest version.

[Outpox]

Also I was only using this plugin to easily connect/disconnect the steam deck to my Google pixel 8 pro phone. But now it seems like the phone isn't shown at all in the list

I worked on a backend refactor to use dbus directly instead of bluez, it should improve the plugin reliability. However I've had a lot of work since then and took some distance from this project.
I'll see what I can do. I wanted to release a new setting menu alongside the backend rework but I'll do that in a separate release.
No promises, I'm already working on several other projects.

[paulverbeke]

I confirmed in the decky menu page that I already have the latest decky 3.2.6, but I reinstalled it anyway to make sure everything is working properly. But I see the same broken UI behavior. I'm testing at my workplace at the moment and there is a lot of bluetooth devices here. Could a big list of devices be the problem's origin ?
I counted 110 devices displayed

[Outpox]

That's my bad I just noticed I was running an unreleased 3.0.0 version which does work.
I reproduce your issue with the public 2.3.1 release.
I'll look into releasing the 3.0.0 without the new settings menu but I'm going on holidays next Sunday so I'm not sure I'll have time to release it before then.

[Outpox]

PR opened to release the new 3.0.0 on the store.

[paulverbeke]

Hi, I checked the decky plugins repo to see why the PR is taking this long to merge but it looks like all PRs are very long to be reviewed. I don't really know what's going on on their end but the release process looks either hard/stringent or slow.

Anyway I tested the 3.0.0 through the dev menu and I can confirm that:

• the UI is fixed
• the list of devices now correctly reflects the devices I have around me
• connecting/disconnecting works
• tested with earphones Sony WF-1000XM4 (as a speaker) and Google Pixel 8 Pro (as a source of media)

Nevertheless I have some feedback for you:

• when clicking on an element it can take several seconds to finish the action of connecting/disconnecting and during this time we don't have any real feedback that both our input was registered and that a connection is trying to be made. I don't know about you but I would expect a loading icon like this perfect to solve both feedbacks
• when the action of connecting/disconnecting is successfully finished, the UI is not refreshed at all. I can ear that my device is connected and working but the element is still grey. This behavior is fine for the case of an unsuccessful connection mind you. But for the UI to correctly reflect the connected state I need to either: close and re-open the plugin UI, or close and re-open the QAM using the 3 dots button, or click a 2nd time on the same device element.

Following here are screenshots to illustrate my 2nd feedback.

My 2 devices are connected in both SteamOS and the plugin:

Then I click on the Pixel 8 Pro, it takes ~3 sec then we can see it disconnects in the SteamOS UI in the background:

I can wait, move around, but still shown as connected in the plugin and disconnected in the background:

Then, if I click a 2nd time on the Pixel 8 Pro it instantly and correctly displays disconnected: