Announcement

Collapse
No announcement yet.

Reinstalling Sonos on new database

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

    Reinstalling Sonos on new database

    Dirk,

    I am in the proces of reinstalling and recreating all devices and events for my installation. Hoping to eliminate events freezing here, something only I seem to experience.

    I was in the progress of recreating the devices for the sonos plugin, but that is going very wrong here. If I activate the plugin for the first time on the new database, it is throwing errors while creating the parent devices. It does not create the child devices anymore. I have attached the HS3 log for this as "sonosfirststart.txt".

    If I then restart the plugin it complains it finds devices which are not found in the corresponding ini file. Probably caused by the errors during the first start. Then it tries to create the child devices, which are created, but again throwing errors. Those devices are not created as child devices, causing parent/child relations not to be visible anymore. Leaving my devices in a mess. The created devices are not updated. This second start is also added as a log file.

    On the config page, after the second start, the player table is adding 3 "?" devices, one less then the number of devices (playbar/sub/2xS3) that I have active. With each subsequent restart it is again adding 3 devices to the player table.

    I don't know what is causing these errors?

    Wim
    Attached Files
    -- Wim

    Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

    1210 devices/features ---- 392 events ----- 40 scripts

    #2
    Wim,

    I'm traveling for the next two weeks so a bit harder to study logs.
    Which version of the PI are you using?
    Suggest you stop HS; delete the Sonos.ini file from the confit directory; restart HS

    This should delete all devices and recreate. Make sure you run HS and PI as administrator.

    Dirk

    Comment


      #3
      Dirk,

      It took me a while to do a new try. Trying to prevent myself of reinventing all events in my system


      I backed out the HS3 database, removed ini's and other traces of the plugin and reinstalled the sonos beta plugin. Results are exactly the same is before. Initially it will only create the parent devices, throw a bunch of errors (see txt file of original post).
      Each restart will again add devices and more errors, and the devices will not be created as child devices for the parent device.

      This is with a clean start?

      Wim
      -- Wim

      Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

      1210 devices/features ---- 392 events ----- 40 scripts

      Comment


        #4
        Dirk,

        I tried here several restarts on an initial HS3 database. After a few tries I started HS3 with the Sonos plugin already enabled in the configuration.

        This is where the creation of devices went better! Enabling the sonos plugin while HS3 is running goes wrong, and with a full restart on an initial HS3 database seems to be doing allright.

        There is only one error coming back still then:


        nov-16 12:24:10 Speaker Speaker host added, Name: Visnet-Homeseer Instance: Default IP address: 127.0.0.1
        nov-16 12:24:10 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = SUB with index 3
        nov-16 12:24:10 Sonos DirectConnect called for Zone SUB with device name = uuid:RINCON_5CAAFD8212A001400 and Model = Sub
        nov-16 12:24:09 Sonos InitIO Called for Instance = RINCON_5CAAFD8212A001400 and running on OS = Win32NT
        nov-16 12:24:09 Info Plugin Sonos with instance RINCON_5CAAFD8212A001400 has connected. IP:127.0.0.1:55447
        nov-16 12:24:09 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Huiskamer with index 4
        nov-16 12:24:08 Sonos Error Error in Adding RenderingControl Call Back for zoneplayer = Huiskamer. Error=Error in MyUPnPService.AddCallback while sending URL = http://[snip]/MediaRenderer/RenderingControl/Event to = http://[snip]:1400/MediaRenderer/RenderingControl/Event with error = De externe server heeft een fout geretourneerd: (500) Interne serverfout.
        nov-16 12:24:08 Sonos DirectConnect called for Zone Huiskamer with device name = uuid:RINCON_B8E937DB2DDE01400 and Model = S3
        nov-16 12:24:07 Sonos InitIO Called for Instance = RINCON_B8E937DB2DDE01400 and running on OS = Win32NT
        nov-16 12:24:07 Info Plugin Sonos with instance RINCON_B8E937DB2DDE01400 has connected. IP:127.0.0.1:55428
        nov-16 12:24:07 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Huiskamer with index 2
        nov-16 12:24:07 Sonos DirectConnect called for Zone Huiskamer with device name = uuid:RINCON_5CAAFD1C3B9101400 and Model = S9
        nov-16 12:24:06 Sonos InitIO Called for Instance = RINCON_5CAAFD1C3B9101400 and running on OS = Win32NT
        nov-16 12:24:06 Info Plugin Sonos with instance RINCON_5CAAFD1C3B9101400 has connected. IP:127.0.0.1:55394
        nov-16 12:24:06 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Huiskamer with index 1
        nov-16 12:24:06 Sonos Error Error in Adding RenderingControl Call Back for zoneplayer = Huiskamer. Error=Error in MyUPnPService.AddCallback while sending URL = http://[snip]:1400/MediaRenderer/RenderingControl/Event to = http://[snip]:1400/MediaRenderer/RenderingControl/Event with error = De externe server heeft een fout geretourneerd: (500) Interne serverfout.
        nov-16 12:24:06 Sonos DirectConnect called for Zone Huiskamer with device name = uuid:RINCON_B8E937DE13DA01400 and Model = S3
        nov-16 12:24:05 Sonos InitIO Called for Instance = RINCON_B8E937DE13DA01400 and running on OS = Win32NT
        nov-16 12:24:05 Info Plugin Sonos with instance RINCON_B8E937DE13DA01400 has connected. IP:127.0.0.1:55382


        I don't know if I have to worry on this one?

        Thanks,

        Wim
        -- Wim

        Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

        1210 devices/features ---- 392 events ----- 40 scripts

        Comment


          #5
          Originally posted by w.vuyk View Post
          Dirk,

          I tried here several restarts on an initial HS3 database. After a few tries I started HS3 with the Sonos plugin already enabled in the configuration.

          This is where the creation of devices went better! Enabling the sonos plugin while HS3 is running goes wrong, and with a full restart on an initial HS3 database seems to be doing allright.

          There is only one error coming back still then:


          nov-16 12:24:10 Speaker Speaker host added, Name: Visnet-Homeseer Instance: Default IP address: 127.0.0.1
          nov-16 12:24:10 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = SUB with index 3
          nov-16 12:24:10 Sonos DirectConnect called for Zone SUB with device name = uuid:RINCON_5CAAFD8212A001400 and Model = Sub
          nov-16 12:24:09 Sonos InitIO Called for Instance = RINCON_5CAAFD8212A001400 and running on OS = Win32NT
          nov-16 12:24:09 Info Plugin Sonos with instance RINCON_5CAAFD8212A001400 has connected. IP:127.0.0.1:55447
          nov-16 12:24:09 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Huiskamer with index 4
          nov-16 12:24:08 Sonos Error Error in Adding RenderingControl Call Back for zoneplayer = Huiskamer. Error=Error in MyUPnPService.AddCallback while sending URL = http://[snip]/MediaRenderer/RenderingControl/Event to = http://[snip]:1400/MediaRenderer/RenderingControl/Event with error = De externe server heeft een fout geretourneerd: (500) Interne serverfout.
          nov-16 12:24:08 Sonos DirectConnect called for Zone Huiskamer with device name = uuid:RINCON_B8E937DB2DDE01400 and Model = S3
          nov-16 12:24:07 Sonos InitIO Called for Instance = RINCON_B8E937DB2DDE01400 and running on OS = Win32NT
          nov-16 12:24:07 Info Plugin Sonos with instance RINCON_B8E937DB2DDE01400 has connected. IP:127.0.0.1:55428
          nov-16 12:24:07 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Huiskamer with index 2
          nov-16 12:24:07 Sonos DirectConnect called for Zone Huiskamer with device name = uuid:RINCON_5CAAFD1C3B9101400 and Model = S9
          nov-16 12:24:06 Sonos InitIO Called for Instance = RINCON_5CAAFD1C3B9101400 and running on OS = Win32NT
          nov-16 12:24:06 Info Plugin Sonos with instance RINCON_5CAAFD1C3B9101400 has connected. IP:127.0.0.1:55394
          nov-16 12:24:06 Sonos CreateOneSonosController: Created instance of ZonePlayerController for Zoneplayer = Huiskamer with index 1
          nov-16 12:24:06 Sonos Error Error in Adding RenderingControl Call Back for zoneplayer = Huiskamer. Error=Error in MyUPnPService.AddCallback while sending URL = http://[snip]:1400/MediaRenderer/RenderingControl/Event to = http://[snip]:1400/MediaRenderer/RenderingControl/Event with error = De externe server heeft een fout geretourneerd: (500) Interne serverfout.
          nov-16 12:24:06 Sonos DirectConnect called for Zone Huiskamer with device name = uuid:RINCON_B8E937DE13DA01400 and Model = S3
          nov-16 12:24:05 Sonos InitIO Called for Instance = RINCON_B8E937DE13DA01400 and running on OS = Win32NT
          nov-16 12:24:05 Info Plugin Sonos with instance RINCON_B8E937DE13DA01400 has connected. IP:127.0.0.1:55382


          I don't know if I have to worry on this one?

          Thanks,

          Wim
          Wim,

          Which version of the PI are you using?
          How many players and which kind?
          Are other players ok or only these two S3s?
          Have you tried restarting the Sonos players and try again?
          If problem with all players, have you checked your firewall setting on the PC?

          Dirk

          Comment


            #6
            Originally posted by dcorsus View Post
            Wim,

            Which version of the PI are you using?
            How many players and which kind?
            Are other players ok or only these two S3s?
            Have you tried restarting the Sonos players and try again?
            If problem with all players, have you checked your firewall setting on the PC?

            Dirk
            I saw an S9. Are the S3s paired with the S9? Didn't think it to be possible but just asking. If they are, unpair them, delete ini file, restart PI and have them completely discovered, than pair them again. The PI wouldn't support S3s paired with S9 properly as I thought that not to be possible and would require more coding to treat same as S1
            Dirk

            Comment


              #7
              Dirk,

              I am running the latest beta, 3.1.0.16, downloaded from the plugins page. Firewall was already disabled for testing purposes, so I could rule out this issue.
              I have a 5.1 config with one playbar, a SUB and two Play:3's all paired.

              I did restart the players with the first try, did not do this today.

              But the same errors occur with the 'old' production system, so these errors are consistent here. And the production system players have been restarted several times in the past few months.

              Wim
              -- Wim

              Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

              1210 devices/features ---- 392 events ----- 40 scripts

              Comment


                #8
                Originally posted by w.vuyk View Post
                Dirk,

                I am running the latest beta, 3.1.0.16, downloaded from the plugins page. Firewall was already disabled for testing purposes, so I could rule out this issue.
                I have a 5.1 config with one playbar, a SUB and two Play:3's all paired.

                I did restart the players with the first try, did not do this today.

                But the same errors occur with the 'old' production system, so these errors are consistent here. And the production system players have been restarted several times in the past few months.

                Wim

                Well that explains a lot. Wasn't aware S3s could be paired. Once paired Sonos "disables" a bunch of functions and that's why the services are not getting created.
                For time being, suggest you unpair, recreate all devices, pair again after all is created properly and for time being ignore the errors until I release a new PI version
                Dirk

                Comment

                Working...
                X