Skip to main content
JohnG666
Enthusiast II
May 25, 2022

Planet Rock unable to play unless select again from My Sonos stations

  • May 25, 2022
  • 45 replies
  • 735 views

I have the proper Planet Rock plugin (or whatever it is called!) for Sonos and it seems to work every time on my Roam, but on the lounge speakers, if I don’t play it for a day or so, when I then press play on the Lounge it is never able to play - it comes back with “can’t find Planet Rock station” or something like that.

I then have to re-select it from my radio stations on My Sonos and then it plays fine. It does the same thing no matter which app I use - I have it on an iPad Pro and on an Android phone. They both have the same issue.

 

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.

45 replies

Show previous replies
JohnG666Author
Enthusiast II
May 30, 2022

Yes that’s exactly the same behaviour I see. Once it’s failed, it will not start using the play/pause button and you have to reselect the station.

 

    JohnG666Author
    Enthusiast II
    May 30, 2022

    I’ve had an online chat with support but they wouldn’t discuss your submitted diagnostic and wanted me to change things on my router which I’m not prepared to do whilst I have everything else working fine!

    I was asked to change :- DNS Primary 8.8.8.8 - Secondary 8.8.4.4

    Also they said it would need some live diagnostics when the error is occuring to which I replied that it should be straightforward for them to create the error themselves :)

     

    Ken_Griffiths
    Ken_Griffiths
    May 30, 2022

    I’ve had an online chat with support but they wouldn’t discuss your submitted diagnostic and wanted me to change things on my router which I’m not prepared to do whilst I have everything else working fine!

    I was asked to change :- DNS Primary 8.8.8.8 - Secondary 8.8.4.4

    Also they said it would need some live diagnostics when the error is occuring to which I replied that it should be straightforward for them to create the error themselves :)

     

    I will go change my router DNS settings to the Google public servers mentioned in your post and see in the coming days what difference it may make. Seems sensible to first try that, I guess.

      JohnG666Author
      Enthusiast II
      May 30, 2022

      So do I take it that mine will be set to Virgin DNS Servers?

      Because the person didn’t explain why and what the new settings were, I was reluctant to change my settings!

       

      JohnG666Author
      Enthusiast II
      May 30, 2022

      Actually I just read something on the Virgin forums saying that the Hub3 has no facility to allow you to change the DNS servers!

       

      Ken_Griffiths
      Ken_Griffiths
      May 30, 2022

      So do I take it that mine will be set to Virgin DNS Servers?

      Because the person didn’t explain why and what the new settings were, I was reluctant to change my settings!

      The VirginMedia DNS servers are (usually):

      194.168.4.100 & 194.168.8.100

      I’ve just changed my router to the Google public DNS…  8.8.8.8 and 8.8.4.4 and will also try the cloudflare public DNS server 1.1.1.1 too when I get a chance, just to see if that makes any difference.

        JohnG666Author
        Enthusiast II
        May 30, 2022

        I’ve just been into my Hub3 settings and can see no way of changing my DNS servers so that is not an option for me. Thanks for trying this for me.

         

        Ken_Griffiths
        Ken_Griffiths
        May 30, 2022

        Actually I just read something on the Virgin forums saying that the Hub3 has no facility to allow you to change the DNS servers!

        Ah okay, The only way around such ISP restrictions would likely be to use their Superhub in "modem mode" and just add your own router.

        I personally prefer to have my own router, but appreciate that’s not going to be the case for everyone. 

        If it does prove to be a DNS issue, I assume you could take-up the issue with VirginMedia, I guess🤔?, but perhaps let’s see what happens now that I’ve switched to the DNS servers suggested.  

          ratty
          ratty
          May 30, 2022

          I’ve just been into my Hub3 settings and can see no way of changing my DNS servers so that is not an option for me. Thanks for trying this for me.

           

          There are ways of achieving this. Probably the easiest would be to put the Hub3 into modem mode and run your own wireless router instead. (Edit: Ken got there first on this point.)

          Alternatively (if feasible) disable the Hub3’s DHCP server and run your own somewhere on the LAN. Since your own DHCP server could well be a re-purposed Ethernet router it might be argued that you may as well go for the first option, unless you already had an old low-power router lying around.

          FWIW I don’t rely solely on my ISP’s DNS (I’m with BT), having had periodic resolution failures in times gone by. I supplement the BT servers with Cloudflare. 

            JohnG666Author
            Enthusiast II
            May 30, 2022

            For a while now I have been thinking of getting my own router - one with at least 4 gigabit network ports and wifi. At the moment with my Superhub3 I can only have one wired Sonos speaker whereas when I had my own router before (it broke so had to switch hub3 into router mode) I had most of my speakers wired.

            I’ve had my eye on a TP-Link AX1800 on Amazon as it seems to get a lot of good reviews but it always feels like it’s going to be a hassle having to reconfigure things and keep my fingers crossed that it doesn’t cause any issues with Sonos.

             

            Show more replies
            Terms & ConditionsAccessibility statement