Others still having these problems?

[ballew35]

I can only connect my controllers if I plug them into a USB cable first and then disconnect them from the cable. Minor annoyance, but would like to be able to just turn them on and have them connect. Also, I swear I have updated my controllers 10 times. It keeps telling me that they have an update, I update them, it says it was successful then the next time I use them it tells me there is another update. I am wondering if the update is really applying or there is a bug that keeps triggering the software to think there is an update. I have thought about resetting the controllers, but I am afraid something weird would happen and they wouldn't connect again.

Anything new on these bugs? As it stands now, it works... so I don't want to mess with it too much.

[JustJeff]

There are a few USB troubleshooting steps you can try, which have solved these issues for some people.

1. Try plugging the Vive into a different USB port.
2. If it is plugged into a USB 2.0 port, try a USB 3.0 port, or vice versa.
3. Make sure the USB cable goes directly from the breakout box to the PC and not through any additional hubs.
4. Disable USB Selective Suspend in Windows. You can find the option in Control Panel->Hardware and Sound->Power Options->Change plan settings (next to the currently selected plan)->Change advanced power settings->USB settings->USB selective suspend setting. You can search for guides on how to find this setting precisely in Windows 7, 8, or 10.

As for the controller always asking for an update, there may be a bug that is flagging it incorrectly. Can you upload a SteamVR system report so I can take a look? You can post a link here or, if you'd prefer, attach it to a support ticket.
https://support.steampowered.com/newticket.php?appid=7&category=408

[ballew35]

Thank you for your reply Jeff. There has been a development since I posted. So I tried all the steps you mentioned and it was still having me upgrade the controllers and even the headset periodically (though not as often as the controllers). Also, I still had to plug my controllers into my computer to get them to connect and then I could unplug them and they remained connected.

So no change, ...at first. Just a while ago I went in to change my audio settings so that the audio was playing through my surround sound speakers instead of through my headphones I would plug into the Vive. After changing the audio settings from the "USB Vive Audio" setting (forgot what it's called exactly, but it's the USB option for the Vive hub) to my HDMI Cable connected to my audio receiver/TV, my controllers can now be turned on and connected without having to plug them into a USB cable. Interestingly I remember someone else mentioning on another forum that changing their audio settings fixed their controller problem. However, I never tried it... until now.

Not sure why there would be a conflict between audio going into the Vive via USB and controllers connecting, but it appears that's the case. I would be happy to provide a report. When should I execute the report? Does the report only detail what's happened since I started the VR program? Does it reset when I exit out? Should I let something happen and then export a report?

[JustJeff]

Good observation! It could be that the USB Audio path is using too much bandwidth on the hub. I am curious if the controllers work normally when using the HDMI Vive audio device. Can you select that device? The Vive will have to be on with SteamVR running for it to be selectable.

The system report includes all of the recent logs. There is a limit, but it will include several days of sessions at least. It is easier to find interesting things in the most recent one or two sessions, so if you want to make sure to highlight an event, create the system report just after something happens. If you could run two sessions of SteamVR back to back, one with USB Vive audio selected (including the controller plug in, connect, unplug ritual), then the next with the HDMI receiver audio and working controllers, that will make it clear.

The firmware updates are in a separate section of the log, so I will be able to investigate that portion even if you haven't updated recently.