Announcement

Collapse
No announcement yet.

HS3 Sonoscontroller beta testing forum

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

    Originally posted by jwigglesfv View Post
    I shut down HS3, deleted the sonos.ini and backup file and restarted.. still shows the same info under status.. any other tips or tricks ?
    You have to wait until (or force) the real owner updates the information!

    Comment


      I have Forced an update and still no luck

      also, how do I uninstall this plugin ? it does not have the red X to remove it. and even though it is disabled, it still shows up when I go to HStouch on my mobil device.
      Attached Files

      Comment


        Originally posted by jwigglesfv View Post
        also, how do I uninstall this plugin ? it does not have the red X to remove it. and even though it is disabled, it still shows up when I go to HStouch on my mobil device.
        Never knew why HS can't "remove" MultipleInstanceSingleEXE type of PIs, but as far as I can tell an HS thing.

        To remove, stop HS, delete hspi_sonos.exe from the HS root directory. Delete the sonos.ini file from the config subdirectory. Go to the <hs root>\html subdirectory and delete the sonos subdirectory.

        Start HS3 again. Delete the devices from the devices page.

        Done.

        Comment


          Hi!

          I've been developing a plug-in for HS3 and noticed something curious regarding devices created by the Sonos plug-in. It appears that some devices report slightly malformed image and HTML status values.

          For example, a device of the following type:

          Code:
          "device_type":{"Device_API":32,"Device_API_Description":"Music API","Device_Type":99,"Device_Type_Description":"Music Root Device","Device_SubType":0,"Device_SubType_Description":"Sonos Player Master Control"}
          When queried using CAPIGetStatus, the device returns the following ImageFile (notice the extra characters after the file extension):

          Code:
          "images/Sonos/Artwork/CoverRINCON_B8E93724A97A01400_268.jpg height="
          And it returns the following StatusHTML (notice the img.src element is not wrapped on quotes):

          Code:
          "<table><tr><td><img src=/images/Sonos/Artwork/CoverRINCON_B8E93724A97A01400_268.jpg height=\"150\"  width=\"150\" ></td><td><p>Playing</p><p>Stream Radio - Radio</p><p>Radio</p><p></p><p></p></td></tr></table>"
          It was possible to work around this, but thought it may be good to let you know

          Cheers,
          Antonio

          Comment


            Originally posted by avargaskun View Post
            Hi!

            I've been developing a plug-in for HS3 and noticed something curious regarding devices created by the Sonos plug-in. It appears that some devices report slightly malformed image and HTML status values.

            For example, a device of the following type:

            Code:
            "device_type":{"Device_API":32,"Device_API_Description":"Music API","Device_Type":99,"Device_Type_Description":"Music Root Device","Device_SubType":0,"Device_SubType_Description":"Sonos Player Master Control"}
            When queried using CAPIGetStatus, the device returns the following ImageFile (notice the extra characters after the file extension):

            Code:
            "images/Sonos/Artwork/CoverRINCON_B8E93724A97A01400_268.jpg height="
            And it returns the following StatusHTML (notice the img.src element is not wrapped on quotes):

            Code:
            "<table><tr><td><img src=/images/Sonos/Artwork/CoverRINCON_B8E93724A97A01400_268.jpg height=\"150\"  width=\"150\" ></td><td><p>Playing</p><p>Stream Radio - Radio</p><p>Radio</p><p></p><p></p></td></tr></table>"
            It was possible to work around this, but thought it may be good to let you know

            Cheers,
            Antonio

            Fixed it in V23 which will be posted in next week or so

            Comment


              Thanks

              I just wanted to say thanks for writing the Plugin.
              I set up TTS as described elsewhere with a Sonos Beam and it was fairly easy to set up.

              Comment


                Originally posted by emiliosic View Post
                I just wanted to say thanks for writing the Plugin.
                I set up TTS as described elsewhere with a Sonos Beam and it was fairly easy to set up.

                Keep an eye on updates for the PI. I received my Beam over the weekend and I probably need to make some small changes to make sure the PI doesn't do anything wrong when it groups/ungroups players to compose the linkgroup for the TTS. All benign stuff ....


                Dirk

                Comment


                  Originally posted by dcorsus View Post


                  Keep an eye on updates for the PI. I received my Beam over the weekend and I probably need to make some small changes to make sure the PI doesn't do anything wrong when it groups/ungroups players to compose the linkgroup for the TTS. All benign stuff ....


                  Dirk
                  I noticed an update from 3.1.0.22 to 3.1.0.24. Anything we should be aware of? Currently, only using with a Beam

                  Comment


                    Originally posted by emiliosic View Post

                    I noticed an update from 3.1.0.22 to 3.1.0.24. Anything we should be aware of? Currently, only using with a Beam
                    Changes described here (https://forums.homeseer.com/node/87447)

                    Comment

                    Working...
                    X