Announcement

Collapse
No announcement yet.

Add Sonos device manually

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

    Add Sonos device manually

    Hi,

    Is it possible to add a sonos device manually?

    My Homeseer server is on an other subnet and even though I've got multicast routing enabled the plugin can't find the device. This is probably because the pim-sm only allows 224.0.0.0/4 traffic. SSDP (239.255.255.250) or MADCAP (239.255.255.254) traffic isn't allowed to go through the firewall.

    My other computers that are on the same subnet as the Homeseer server are able to connect to the sonos device using only multicast.
    On the Micassa Vera Egde it is possible to add the ip address of the sonos manual so I was hoping I could do the same on Homeseer.

    #2
    Originally posted by alan_smithee View Post
    Hi,

    Is it possible to add a sonos device manually?

    My Homeseer server is on an other subnet and even though I've got multicast routing enabled the plugin can't find the device. This is probably because the pim-sm only allows 224.0.0.0/4 traffic. SSDP (239.255.255.250) or MADCAP (239.255.255.254) traffic isn't allowed to go through the firewall.

    My other computers that are on the same subnet as the Homeseer server are able to connect to the sonos device using only multicast.
    On the Micassa Vera Egde it is possible to add the ip address of the sonos manual so I was hoping I could do the same on Homeseer.
    Which version of the PI are you using? The UPNP subsystem between the 3.0.x.x and 3.1.x.x baselines are different but I suspect neither would work if SSDP isn't enabled between subnets nor do I think UPNP was supposed to allow a TTL>1 but the latter I could be wrong.
    No there is no option to add manually. When you say "my other computers are able to connect", are you referring to the Sonos controller app or what program on the other computer can connect to the Sonos player on another subnet?
    Not sure whether there are other computers on the same subnet as the Sonos players but if there are, you could try to run the Sonos PI remotely on a computer that is part of the same subnet as the players.

    Thanks

    Dirk

    Comment


      #3
      Hi Dirk, thank you for your fast response.

      Which version of the PI are you using?
      I'm running version 3.1.0.16 on a debian server.

      When you say "my other computers are able to connect", are you referring to the Sonos controller app or what program on the other computer can connect to the Sonos player on another subnet?
      I had to test if the multicast routing was working and I used the official sonos controller app on OSX.

      No there is no option to add manually.
      Would this be easy to implement?

      Not sure whether there are other computers on the same subnet as the Sonos players but if there are, you could try to run the Sonos PI remotely on a computer that is part of the same subnet as the players.
      Not sure if I understand correctly. Do you mean moving the homeseer server to the other subnet or is there something like an intermediate server that can relay the sonos request?

      Comment


        #4
        Originally posted by alan_smithee View Post
        Hi Dirk, thank you for your fast response.


        I'm running version 3.1.0.16 on a debian server.


        I had to test if the multicast routing was working and I used the official sonos controller app on OSX.


        Would this be easy to implement?


        Not sure if I understand correctly. Do you mean moving the homeseer server to the other subnet or is there something like an intermediate server that can relay the sonos request?
        Version 3.1.x.x has a UPNP subsystem I rolled, so interesting to read that the Sonos APP works, so this might be something I could "enhance", not sure how to debug it or test it, need to think about that. If you have a windows machine, I would be interested to know whether the 3.0.x.x version works (uses Windows UPNP/SSDP subsystem).

        As of HS3, plugins can work remotely, meaning they don't have to run on the same machine as HS3. As of HS3, all PIs run as stand alone executables and make use of (forgot name) some communication mechanisms which I suspect run over TCP Sockets. The PI was designed (and coarsely tested) to run on another machine. I may have to verify the right syntax when I'm at home but you would start the PI on another machine something like HSPI_Sonos.exe SERVER=xx.xx.xx.xx which will establish a comm pipe between this PI on this machine and HS3 running on another machine. The only thing to watch out for is that the PI expects the right subdirectory structure to be in place so the easiest way to do that is to install HS3 on the remote machine and use the installer to install the PI. Once that is done, there is no need to run HS3 on that machine, just manually start the PI with the HS3 IP address (and run as administrator if under windows). Another note, if the PI terminates for any reason, HS3 won't be able to restart it, you would have to add for example a task to restart the PI.

        As to your last question whether it is easy to add functions to manually add players, the answer is no, all code was written around dynamically discovering players including, recoveries when they go away or come back; it would be a pretty large task.

        Dirk

        Comment


          #5
          I'll install the windows version this weekend to see if there is a difference in the two and post the result.

          This kind of software architecture is pretty cool. Is this used for offloading tasks of the hs3 server or mainly for developing purposes?

          Comment


            #6
            Originally posted by alan_smithee View Post
            I'll install the windows version this weekend to see if there is a difference in the two and post the result.

            This kind of software architecture is pretty cool. Is this used for offloading tasks of the hs3 server or mainly for developing purposes?
            HomeSeer created the remote running of PIs to allow you for example to have HS3 running at home and the z-wave or alarm/security PI running in your vacation home or other properties you may have, while controlling it all from home.

            Dirk

            Comment


              #7
              I've just installed the homeseer on windows with sonos pi version 3.0.x.x but this had the same result.

              Then I moved the homeseer server to my other subnet and now everything is working. I hope sophos UTM will support SSDP one day.

              Comment

              Working...
              X