Announcement

Collapse
No announcement yet.

Noticed error in log

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Noticed error in log

    Hi,

    Have sometimes noticed that there is a error in the log from the Sonos plugin.
    Have not noticed any trouble regarding usage.

    When I restart the plugin I get these errors:
    okt-27 23:20:30 Sonos Registered SpeakerProxy
    okt-27 23:20:30 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Eine with index 6
    okt-27 23:20:30 Sonos Error Error in Adding VirtualLineIn Call Back for zoneplayer = Eine. Error=Error in MyUPnPService.AddCallback while sending URL = http://192.168.10.187:1400/MediaRend...alLineIn/Event to = http://192.168.10.187:1400/MediaRend...alLineIn/Event with error = The remote server returned an error: (503) Server Unavailable.
    okt-27 23:20:30 Sonos DirectConnect called for Zone Eine with device name = uuid:RINCON_B8E937B6FAB601400 and Model = S1
    okt-27 23:20:29 Starting Plug-In Plugin Sonos started successfully in 8 milliseconds
    okt-27 23:20:29 Sonos InitIO Called for Instance = RINCON_B8E937B6FAB601400 and running on OS = Win32NT
    okt-27 23:20:29 Starting Plug-In Initializing plugin Sonos ...
    okt-27 23:20:29 Info Plugin Sonos with instance RINCON_B8E937B6FAB601400 has connected. IP:127.0.0.1:60173
    okt-27 23:20:29 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Bad with index 5
    okt-27 23:20:29 Sonos Error Error in Adding VirtualLineIn Call Back for zoneplayer = Bad. Error=Error in MyUPnPService.AddCallback while sending URL = http://192.168.10.186:1400/MediaRend...alLineIn/Event to = http://192.168.10.186:1400/MediaRend...alLineIn/Event with error = The remote server returned an error: (503) Server Unavailable.
    okt-27 23:20:28 Sonos DirectConnect called for Zone Bad with device name = uuid:RINCON_B8E937864BD801400 and Model = S1
    okt-27 23:20:27 Starting Plug-In Plugin Sonos started successfully in 8 milliseconds
    okt-27 23:20:27 Sonos InitIO Called for Instance = RINCON_B8E937864BD801400 and running on OS = Win32NT
    okt-27 23:20:27 Starting Plug-In Initializing plugin Sonos ...
    okt-27 23:20:27 Info Plugin Sonos with instance RINCON_B8E937864BD801400 has connected. IP:127.0.0.1:60144
    okt-27 23:20:27 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Kjøkken with index 4
    okt-27 23:20:27 Sonos Error Error in Adding VirtualLineIn Call Back for zoneplayer = Kjøkken. Error=Error in MyUPnPService.AddCallback while sending URL = http://192.168.10.111:1400/MediaRend...alLineIn/Event to = http://192.168.10.111:1400/MediaRend...alLineIn/Event with error = The remote server returned an error: (503) Server Unavailable.
    okt-27 23:20:27 Sonos DirectConnect called for Zone Kjøkken with device name = uuid:RINCON_B8E9378EA8E601400 and Model = S1
    okt-27 23:20:26 Starting Plug-In Plugin Sonos started successfully in 10 milliseconds
    okt-27 23:20:26 Sonos InitIO Called for Instance = RINCON_B8E9378EA8E601400 and running on OS = Win32NT
    okt-27 23:20:26 Starting Plug-In Initializing plugin Sonos ...
    okt-27 23:20:26 Info Plugin Sonos with instance RINCON_B8E9378EA8E601400 has connected. IP:127.0.0.1:60114
    okt-27 23:20:26 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Ingvild with index 3
    okt-27 23:20:26 Sonos Error Error in Adding VirtualLineIn Call Back for zoneplayer = Ingvild. Error=Error in MyUPnPService.AddCallback while sending URL = http://192.168.10.228:1400/MediaRend...alLineIn/Event to = http://192.168.10.228:1400/MediaRend...alLineIn/Event with error = The remote server returned an error: (503) Server Unavailable.
    okt-27 23:20:26 Sonos DirectConnect called for Zone Ingvild with device name = uuid:RINCON_B8E937B7044C01400 and Model = S1
    okt-27 23:20:25 Starting Plug-In Plugin Sonos started successfully in 8 milliseconds
    okt-27 23:20:25 Sonos InitIO Called for Instance = RINCON_B8E937B7044C01400 and running on OS = Win32NT
    okt-27 23:20:25 Starting Plug-In Initializing plugin Sonos ...
    okt-27 23:20:25 Info Plugin Sonos with instance RINCON_B8E937B7044C01400 has connected. IP:127.0.0.1:60087
    okt-27 23:20:25 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Playbar with index 2
    okt-27 23:20:25 Sonos Error Error in Adding VirtualLineIn Call Back for zoneplayer = Playbar. Error=Error in MyUPnPService.AddCallback while sending URL = http://192.168.10.171:1400/MediaRend...alLineIn/Event to = http://192.168.10.171:1400/MediaRend...alLineIn/Event with error = The remote server returned an error: (503) Server Unavailable.
    okt-27 23:20:24 Sonos DirectConnect called for Zone Playbar with device name = uuid:RINCON_5CAAFD16BDDE01400 and Model = S9
    okt-27 23:20:24 Starting Plug-In Plugin Sonos started successfully in 7 milliseconds
    okt-27 23:20:24 Sonos InitIO Called for Instance = RINCON_5CAAFD16BDDE01400 and running on OS = Win32NT
    okt-27 23:20:24 Starting Plug-In Initializing plugin Sonos ...
    okt-27 23:20:23 Info Plugin Sonos with instance RINCON_5CAAFD16BDDE01400 has connected. IP:127.0.0.1:60059
    okt-27 23:20:23 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Loftstue with index 1
    okt-27 23:20:23 Sonos Error Error in Adding VirtualLineIn Call Back for zoneplayer = Loftstue. Error=Error in MyUPnPService.AddCallback while sending URL = http://192.168.10.147:1400/MediaRend...alLineIn/Event to = http://192.168.10.147:1400/MediaRend...alLineIn/Event with error = The remote server returned an error: (503) Server Unavailable.
    okt-27 23:20:23 Sonos DirectConnect called for Zone Loftstue with device name = uuid:RINCON_5CAAFD4557A001400 and Model = S1
    okt-27 23:20:22 Starting Plug-In Plugin Sonos started successfully in 11 milliseconds
    okt-27 23:20:22 Sonos InitIO Called for Instance = RINCON_5CAAFD4557A001400 and running on OS = Win32NT
    okt-27 23:20:22 Starting Plug-In Initializing plugin Sonos ...
    okt-27 23:20:22 Info Plugin Sonos with instance RINCON_5CAAFD4557A001400 has connected. IP:127.0.0.1:60032
    okt-27 23:19:41 Plug-In Finished initializing plug-in Sonos
    okt-27 23:19:41 Starting Plug-In Sonos loaded in 605 milliseconds
    okt-27 23:19:41 Starting Plug-In Plugin Sonos started successfully in 215 milliseconds
    okt-27 23:19:41 Sonos Sonos Plugin Initialized
    okt-27 23:19:40 Sonos InitIO Called for Instance =
    okt-27 23:19:40 Sonos InitIO for Instance = found this plugin running on Linux = False
    okt-27 23:19:40 Sonos InitIO Called for Instance = and running on OS = Win32NT
    okt-27 23:19:40 Sonos InitIO for Instance = found HS running on Linux = False
    okt-27 23:19:40 Sonos InitIO for Instance = found CurrentAppPath = C:\Program Files (x86)\HomeSeer HS3
    okt-27 23:19:40 Starting Plug-In Initializing plugin Sonos ...
    okt-27 23:19:40 Info Plugin Sonos has connected. IP:127.0.0.1:59923

    But after letting the plugin settle for a while, I can't seem to notice any impact on the usage.
    Without any deep testing, the speakers are working as it should in our daily lives.

    Any thoughts?
    Tags: None
    #2
    I started getting those errors a couple months ago whenever I restarted the PI. I didn't change anything so figured it must have been a Windows or Unifi update that did something. It was still working okay so I hadn't really looked into it very much. I'm now running the latest beta and the errors are gone. They actually went away a few beta versions back (within the last couple weeks).

    Comment

      #3
      May I suggest that the first thing I recommend people to do, is to take a key word of the error and plug it into the search bar of this forum or google it.
      In a lot of cases, you may find an analysis or conclusion to your issue(s).
      This error is benign, I'm sure some of it was caused by me and some more was caused by some Sonos SW changes.
      There is a new Sonos version in the Beta section of the updater, it has a bunch of other changes but this error should be gone.
      Cheers,
      Dirk

      Comment

        #4
        Hi,

        I'm have been running the beta for a long time now and I'm already on 3.1.0.36.

        Comment

          #5
          Originally posted by Groot View Post
          Hi,

          I'm have been running the beta for a long time now and I'm already on 3.1.0.36.
          Beta is at v45

          Comment

          Previous template Next
          Working...
          X