Announcement

Collapse
No announcement yet.

Errors - Duplicate Players?

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

  • Errors - Duplicate Players?

    I've had this issue for a while but have learned to work around it which usually involves disabling and reenabling the PI or power cycling the two sonos play1 devices. When both duplicate devices show an error it actually works correctly. This happens every time I have to restart HS. I would like to finally fix the issue but have ran out of options. I have completely removed the PI. Deleted the sonos.ini. Remove PI, reset the two sono play1 devices to factory settings, and then reinstalled the PI. Running HS3 .531, Sonos PI .28, and Windows 10

    The below log is after deleting the sonos.ini file and then restarting HS. The errors are for two sonos play1 devices connected as a surround sound set with playbar and sub. At one time I had named them Family Room_LR and Family Room_RR to differentiate them in the PI drop down selector and events (else all 3 show up as Family Room). I started getting these errors so, a few months back, I removed them from the surround sound group, factory reset the devices, and added them back. The settings in the sonos app shows them as Family Room (RS) and Family Room (LS). But I'm still getting the errors. It seems the Sonos PI is trying to add the playbar and both play1's as Family Room (I think that's correct) but then tries to add them again with old names (Family Room_LR and Family Room_RR). Any suggestion on what to do next? I would prefer to remove them completely since they are part of the surround sound set, is that possible?

    May-12 5:26:10 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Family Room with index 8
    May-12 5:26:10 PM Sonos Warning Warning in ZoneNameChanged where ZoneName in Array didn't match. Found = Family Room_LR supposed to = Family Room
    May-12 5:26:09 PM Sonos Warning Warning in ZoneNameChanged where ZoneName in Array didn't match. Found = Family Room_RR supposed to = Family Room
    May-12 5:26:09 PM Sonos DirectConnect called for Zone Family Room with device name = uuid:RINCON_949F3E62654101400 and Model = S9
    May-12 5:26:05 PM Starting Plug-In Plugin Sonos started successfully in 22 milliseconds
    May-12 5:26:05 PM Sonos InitIO Called for Instance = RINCON_949F3E62654101400 and running on OS = Win32NT
    May-12 5:26:05 PM Starting Plug-In Initializing plugin Sonos ...
    May-12 5:26:05 PM Info Plugin Sonos with instance RINCON_949F3E62654101400 has connected. IP:127.0.0.1:51038
    May-12 5:26:05 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Family Room_LR with index 7
    May-12 5:26:04 PM Sonos Error ERROR in GetLoudnessState for zoneplayer = Family Room with UPNP Error = Read only tag / Transport is locked / Access denied. Error = MyUPnPService.InvokeAction for ServiceID = http://172.16.0.32:1400/xml/RenderingControl1.xml while sending Action = GetLoudness for URI = http://172.16.0.32:1400/MediaRendere...ontrol/Control and Request = 0 Master UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 803 with error = The remote server returned an error: (500) Internal Server Error.
    May-12 5:26:04 PM Sonos DirectConnect called for Zone Family Room with device name = uuid:RINCON_949F3E86F8EC01400 and Model = S12
    May-12 5:26:00 PM Starting Plug-In Plugin Sonos started successfully in 11 milliseconds
    May-12 5:26:00 PM Sonos InitIO Called for Instance = RINCON_949F3E86F8EC01400 and running on OS = Win32NT
    May-12 5:26:00 PM Starting Plug-In Initializing plugin Sonos ...
    May-12 5:26:00 PM Info Plugin Sonos with instance RINCON_949F3E86F8EC01400 has connected. IP:127.0.0.1:51021
    May-12 5:26:00 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Gym with index 6
    May-12 5:26:00 PM Sonos DirectConnect called for Zone Gym with device name = uuid:RINCON_000E5879734601400 and Model = S3
    May-12 5:25:57 PM Starting Plug-In Plugin Sonos started successfully in 29 milliseconds
    May-12 5:25:57 PM Sonos InitIO Called for Instance = RINCON_000E5879734601400 and running on OS = Win32NT
    May-12 5:25:57 PM Starting Plug-In Initializing plugin Sonos ...
    May-12 5:25:56 PM Info Plugin Sonos with instance RINCON_000E5879734601400 has connected. IP:127.0.0.1:50997
    May-12 5:25:56 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Bathroom with index 5
    May-12 5:25:56 PM Sonos DirectConnect called for Zone Bathroom with device name = uuid:RINCON_7828CA02682C01400 and Model = S13
    May-12 5:25:53 PM Starting Plug-In Plugin Sonos started successfully in 14 milliseconds
    May-12 5:25:53 PM Sonos InitIO Called for Instance = RINCON_7828CA02682C01400 and running on OS = Win32NT
    May-12 5:25:53 PM Starting Plug-In Initializing plugin Sonos ...
    May-12 5:25:52 PM Info Plugin Sonos with instance RINCON_7828CA02682C01400 has connected. IP:127.0.0.1:50973
    May-12 5:25:52 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Family Room with index 4
    May-12 5:25:52 PM Sonos Error ERROR in GetLoudnessState for zoneplayer = Family Room with UPNP Error = Read only tag / Transport is locked / Access denied. Error = MyUPnPService.InvokeAction for ServiceID = http://172.16.0.31:1400/xml/RenderingControl1.xml while sending Action = GetLoudness for URI = http://172.16.0.31:1400/MediaRendere...ontrol/Control and Request = 0 Master UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 803 with error = The remote server returned an error: (500) Internal Server Error.
    May-12 5:25:52 PM Sonos DirectConnect called for Zone Family Room with device name = uuid:RINCON_949F3E830A7201400 and Model = S12
    May-12 5:25:48 PM Web Server Web Server authorized local login successful from: 172.16.0.55 User: Default
    May-12 5:25:48 PM Starting Plug-In Plugin Sonos started successfully in 10 milliseconds
    May-12 5:25:48 PM Sonos InitIO Called for Instance = RINCON_949F3E830A7201400 and running on OS = Win32NT
    May-12 5:25:48 PM Starting Plug-In Initializing plugin Sonos ...
    May-12 5:25:48 PM Info Plugin Sonos with instance RINCON_949F3E830A7201400 has connected. IP:127.0.0.1:50955
    May-12 5:25:48 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Office with index 3
    May-12 5:25:48 PM Sonos DirectConnect called for Zone Office with device name = uuid:RINCON_000E5879AA0A01400 and Model = S3
    May-12 5:25:44 PM Starting Plug-In Plugin Sonos started successfully in 8 milliseconds
    May-12 5:25:44 PM Sonos InitIO Called for Instance = RINCON_000E5879AA0A01400 and running on OS = Win32NT
    May-12 5:25:44 PM Starting Plug-In Initializing plugin Sonos ...
    May-12 5:25:44 PM Info Plugin Sonos with instance RINCON_000E5879AA0A01400 has connected. IP:127.0.0.1:50931
    May-12 5:25:44 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Living Room with index 2
    May-12 5:25:43 PM Sonos DirectConnect called for Zone Living Room with device name = uuid:RINCON_949F3E6511E001400 and Model = S9
    May-12 5:25:40 PM Starting Plug-In Plugin Sonos started successfully in 31 milliseconds
    May-12 5:25:40 PM Sonos InitIO Called for Instance = RINCON_949F3E6511E001400 and running on OS = Win32NT
    May-12 5:25:40 PM Starting Plug-In Initializing plugin Sonos ...
    May-12 5:25:40 PM Info Plugin Sonos with instance RINCON_949F3E6511E001400 has connected. IP:127.0.0.1:50907
    May-12 5:25:40 PM Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Master Bedroom with index 1
    May-12 5:25:40 PM Sonos DirectConnect called for Zone Master Bedroom with device name = uuid:RINCON_949F3E647DAB01400 and Model = S9
    May-12 5:25:36 PM Starting Plug-In Plugin Sonos started successfully in 12 milliseconds
    May-12 5:25:36 PM Sonos InitIO Called for Instance = RINCON_949F3E647DAB01400 and running on OS = Win32NT
    May-12 5:25:36 PM Starting Plug-In Initializing plugin Sonos ...
    May-12 5:25:36 PM Info Plugin Sonos with instance RINCON_949F3E647DAB01400 has connected. IP:127.0.0.1:50883
    May-12 5:25:36 PM Sonos CreatePlayerDevice: Created device Player with reference 3699 and ZoneModel = S9
    May-12 5:25:36 PM Sonos CreatePlayerDevice: Created device Player with reference 3698 and ZoneModel = S12
    May-12 5:25:35 PM Sonos CreatePlayerDevice: Created device Player with reference 3697 and ZoneModel = S3
    May-12 5:25:35 PM Sonos CreatePlayerDevice: Created device Player with reference 3696 and ZoneModel = S13
    May-12 5:25:35 PM Sonos CreatePlayerDevice: Created device Player with reference 3695 and ZoneModel = S12
    May-12 5:25:34 PM Sonos CreatePlayerDevice: Created device Player with reference 3694 and ZoneModel = S3
    May-12 5:25:34 PM Sonos CreatePlayerDevice: Created device Player with reference 3693 and ZoneModel = S9
    May-12 5:25:34 PM Sonos CreatePlayerDevice: Created device Player with reference 3692 and ZoneModel = S9
    May-12 5:24:53 PM Sonos InitializeSonosDevices is creating new MasterDevice with Ref = 3691
    May-12 5:24:53 PM Sonos Warning InitializeSonosDevices is deleting all existing HS devices
    May-12 5:24:52 PM Starting Plug-In Plugin Sonos started successfully in 1018 milliseconds
    May-12 5:24:52 PM Sonos Sonos Plugin Initialized
    May-12 5:24:51 PM Sonos InitIO Called for Instance =
    May-12 5:24:51 PM Sonos InitIO for Instance = found this plugin running on Linux = False
    May-12 5:24:51 PM Sonos InitIO Called for Instance = and running on OS = Win32NT
    May-12 5:24:51 PM Sonos InitIO for Instance = found HS running on Linux = False
    May-12 5:24:51 PM Sonos InitIO for Instance = found CurrentAppPath = C:\Program Files (x86)\HomeSeer HS3

  • #2
    These errors should be benign. When an S1 is paired with a playbar/beam it "looses" some of its functions because all functions, such as setting volume is now done through the master player ie the playbar/beam. Unfortunately, the Pi can't know in advance whether a player is paired or not until it is discovered, a bit of a chicken and egg issue.
    I suspect the errors you had in the past, having duplicate devices was a remnant of manually deleting players from the device page or DB corruption or porting between platforms ....
    This should be gone now that you deleted the sonos.ini file and the PI cleaned up all inconsistencies.
    I think for now you are in good shape, just don't delete any HS device from the HS device management page associated with this PI!
    Cheers,
    Dirk

    Comment


    • #3
      Unfortunately this happens every time I delete the sonos.ini so it doesn't appear to be correcting the problem; still creates Family Room_LR and _RR when devices with those names no longer exist. I would like to start completely over and remove everything. I've done this before but must have missed something, do you have a list of files the PI creates? Also wondering if this could be my sonos system and not the PI, is the "ZoneName in Array" coming from the PI?

      Comment


      • #4
        Originally posted by RGMessick View Post
        Unfortunately this happens every time I delete the sonos.ini so it doesn't appear to be correcting the problem; still creates Family Room_LR and _RR when devices with those names no longer exist. I would like to start completely over and remove everything. I've done this before but must have missed something, do you have a list of files the PI creates? Also wondering if this could be my sonos system and not the PI, is the "ZoneName in Array" coming from the PI?
        The PI automatically changes players names when they are paired, it is a long story and I wrote about it many times on this forum, its a Sonos thing that once the players are paired, they all report the player name of the master, so the PI has no way to know their original name and to make them appear differently for the user, the PI adds suffixes. You should stop HS3 when you delete the sonos.ini file because HS3 caches ini files, so deleting them while HS3 is running will definitely cause issues.
        If you really want the PI to have the original names of the players, you simply need to unpair them ALL when the PI is running. Once unpaired, the players report their original zone name and the PI will learn them and there is logic in the PI to avoid the names to get lost when they are paired. HOWEVER, if you start deleting things when zones are paired, all bets are off , but these are just names being renamed, all should work and the suffixes actually should help you understand which player is which. The duplicate zones is because of deleting things!

        Hope this helps,

        Dirk

        Comment


        • #5
          Hi,

          I have exactly the same errors, including the get loudness check. I will try unpairing

          regards

          Bart
          Regards Bart
          ------------------------------------------
          Win7 64Bit on Intel NUCI7 with SSD
          HSPRO 3.
          Devices; 1370 Events; 691

          Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

          Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

          Comment

          Working...
          X