Skip to main content

My Era100 won’t keep the coneection and turns off when used with my PC.

When playing music from my phone there is no problem. But when I play from AppleMusic and Youtube via my computer it shuts down after about 10 seconds.

Other times it keeps the connection for a longer while, but either way, it never actually play the sounds. It is connected but no sounds come out from either my PC or the Era100. The PC’s sound output is always set to the Era100.

So it is has nothing to do with bluetooth or wifi connection - those are stable when I use my phone. Also the speaker is located right next to my wifi and I have another Era100 further away, with no issues. And my PC has no problem keeping bluetooth connection with my mouse and keyboard, so it shouldn’t be that either.

Hope someone can help?

Hello ​@FredVillads, welcome to the Sonos Community!

I’m sorry to hear you are experiencing issues with your Sonos Era 100 Bluetooth connection with your PC.

A few things I can think of:

  • Era 100 has an Idle Auto-Disconnect setting which will disconnect your Era 100 from a Bluetooth device after 30 minutes of sitting idle. This setting is off by default, but can be turned on in the Settings menu. Select your Era 100, then go to BluetoothIdle Auto-Disconnect and make sure it is off.

  • Since the Audio output of the PC is always set on the Sonos Era 100, the Bluetooth connection is not terminating, but the audio is not going through. Does adjusting the Volume bring back the audio?

  • Does a PC reboot help? That would refresh the built-in Bluetooth dongle or adapter you might be using and improve the situation.

And my PC has no problem keeping bluetooth connection with my mouse and keyboard, so it shouldn’t be that either.

While both keyboard/mouse and Sonos Era 100 use the Bluetooth connection, the difference between the information transferred is huge.

Since there is no issue when you are connecting the Sonos Era 100 with your phone, there might be an issue with the software on your PC.

If none of the above bullet points resolved the issue, I would recommend reaching out to our Support Team for some live troubleshooting.

I hope this helps.


Reply