Skip to main content
Avid Contributor I
November 25, 2018

Alexa "Sorry something went wrong" response when requesting radio stations via Tune in.

  • November 25, 2018
  • 12 replies
  • 4028 views
Alexa unable to play any radio stations from Tune in apart from the BBC. A request to play BBC radio 2 for example, Alexa responds with "Playing BBC 2 from tune in". All other radio station requests from tune in always generate the same response, "Sorry something went wrong". This issue is replicated across three separate devices, sonos one and two beams. All tune in stations available manually using the Sonos app. Thanks.
    This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

    12 replies

    cdubbAuthor
    Avid Contributor I
    December 26, 2018
    Hi Tim4971, Sorted !!! Purchased a third beam. Installed as per previous Sonos equipment. Delighted to discover there were no request issues whatsoever with this new beam. The new beam, via alexa, will instantly discover any "Tune in" Station and play on the device as requested. Alas still the same "Sorry something went wrong" response from existing three smart devices, (Sonos One, 1st and 2nd beams). Went into the alexa app, via PC, to compare the settings for the new 3rd beam against existing devices. Touchdown!!!!! The new beam had my postcode entered in the "zip code" field. The zip code fields for the previous three devices were not completed, the fields were empty. I entered my postcode and address into the zip code for the first original beam. It then gave me the choice to select my original post code with just a house number. This original data must have existed from when the speakers were first installed. I completed the process for the remaining two devices. ALL devices now play any "Tune In" radio station as requested and everything is all back to normal. I assume all the zip codes must have been deleted either during the set up process for the 2nd beam or during some update. I cannot believe it was something as simple as that and despite detailed and involved support from Sonos technical, this was not identified. Still waiting for Sonos support to respond to original requests. Hope this is of help to anybody with similar issues.
    Lyricist III
    December 26, 2018
    Hey Cdubb - you are seriously in the wrong business (not sure what you do lol). You have discovered something the whole dev team at Sonos could not!! I am yet to try this as out and about but will do as soon as I get back... Great work! Happy Holidays!!