Skip to main content

I have a Port, and in the Line-In settings the Source Name is ‘Turntable’, when I select the Line-in in another room, it doesn't display the Source Name, it just displays ‘Audio Component’. Should it display the name that is configured in the Port Settings?

 

eg, HiFi is the Port, when I select the Line-In in the Lounge, it displays ‘Audio Component’

 

I believe the intention is to show the Source Name ie. Turntable in your case, no matter what room the Line-In input is playing.

However, playing around with various room configurations, I was able to get the Source Name to appear as “Audio Component” from “Portable Player” so the correct Source Name does not always appear.

In the screenshot below using an iPad Pro, the Line-In “Portable Player” is connected to a separate room not shown in screenshot.

 

When the system is viewed on an android device, both Source Names show as “Audio Component” !


But other times, the correct Source Name does appear on android.


The old Windows App displays what I would expect to see, Room and Source name, but iOS App is not, and web app (play.sonos.com) is different again, tries to display the queue on the Line-In, an interesting concept.

See comparison below whilst listening to LP via Source Name ‘Turntable’ on Port with Room Name ‘HiFi’ on stereo pair speakers with Room Name ‘Lounge’

Windows App:

 

iOS App:

play.sonos.com

 

 

In iOS I always see the correct source name on the Port, but this is never replicated to the player when the source is selected. Consistently inconsistent.

Maybe ​@Corry P can log as issue?


Hi ​@craigski 

Thanks for flagging, and I’m sorry to hear about this issue you are having with the Line-In source name not being displayed when played on other devices in the system. We are aware of this issue and are investigating. We do not have an estimate for when a fix might be put in place, but I will update this thread when I hear of it.

I hope this helps.

/Edited]


We are aware of this issue that seems to only affect iOS controllers and are investigating.

Thanks, also affecting play.sonos.com, and Android as per above.

 


Hi ​@craigski 

Thanks! I confess I did not fully take-in what you had written immediately before my post, as I already knew we were aware of the issue.

I have just checked the documentation and it seems that I was erroneously informed that the issue was iOS only - the documents make no such distinctions. I'll alter my above statement.


Reply