Announcement

Collapse
No announcement yet.

Sonos Errors on Startup - no TTS

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

    Sonos Errors on Startup - no TTS

    I just developed a new problem. Restarting HS3 has suddenly gotten very slow - takes up to 10 minutes, and when it does start, the Sonos plugin doesn't do TTS anymore. Oddly I get no errors in the log for a speaking event, I just get no TTS.

    I'm guessing it is related to Sonos errors that occur during startup:
    10/15/2017 9:34:15 PM ~!~Sonos Error~!~Error in AddInstance connecting or disconnecting InstanceName = RINCON_000E58BB17CC01400 with Error = :Object reference not set to an instance of an object.
    10/15/2017 9:34:16 PM ~!~Sonos Error~!~Error in CreateSonosControllers. Could not create instance of ZonePlayerController for zoneplayer = Master Bedroom with error = Object reference not set to an instance of an object.

    I tried deleting the ini file - no fix.
    Mark

    #2
    Originally posted by Mark S. View Post
    I just developed a new problem. Restarting HS3 has suddenly gotten very slow - takes up to 10 minutes, and when it does start, the Sonos plugin doesn't do TTS anymore. Oddly I get no errors in the log for a speaking event, I just get no TTS.

    I'm guessing it is related to Sonos errors that occur during startup:
    10/15/2017 9:34:15 PM ~!~Sonos Error~!~Error in AddInstance connecting or disconnecting InstanceName = RINCON_000E58BB17CC01400 with Error = :Object reference not set to an instance of an object.
    10/15/2017 9:34:16 PM ~!~Sonos Error~!~Error in CreateSonosControllers. Could not create instance of ZonePlayerController for zoneplayer = Master Bedroom with error = Object reference not set to an instance of an object.

    I tried deleting the ini file - no fix.
    Did you delete .ini file when HS3 was stopped?
    I assume we're talking about the sonos.ini file, right?

    Make sure you don't have the create music DB set to immediate, which could explain why HS3 would be very busy. Is the MediaAPI set, if it is, uncheck it.

    Dirk

    Comment


      #3
      Thanks, Dirk.

      Correct, I deleted the sonos ini when HS3 was not running.

      Auto Update and Immediate Update were/are not checked.

      I don't know what you mean by MediaAPI set.

      I am on HS3 3.0.0.297 and Sonos 3.0.0.21, running on a Hometroller S6.
      Mark

      Comment


        #4
        Originally posted by Mark S. View Post
        Thanks, Dirk.

        Correct, I deleted the sonos ini when HS3 was not running.

        Auto Update and Immediate Update were/are not checked.

        I don't know what you mean by MediaAPI set.

        I am on HS3 3.0.0.297 and Sonos 3.0.0.21, running on a Hometroller S6.
        MediaAPI is a checkbox on the config page, near the top of the page at the bottom of the right column.

        Click image for larger version

Name:	Capture.PNG
Views:	1
Size:	59.1 KB
ID:	1192721

        You probably should get the Sonos Beta 3.1.0.22 from the beta plug-ins section. 3.0.0.21 is going to be deprecated.
        HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

        Comment


          #5
          Originally posted by Mark S. View Post
          Thanks, Dirk.

          Correct, I deleted the sonos ini when HS3 was not running.

          Auto Update and Immediate Update were/are not checked.

          I don't know what you mean by MediaAPI set.

          I am on HS3 3.0.0.297 and Sonos 3.0.0.21, running on a Hometroller S6.
          Then I suspect that either the Sonos PI is a victim or the environment it runs on is poisoned.

          Check for other rogue behavior of other PIs or scripts; but I would start with resources, like memory, CPU, events that fire repeatedly, rogue scripts etc.

          Comment


            #6
            I don't see any other problems with HS3 or the Hometroller. I haven't really modified anything in months. The plugin just seemed to quit working, maybe after a reboot.

            This is not the first time the Sonos plugin got corrupted. Over the past 3 years or so, I'd say it has happened about 4 or 5 times. This is the only plugin where this has happened. Once the HS devices and the Sonos ini settings get out of synch, it seems to require a complete do-over because all my Sonos device numbers change.

            As you might imagine, it is many hours of work to recreate all the devices for 7 players, recreate 8 complex linkgroups, and then rebuild/modify a lot of events, scripts and HSTouch screens for the new devices.

            Is there an easier way? For example, is it possible to grab the old linkgroup settings and paste them into the new ini when I rebuild? Any way to specify or fix the device numbers for each player so I don't have to edit every single element of HSTouch screens? Any suggestions?
            Mark

            Comment


              #7
              Originally posted by Mark S. View Post
              I don't see any other problems with HS3 or the Hometroller. I haven't really modified anything in months. The plugin just seemed to quit working, maybe after a reboot.

              This is not the first time the Sonos plugin got corrupted. Over the past 3 years or so, I'd say it has happened about 4 or 5 times. This is the only plugin where this has happened. Once the HS devices and the Sonos ini settings get out of synch, it seems to require a complete do-over because all my Sonos device numbers change.

              As you might imagine, it is many hours of work to recreate all the devices for 7 players, recreate 8 complex linkgroups, and then rebuild/modify a lot of events, scripts and HSTouch screens for the new devices.

              Is there an easier way? For example, is it possible to grab the old linkgroup settings and paste them into the new ini when I rebuild? Any way to specify or fix the device numbers for each player so I don't have to edit every single element of HSTouch screens? Any suggestions?
              Did you try the Sonos Beta 3.1.0.22 as I suggested above? I never could get 3.0.0.21 to work correctly.
              HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

              Comment


                #8
                Originally posted by Mark S. View Post
                I don't see any other problems with HS3 or the Hometroller. I haven't really modified anything in months. The plugin just seemed to quit working, maybe after a reboot.

                This is not the first time the Sonos plugin got corrupted. Over the past 3 years or so, I'd say it has happened about 4 or 5 times. This is the only plugin where this has happened. Once the HS devices and the Sonos ini settings get out of synch, it seems to require a complete do-over because all my Sonos device numbers change.

                As you might imagine, it is many hours of work to recreate all the devices for 7 players, recreate 8 complex linkgroups, and then rebuild/modify a lot of events, scripts and HSTouch screens for the new devices.

                Is there an easier way? For example, is it possible to grab the old linkgroup settings and paste them into the new ini when I rebuild? Any way to specify or fix the device numbers for each player so I don't have to edit every single element of HSTouch screens? Any suggestions?
                Sorry but if device references between HS and the PI get out of sync it is almost in 100% of the cases caused by the user who starts to manually delete devices, restore HS databases that are out of sync and hardly ever due to an ini file corruption. In the latter case, the ini file is managed by HS as well and the PI hardly EVER writes in it. In the 7 years or so since this PI has been around, I can't recall any real ini file corruptions apart from what I described above.

                So I'm not saying that you didn't have issues over the years but I'm saying that there is something else going on. Perhaps memory corruption issue, overload issues, crashes, power outages, scheduled reboots, flash problems .....

                Maybe a debug log of HS3 and PI starting, wait 10 minutes to capture all the startup issues/delays and at the back-end of the 10 minutes, do a TTS and capture all of that in the log. Post log so we can have a look at what might be going on. Have you checked resources?

                Dirk

                Comment

                Working...
                X