Announcement

Collapse
No announcement yet.

Duplicate Sonos Players

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Duplicate Sonos Players

    I have six Sonos devices in my house. The app keeps generating duplicate entries for certain devices. Is this normal? And if not, any thoughts on how to fix it? I've tried deleting the dupes but either they won't delete or they just repopulate. Thanks for any help.

    I've attached a screenshot of the PI, and the log is below.


    Click image for larger version

Name:	Screenshot 2018-09-14 06.14.20.png
Views:	13
Size:	389.1 KB
ID:	1247275
    Sep-14 6:15:30 AM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_000E582C370001400
    Sep-14 6:15:20 AM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_000E58A027C601400
    Sep-14 6:15:10 AM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E9375F6E7201400
    Sep-14 6:10:56 AM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Entry with index 6
    Sep-14 6:10:55 AM Starting Plug-In Plugin Sonos started successfully in 3 milliseconds
    Sep-14 6:10:55 AM Starting Plug-In Initializing plugin Sonos ...
    Sep-14 6:10:55 AM Info Plugin Sonos with instance RINCON_000E58796FD001400 has connected. IP:127.0.0.1:2912
    Sep-14 6:10:55 AM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Bedroom with index 2
    Sep-14 6:10:54 AM Starting Plug-In Plugin Sonos started successfully in 8 milliseconds
    Sep-14 6:10:54 AM Starting Plug-In Initializing plugin Sonos ...
    Sep-14 6:10:53 AM Info Plugin Sonos with instance RINCON_949F3ED5B68701400 has connected. IP:127.0.0.1:2850
    Sep-14 6:10:53 AM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_000E58A027C601400
    Sep-14 6:10:52 AM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_000E582C370001400
    Sep-14 6:10:51 AM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E9375F6E7201400
    Sep-14 6:10:50 AM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Den with index 5
    Sep-14 6:10:48 AM Starting Plug-In Plugin Sonos started successfully in 3 milliseconds
    Sep-14 6:10:48 AM Starting Plug-In Initializing plugin Sonos ...
    Sep-14 6:10:48 AM Info Plugin Sonos with instance RINCON_000E58A027C601400 has connected. IP:127.0.0.1:2800
    Sep-14 6:10:48 AM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Living Room with index 4
    Sep-14 6:10:46 AM Starting Plug-In Plugin Sonos started successfully in 6 milliseconds
    Sep-14 6:10:46 AM Starting Plug-In Initializing plugin Sonos ...
    Sep-14 6:10:46 AM Info Plugin Sonos with instance RINCON_000E582C370001400 has connected. IP:127.0.0.1:2767
    Sep-14 6:10:46 AM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Deck with index 3
    Sep-14 6:10:43 AM Starting Plug-In Plugin Sonos started successfully in 3 milliseconds
    Sep-14 6:10:43 AM Starting Plug-In Initializing plugin Sonos ...
    Sep-14 6:10:43 AM Info Plugin Sonos with instance RINCON_000E5888515A01400 has connected. IP:127.0.0.1:2732
    Sep-14 6:10:43 AM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Patio with index 1
    Sep-14 6:10:42 AM Starting Plug-In Plugin Sonos started successfully in 4 milliseconds
    Sep-14 6:10:42 AM Starting Plug-In Initializing plugin Sonos ...
    Sep-14 6:10:41 AM Info Plugin Sonos with instance RINCON_B8E9375F6E7201400 has connected. IP:127.0.0.1:2702
    Sep-14 6:09:56 AM Starting Plug-In Plugin Sonos started successfully in 1845 milliseconds
    Sep-14 6:09:56 AM Sonos Sonos Plugin Initialized
    Sep-14 6:09:54 AM Starting Plug-In Initializing plugin Sonos ...
    Sep-14 6:09:12 AM Info Plugin Sonos has connected. IP:127.0.0.1:2276
    Sep-14 6:09:12 AM Plug-In Finished initializing plug-in Sonos
    Sep-14 6:09:02 AM Plug-In Found plug-in: Sonos, version: 3.1.0.24

  • #2
    This just happened to me this week, on my system another plugin was causing HS to run out of memory, when about to crash a bunch of plugins started acting very weird including Sonos which wound up creating numerous duplicate devices. Might be worth checking your log to see if your system is restarting more than you realize (took me a bit to notice since HSSentry was masking the issue)...

    Comment


    • #3
      Originally posted by bsobel View Post
      This just happened to me this week, on my system another plugin was causing HS to run out of memory, when about to crash a bunch of plugins started acting very weird including Sonos which wound up creating numerous duplicate devices. Might be worth checking your log to see if your system is restarting more than you realize (took me a bit to notice since HSSentry was masking the issue)...
      Thanks. I looked at that. No resets in an hour and no other errors. The Sonos PI is trying to recreate those three dupes every five minutes to the second though.

      Comment


      • #4
        Originally posted by pcourt View Post

        Thanks. I looked at that. No resets in an hour and no other errors. The Sonos PI is trying to recreate those three dupes every five minutes to the second though.
        If the PI creates them every 5 minutes, how are you deleting them? Have you or are you deleting these "duplicate" devices from the HS device management page? That is a big no-no! Pretty sure your HS database is out of sync with your Sonos PI DB, either because HS crapped out (and from your posting it doesn't look like the cause) or a manual step like deleting from devices management page or copy/paste setups between PCs. Which version of the PI are you using? If you are still on 3.0.x.x the delete all might not work due to changes in HS itself that were made over the years after that version was end-of-life'd.

        You get out of this by

        stop HS
        delete the sonos.ini file
        restart HS

        All devices will be cleaned up and recreated.



        Dirk

        Comment


        • #5
          Originally posted by bsobel View Post
          This just happened to me this week, on my system another plugin was causing HS to run out of memory, when about to crash a bunch of plugins started acting very weird including Sonos which wound up creating numerous duplicate devices. Might be worth checking your log to see if your system is restarting more than you realize (took me a bit to notice since HSSentry was masking the issue)...
          This would mean that the HS database got corrupted and when the PI restarts, it doesn't find its devices in the HS database and recreates causing duplicated devices. See steps above to remedy.

          Comment


          • #6
            Thanks for all the responses. I'm not at home, but I did update the PI to the latest just last night. I am not trying to delete the devices from the Device Management page.
            When I try to delete them in the PI, the pop-up confirmation dialogue just stays there after I confirm it and nothing happens. I can hit the X to get rid of that dialogue.

            And yes, HS has been working fine overall. And I have not been trying to copy the database or anything.

            I have deleted the Sonos.ini a number of times, I think with HS stopped, but I will try that for sure when I get home. Do I need to delete the Sonos.ini backup file too?

            And just to be clear, by stopping Homeseer you mean shutting it down by clicking the X in the upper right hand corner of box that pops up when I start it? I just want to make sure there's not some other sub-process or something going on that I need to stop as well.

            I'll try all this and report back.

            Comment


            • #7
              Originally posted by pcourt View Post
              Thanks for all the responses. I'm not at home, but I did update the PI to the latest just last night. I am not trying to delete the devices from the Device Management page.
              Do I need to delete the Sonos.ini backup file too?

              And just to be clear, by stopping Homeseer you mean shutting it down by clicking the X in the upper right hand corner of box that pops up when I start it? I just want to make sure there's not some other sub-process or something going on that I need to stop as well.

              I'll try all this and report back.
              No need to delete the .ini backup file but crucial HS is stopped because it cashes the ini files. You would stop HS indeed by clicking on the x and confirm. That should do it unless you have some autostart script which restarts HS by itself. Come to think of it, didn't I read somewhere that HSSentry active will auto start HS even if you stop it manually, so check your HSSentry setting, turn off first if it was selected.

              If things still go sideways after deleting the Sonos.ini file, something else is seriously wrong. Always make sure HS runs as admin ESPECIALLY if it is installed in the default location under "Program files (x86)" because that directory tree is write protected and could explain a lot of DB problems.

              Dirk

              Comment


              • #8
                Originally posted by dcorsus View Post

                No need to delete the .ini backup file but crucial HS is stopped because it cashes the ini files. You would stop HS indeed by clicking on the x and confirm. That should do it unless you have some autostart script which restarts HS by itself. Come to think of it, didn't I read somewhere that HSSentry active will auto start HS even if you stop it manually, so check your HSSentry setting, turn off first if it was selected.

                If things still go sideways after deleting the Sonos.ini file, something else is seriously wrong. Always make sure HS runs as admin ESPECIALLY if it is installed in the default location under "Program files (x86)" because that directory tree is write protected and could explain a lot of DB problems.

                Dirk
                So I verified it's 3.1.0.24. Verified Sentry is not running. Shutdown HS. Checked Task Manager for anything else running. Shutdown even the HS speaker. Deleted the Sonos.ini. Launched HS again, same problem. Then I even moved the HS3 directory out of Program Files (X86) to a new HomeSeer directory right off C and that did not work either. It's just those three players each time. The other three are fine.

                Appreciate any help.
                Sep-14 1:58:17 PM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E9375F6E7201400
                Sep-14 1:58:07 PM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_000E582C370001400
                Sep-14 1:57:57 PM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_000E58A027C601400
                Sep-14 1:57:43 PM DirecTV INFO CMD SENT: http://192.168.0.2:8080/info/mode?clientAddr=0
                Sep-14 1:53:39 PM Sonos Registered SpeakerProxy
                Sep-14 1:53:39 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Entry with index 6
                Sep-14 1:53:39 PM Sonos DirectConnect called for Zone Entry with device name = uuid:RINCON_000E58796FD001400 and Model = S3
                Sep-14 1:53:38 PM Starting Plug-In Plugin Sonos started successfully in 3 milliseconds
                Sep-14 1:53:38 PM Sonos InitIO Called for Instance = RINCON_000E58796FD001400 and running on OS = Win32NT
                Sep-14 1:53:38 PM Starting Plug-In Initializing plugin Sonos ...
                Sep-14 1:53:38 PM Info Plugin Sonos with instance RINCON_000E58796FD001400 has connected. IP:127.0.0.1:51709
                Sep-14 1:53:38 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Bedroom with index 2
                Sep-14 1:53:37 PM Sonos DirectConnect called for Zone Bedroom with device name = uuid:RINCON_949F3ED5B68701400 and Model = S14
                Sep-14 1:53:36 PM Starting Plug-In Plugin Sonos started successfully in 2 milliseconds
                Sep-14 1:53:36 PM Sonos InitIO Called for Instance = RINCON_949F3ED5B68701400 and running on OS = Win32NT
                Sep-14 1:53:36 PM Starting Plug-In Initializing plugin Sonos ...
                Sep-14 1:53:36 PM Info Plugin Sonos with instance RINCON_949F3ED5B68701400 has connected. IP:127.0.0.1:51680
                Sep-14 1:53:36 PM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_000E58A027C601400
                Sep-14 1:53:35 PM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_000E582C370001400
                Sep-14 1:53:34 PM Sonos Error Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E9375F6E7201400
                Sep-14 1:53:33 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Den with index 5
                Sep-14 1:53:32 PM Sonos DirectConnect called for Zone Den with device name = uuid:RINCON_000E58A027C601400 and Model = ZP90
                Sep-14 1:53:31 PM Starting Plug-In Plugin Sonos started successfully in 2 milliseconds
                Sep-14 1:53:31 PM Sonos InitIO Called for Instance = RINCON_000E58A027C601400 and running on OS = Win32NT
                Sep-14 1:53:31 PM Starting Plug-In Initializing plugin Sonos ...
                Sep-14 1:53:31 PM Info Plugin Sonos with instance RINCON_000E58A027C601400 has connected. IP:127.0.0.1:51590
                Sep-14 1:53:31 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Living Room with index 4
                Sep-14 1:53:30 PM Sonos DirectConnect called for Zone Living Room with device name = uuid:RINCON_000E582C370001400 and Model = ZP90
                Sep-14 1:53:29 PM Starting Plug-In Plugin Sonos started successfully in 4 milliseconds
                Sep-14 1:53:29 PM Sonos InitIO Called for Instance = RINCON_000E582C370001400 and running on OS = Win32NT
                Sep-14 1:53:29 PM Starting Plug-In Initializing plugin Sonos ...
                Sep-14 1:53:29 PM Info Plugin Sonos with instance RINCON_000E582C370001400 has connected. IP:127.0.0.1:51556
                Sep-14 1:53:29 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Deck with index 3
                Sep-14 1:53:27 PM Sonos DirectConnect called for Zone Deck with device name = uuid:RINCON_000E5888515A01400 and Model = S5
                Sep-14 1:53:26 PM Starting Plug-In Plugin Sonos started successfully in 6 milliseconds
                Sep-14 1:53:26 PM Sonos InitIO Called for Instance = RINCON_000E5888515A01400 and running on OS = Win32NT
                Sep-14 1:53:26 PM Starting Plug-In Initializing plugin Sonos ...
                Sep-14 1:53:26 PM Info Plugin Sonos with instance RINCON_000E5888515A01400 has connected. IP:127.0.0.1:51501
                Sep-14 1:53:26 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Patio with index 1
                Sep-14 1:53:26 PM Sonos DirectConnect called for Zone Patio with device name = uuid:RINCON_B8E9375F6E7201400 and Model = S1
                Sep-14 1:53:25 PM Starting Plug-In Plugin Sonos started successfully in 5 milliseconds
                Sep-14 1:53:25 PM Sonos InitIO Called for Instance = RINCON_B8E9375F6E7201400 and running on OS = Win32NT
                Sep-14 1:53:25 PM Starting Plug-In Initializing plugin Sonos ...
                Sep-14 1:53:25 PM Info Plugin Sonos with instance RINCON_B8E9375F6E7201400 has connected. IP:127.0.0.1:51473

                Comment


                • #9
                  Originally posted by pcourt View Post

                  So I verified it's 3.1.0.24. Verified Sentry is not running. Shutdown HS. Checked Task Manager for anything else running. Shutdown even the HS speaker. Deleted the Sonos.ini. Launched HS again, same problem. Then I even moved the HS3 directory out of Program Files (X86) to a new HomeSeer directory right off C and that did not work either. It's just those three players each time. The other three are fine.
                  Let's go back to basics. Where do you delete the sonos.ini file? Have you checked it is actually deleted (seen some weird behavior that the file was locked (or owned by different user) and actually delete didn't really delete it). Is this a VM?

                  What I would like you to do is the same thing:

                  stop HS
                  copy/paste the ini file here on your response
                  go to <hs root>/config and delete sonos.ini
                  check it is really gone
                  Start HS
                  capture the startup log.
                  post the new .ini file

                  There should be log entries from the Sonos PI indicating that it didn't find an ini file and is deleting all HS associated devices.

                  The log above still shows that the same player is being created twice. Recommend you also post the .ini file before you delete it and post the ini file after delete and restart of HS.

                  We'll figure it out.

                  Dirk

                  Comment


                  • #10
                    Dirk, Thanks for your help. The issue resolved itself. I'll try to explain how. One of your earlier posts cited the problem with the Program Files (x86). I created a separate directory off of C just for HomeSeer. But I must have screwed up moving / copying the files. When I went to restart HS, not only did I have to enter my license code, but everything, devices and plugins, was gone from HS. It was like a virgin birth of HS. I went to just move everything back to the original directory and got the Duplicate file warning. Obviously I screwed up and had created two partial or complete HS directories.

                    Anyway, once I sorted that out (and I deleted the Sonos.ini along the way) the Sonos player list rebuilt correctly. I promise you I had deleted the Sonos.ini several times before this (there are seven copies in my Recycle bin), but somehow it did not "take" until I screwed up moving around the entire directory. So works great now and no errors. Thanks again for your help.

                    Comment

                    Working...
                    X