Skip to main content

I have two Play:1 speakers that generally work well and play across the various services I have. However, one of them won’t allow me to play a specific radio station via TuneIn (nor Sonos Radio) -- WPFW, a public station in Washington, D.C.

Speaker details:

  • A:  Play:1
    • Version: 17.1.1 (build 85066270)
      Hardware Version: 1.20.1.6-1.2
      Series ID: A200
  • B: Play:1
    • Version: 17.1.1 (build 85066270)
      Hardware Version: 1.8.3.7-1.0
      Series ID: A101

If I try to start listening to WPFW on Speaker A, it looks like it’s initiating but then just returns to Stop.  If I start it on Speaker B, it works fine.  If I start it on B then group it with A, both play it. If I then upgroup B, it will stop on A.  In short, the only way to listen to it on A is to have it grouped.

I don’t seem to have this issue with any other radio station, although I guess it’s definitely possible given the number. Anyone have a clue as to why this may be happening? No updates pending...

If you switch the location of Speaker A with Speaker B, does the issue remain with the same speaker or switch to the other speaker?

 

That’s a great question!  I hadn’t swapped them before simply because of the location of one, but it’s a great test.

I just swapped them and the issue continues with the specific speaker (“A” above), even in its new location. At least I’m now able to access the station in the room I’m most likely to listen to it, but there’s something different about that one speaker.

I just checked the error log and it has an entry but no info:
“Monday, July 14, 2025 - 2:50 PM Eastern Time” (no data listed below it).

That does appear each time I try to start WPFW on that speaker.

It’s certainly an unusual issue.

If you submit a diagnostic from the Sonos app the next time the speaker fails to play the station, then contact Sonos Support, there may be some data in the diagnostic that identifies what the actual problem is initiating the station from that particular speaker.

I’ve been in touch with Support and it's working its way up the chain -- a stumper, for sure!  I’ll update post when/if it gets resolved.

Reply


Terms & ConditionsCookie settings