replace it with a rpi, the thing is ancient and EoL time to retire I am doing the same.

In this *specific* case, fwiw, if you have never updated the firmware on the 8BitDo Ultimate 2, you probably want to -- they improved a lot of things after firmware v1.06, and connection latency and reliability is one of them.

My controller firmware is already on version 2.x

The issue is specific to my steam link and it seems like a software issue with the steam link based on the consistency and that my desktop and Nvidia shield work fine with the controller in this mode.

Originally posted by Daddy_Morendo:

The issue is specific to my steam link and it seems like a software issue with the steam link based on the consistency and that my desktop and Nvidia shield work fine with the controller in this mode.

To clarify slightly, since these threads stick around forever and someone else is inevitably going to get this in a Google search result 3 years from now or whatever: Windows and Android use fairly aggressive default Bluetooth connection parameters in terms of what they request as a minimum connection interval. Linux, particularly older versions (such as the Link runs), tends to favor battery life over latency considerations and while the Linux defaults are better now, circa the Link's Linux version they had a fairly long minimum connection interval.

The 8BitDo Ultimate 2, prior to v1.06 of the 8BitDo firmware, would just blindly accept whatever connection parameters it was given and not request different ones; on the Link, best case scenario was that it would have noticeable latency, and worst case scenario was that if you were in a noisy RF environment, it could actually drop connection.

(Connecting anything that does request a shorter connection interval will, due to how Bluetooth works, end up with the old-firmware 8BitDo partly inheriting those settings, hence why the connection would magically 'improve' when a different controller was also connected via Bluetooth.)

After v1.06 (when they fixed connectivity with the Switch 2), it actually seems to request reasonable connection parameters, and the Link *will* honor those when the device requests different ones.

If, however, you're already on a firmware post-v1.06, that's obviously not the problem.

FWIW, I tested the 8BitDo Ultimate 2 on both my home Link and the Link sitting on my desk, with both firmware v1.09 and v2.01 (the one that has fixes for Switch connection issues), and I'm not having connection issues. So there has to be some other element involved than merely Link and 8BitDo Ultimate 2. :(

So I guess my next question would be "do you see connection issues with any other Bluetooth devices?"

If not, we can take the step of trying to get some logs off of the Link to see what's going on. If other Bluetooth devices *are* misbehaving... well, the logs might still be useful there, but I really hope it isn't something like your Link's hardware radio dying. :/

So to be clear, I'm referring to my controller by it's full name (8bitdo Ultimate 2 Bluetooth controller) because I think it's a separate SKU from the plain "Ultimate 2" controller (?). But, I am trying to connect via 2.4 GHz dongle and that is giving the issues.

I am actually able to use bluetooth with this 8bitdo controller and the steam link just fine.... as well as using a dual sense controller and I think at some point a series X over bluetooth as well.

I'm trying to get 2.4 mode working with the steam link because I'd like to be able to use the bluetooth mode on the Switch and change over to 2.4 GHz to use the steam link without having to re-pair anything.

I also have a separate "8Bitdo Ultimate 2C" which I'm able to use with the steam link with it's 2.4 GHz dongle so I'm assuming the 8U2B controller should be able to as well.

The 8U2B works in 2.4 dongle mode on my PC as well as Nvidia shield.

I will try to collect some logs this evening. Do I need to enable logs, then connect to my PC, then attempt to connect my controller a few times... then end the session?

Originally posted by Daddy_Morendo:

So to be clear, I'm referring to my controller by it's full name (8bitdo Ultimate 2 Bluetooth controller) because I think it's a separate SKU from the plain "Ultimate 2" controller (?). But, I am trying to connect via 2.4 GHz dongle and that is giving the issues.

OH, that definitely changes things! Thanks for the clarification.

Okay, some more testing to do now. :)

Thaaaanks. Glad I made it confusing

Actually, one wild theory -- I know the dongle/base thing will happily charge if you give it a USB-A to USB-C cable that's only rated for power delivery, but while I haven't tested this theory with the Ultimate 2's base/dongle specifically, I do know some other 8BitDo bases will be Very Unhappy if you try to actually do data over a lousy or damaged USB cable.

So before we go TOO deep into this rabbit hole... do you happen to have a different USB cable to try? Just in case. It's *probably* not what's going on if you're able to use the Ultimate 2C's dongle (since I imagine you're using the same USB cable), but still...

As for logs, the Link will collect logs automatically -- you can send them to your host PC by doing "Save Debug Logs" on the Link; when you start your next streaming session it'll dump them to the PC as steamlink_debug.txt. (The streaming_log.txt should also contain details about any controller disconnect/reconnect, but not necessarily *why*, hence wanting more logs if possible.)

Alternatively, you can enable SSH and just grab /mnt/scratch/log/S99steam off of the Link to get the shell and streaming client log directly.

So I have good news and bad news.

The good news is that I plugged in the 8BitDo Ultimate 2 Bluetooth via the dongle/charging station, and it's been connected for over 30 minutes without any issue!

The bad news is that this is on stock firmware 916, so I got no idea what's going on over on your side. Hopefully logs can help clarify it...

I can look for a data cable and try changing it out when I'm home but I can confirm I used the whole base + same cable when connected to the Nvidia Shield which worked.

Of note the U2 controller has a USB C dongle and I'm connecting it through the dock and out the dock through a USBC->USBA cable. the 2C has USB A dongle straight into the steam link.

Can also get logs when home.

Originally posted by Daddy_Morendo:

Of note the U2 controller has a USB C dongle and I'm connecting it through the dock and out the dock through a USBC->USBA cable. the 2C has USB A dongle straight into the steam link.

Just to double-check: for the Ultimate 2 Bluetooth I've got here, the 8BitDo charging dock IS the dongle. Is that the case for yours, or do they have two different models (which would be annoying but not surprising)?

At any rate, I've got the dock/dongle plugged right into the Link via a USB-A (Link side) to USB-C (8BitDo dock side) data cable.

Oh wait, you mean the little dongle inside the little compartment in the base of the dock (honestly I forgot that was removable). Then yeah, that's the same configuration.

logs!

https://pastebin.com/zJuwLDzT

https://pastebin.com/dsak13u5

https://pastebin.com/KXDEQRrs

Juuuust out of curiosity -- are you plugging the Ultimate 2 dock/dongle into the side USB port, or one of the back ones? And if it's the side port, could you try one of the back ones?

I am pretty sure I've tried a mix of them at some point but can try that next.