Announcement

Collapse
No announcement yet.

Announcements not working since upgrade to .383 - Solved!

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

    #16
    Originally posted by Tomgru View Post
    crazy... tried that, now i see this in logs: (notice the 127 subnet now)

    Nov-21 11:43:02 AM
    *
    Sonos
    Registered SpeakerProxy
    Nov-21 11:43:02 AM
    *
    Sonos
    CreateSonosControllers called but no devices found
    Nov-21 11:42:38 AM
    *

    Plug-In
    Finished initializing plug-in Sonos
    Nov-21 11:42:22 AM
    *
    Sonos
    Sonos Plugin Initialized
    Nov-21 11:42:22 AM
    *
    Sonos
    InitIO Called for Instance =
    Nov-21 11:42:22 AM
    *
    Sonos
    InitIO for Instance = found this plugin running on Linux = False
    Nov-21 11:42:22 AM
    *
    Sonos
    InitIO Called for Instance = and running on OS = Win32NT
    Nov-21 11:42:22 AM
    *
    Sonos
    InitIO for Instance = found HS running on Linux = False
    Nov-21 11:42:22 AM
    *
    Sonos
    InitIO for Instance = found CurrentAppPath = C:\Program Files (x86)\HomeSeer HS3
    Nov-21 11:42:22 AM
    *
    Info
    Plugin Sonos has connected. IP:127.0.0.1:63420
    Nov-21 11:42:07 AM
    *
    Web Server
    Web Server started on IP Address 192.168.1.154, port 80
    Nov-21 11:42:07 AM
    *
    Web Server
    The web server has been bound specifically to IP address 192.168.1.154
    Nov-21 11:42:07 AM
    *
    Web Server
    Local IP address (subnet) is: 192.168.249.97 (255.255.255.240)
    Nov-21 11:42:07 AM
    *
    Web Server
    Web Server stopped
    There should be a second line like this one
    -> Nov-21 11:42:07 AM Info Plugin Sonos has connected. IP:127.0.0.1:63420

    Not sure why it is not working but now I'm starting to suspect that perhaps something in v.383 changed or did you very recently move this to a VM or made a change to the VM?
    I can check tonight but I'm pretty sure the PI at start-up asks HS3 what the IP address is and uses that.

    I do start a listener by default on the loop back interface 127.0.0.1 but there should be a second listener which in this case should be 192.168.1.154 or 198.168.249.97 but your log didn't show it. Is the debug flag still on? If not keep it on for now.

    Just for my understanding, HS3 is running in a VM and that VM has IP address 249.97/28 or you have some VMs running on this instance of Windows but HS is running native? I'm also surprised that you have the VM running on a different subnet, do you route between the subnets? Care to share why you do that?

    Dirk

    Comment


      #17
      Originally posted by Tomgru View Post
      crazy... tried that, now i see this in logs: (notice the 127 subnet now)
      127.0.0.1 is the address for localhost. It is the IP all plug-ins connect to when they are on the same machine as HomeSeer.

      Mine has continued announcements without fail through 3.0.0.379-387, so I doubt it is the HS beta. It seems like the speakers are not reachable. When you use an iOS or Android app, do all the speakers show up? If they connect through the app, what IP addresses are shown on the About page under settings? Are the speakers on the same subnet as HomeSeer?

      A diagnostic tool we used at a friends house was installing the Sonos Windows controller on the HS server. He was unable to see the speakers with the controller. It turned out to be a firewall issue in his case, but it might help you to know if the speakers are reachable from the HS server.
      HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

      Comment


        #18
        Originally posted by bartbakels View Post
        Just for info, im running 387 beta and my sonos tts still works

        Regards
        Bart
        Hi Bart, but you are not running it in a VM with some second subnet associated to it

        Comment


          #19
          Originally posted by dcorsus View Post
          Hi Bart, but you are not running it in a VM with some second subnet associated to it


          True, not anymore haha

          Regards


          Verzonden vanaf mijn iPhone met Tapatalk
          Regards Bart
          ------------------------------------------
          Win7 64Bit on Intel NUCI7 with SSD
          HSPRO 3.
          Devices; 1370 Events; 691

          Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

          Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

          Comment


            #20
            Originally posted by dcorsus View Post
            There should be a second line like this one
            -> Nov-21 11:42:07 AM Info Plugin Sonos has connected. IP:127.0.0.1:63420

            Not sure why it is not working but now I'm starting to suspect that perhaps something in v.383 changed or did you very recently move this to a VM or made a change to the VM?
            I can check tonight but I'm pretty sure the PI at start-up asks HS3 what the IP address is and uses that.

            I do start a listener by default on the loop back interface 127.0.0.1 but there should be a second listener which in this case should be 192.168.1.154 or 198.168.249.97 but your log didn't show it. Is the debug flag still on? If not keep it on for now.

            Just for my understanding, HS3 is running in a VM and that VM has IP address 249.97/28 or you have some VMs running on this instance of Windows but HS is running native? I'm also surprised that you have the VM running on a different subnet, do you route between the subnets? Care to share why you do that?

            Dirk
            Hey all... see my post here just now, although maybe i should have just kept it all to this one.

            no idea why the two subnets.

            https://forums.homeseer.com/showthread.php?t=192146

            Comment


              #21
              Originally posted by rprade View Post
              127.0.0.1 is the address for localhost. It is the IP all plug-ins connect to when they are on the same machine as HomeSeer.

              Mine has continued announcements without fail through 3.0.0.379-387, so I doubt it is the HS beta. It seems like the speakers are not reachable. When you use an iOS or Android app, do all the speakers show up? If they connect through the app, what IP addresses are shown on the About page under settings? Are the speakers on the same subnet as HomeSeer?

              A diagnostic tool we used at a friends house was installing the Sonos Windows controller on the HS server. He was unable to see the speakers with the controller. It turned out to be a firewall issue in his case, but it might help you to know if the speakers are reachable from the HS server.
              smart... will do that. HS is on the host machine.

              funny... see this during install.

              It installed fine on the HS3 server (it did say it needed to make a firewall change). in the about box, all speakers show up with IPs 192.168.1.xxx

              Still no joy on the Sonos PI. Do I need to recreate the .ini again?
              Attached Files

              Comment


                #22
                just tried disable/enable again on plugin with debugging turned on. it's clearly looking at the wrong IP (I think).

                Nov-21 1:36:56 PM
                *
                Sonos
                SetDeviceStringConnected called
                Nov-21 1:36:56 PM
                *
                Sonos
                InitializeSonosDevices: Done Initializing Sonos Devices
                Nov-21 1:36:56 PM
                *
                Sonos
                CreateSonosControllers called but no devices found
                Nov-21 1:36:56 PM
                *
                Sonos
                FindZonePlayers - Discovery succeeded: 0 ZonePlayer(s) found.
                Nov-21 1:36:56 PM
                *
                Sonos
                FindZonePlayers - Discovery succeeded: 0 ZonePlayer(s) found.
                Nov-21 1:36:29 PM
                *
                Z-Wave
                Device: Light Entryway Power Set to 5.8 (W)
                Nov-21 1:36:17 PM
                *
                Sonos
                FindZonePlayers: Attempting to locate all connected ZonePlayers. This may take up to 9 seconds.
                Nov-21 1:36:17 PM
                *
                Sonos
                MyTcpListener.Start successfully opened TCP Listening Port with HostAddress = 192.168.249.97 and HostIPPort = 53561
                Nov-21 1:36:17 PM
                *
                Sonos
                MyTcpListener.Start called with HostAddress = 192.168.249.97
                Nov-21 1:36:17 PM
                *
                Sonos
                InitializeSonosDevices found MasterHSDeviceRef in the inifile. MasterHSDeviceRef = 823
                Nov-21 1:36:17 PM
                *
                Sonos
                Initializing Sonos Devices
                Nov-21 1:36:16 PM
                *
                Plug-In
                Finished initializing plug-in Sonos
                Nov-21 1:36:16 PM
                *
                Sonos
                Sonos Plugin Initialized
                Nov-21 1:36:16 PM
                *
                Sonos
                DeleteIniSection called with section = TTSSpeakDevice and FileName = Sonos.ini
                Nov-21 1:36:15 PM
                *
                Sonos
                INIT: MaxNbrOfUPNPObjects set to 400
                Nov-21 1:36:15 PM
                *
                Sonos
                ReadIniFile called
                Nov-21 1:36:15 PM
                *
                Sonos
                InitIO Called for Instance =
                Nov-21 1:36:15 PM
                *
                Sonos
                InitIO for Instance = found this plugin running on Linux = False
                Nov-21 1:36:15 PM
                *
                Sonos
                InitIO Called for Instance = and running on OS = Win32NT
                Nov-21 1:36:15 PM
                *
                Sonos
                InitIO for Instance = found HS running on Linux = False
                Nov-21 1:36:15 PM
                *
                Sonos
                InitIO for Instance = found CurrentAppPath = C:\Program Files (x86)\HomeSeer HS3
                Nov-21 1:36:15 PM
                *
                Info
                Plugin Sonos has connected. IP:127.0.0.1:53556

                Comment


                  #23
                  Originally posted by Tomgru View Post
                  just tried disable/enable again on plugin with debugging turned on. it's clearly looking at the wrong IP (I think).

                  Nov-21 1:36:56 PM
                  *
                  Sonos
                  SetDeviceStringConnected called
                  Nov-21 1:36:56 PM
                  *
                  Sonos
                  InitializeSonosDevices: Done Initializing Sonos Devices
                  Nov-21 1:36:56 PM
                  *
                  Sonos
                  CreateSonosControllers called but no devices found
                  Nov-21 1:36:56 PM
                  *
                  Sonos
                  FindZonePlayers - Discovery succeeded: 0 ZonePlayer(s) found.
                  Nov-21 1:36:56 PM
                  *
                  Sonos
                  FindZonePlayers - Discovery succeeded: 0 ZonePlayer(s) found.
                  Nov-21 1:36:29 PM
                  *
                  Z-Wave
                  Device: Light Entryway Power Set to 5.8 (W)
                  Nov-21 1:36:17 PM
                  *
                  Sonos
                  FindZonePlayers: Attempting to locate all connected ZonePlayers. This may take up to 9 seconds.
                  Nov-21 1:36:17 PM
                  *
                  Sonos
                  MyTcpListener.Start successfully opened TCP Listening Port with HostAddress = 192.168.249.97 and HostIPPort = 53561
                  Nov-21 1:36:17 PM
                  *
                  Sonos
                  MyTcpListener.Start called with HostAddress = 192.168.249.97
                  Nov-21 1:36:17 PM
                  *
                  Sonos
                  InitializeSonosDevices found MasterHSDeviceRef in the inifile. MasterHSDeviceRef = 823
                  Nov-21 1:36:17 PM
                  *
                  Sonos
                  Initializing Sonos Devices
                  Nov-21 1:36:16 PM
                  *
                  Plug-In
                  Finished initializing plug-in Sonos
                  Nov-21 1:36:16 PM
                  *
                  Sonos
                  Sonos Plugin Initialized
                  Nov-21 1:36:16 PM
                  *
                  Sonos
                  DeleteIniSection called with section = TTSSpeakDevice and FileName = Sonos.ini
                  Nov-21 1:36:15 PM
                  *
                  Sonos
                  INIT: MaxNbrOfUPNPObjects set to 400
                  Nov-21 1:36:15 PM
                  *
                  Sonos
                  ReadIniFile called
                  Nov-21 1:36:15 PM
                  *
                  Sonos
                  InitIO Called for Instance =
                  Nov-21 1:36:15 PM
                  *
                  Sonos
                  InitIO for Instance = found this plugin running on Linux = False
                  Nov-21 1:36:15 PM
                  *
                  Sonos
                  InitIO Called for Instance = and running on OS = Win32NT
                  Nov-21 1:36:15 PM
                  *
                  Sonos
                  InitIO for Instance = found HS running on Linux = False
                  Nov-21 1:36:15 PM
                  *
                  Sonos
                  InitIO for Instance = found CurrentAppPath = C:\Program Files (x86)\HomeSeer HS3
                  Nov-21 1:36:15 PM
                  *
                  Info
                  Plugin Sonos has connected. IP:127.0.0.1:53556
                  I'll look at my code tonight. The above trace is taken with the HS3 setting how? No binding or specifically bound? When I said restart PI, I assume you restarted HS3 as well after you changed it to use 192.168.1.154, right?

                  Dirk

                  Comment


                    #24
                    Hey Dirk...

                    Randy and I just walked through my VM settings... Seems that with the Fall Creator's update, something seemed to change with regards to my virtual switches, creating that weird additional IP/subnet.

                    He's doing some investigating, but in the meantime, we were able to disable that Virtual switch, and Sonos was back up and running immediately, including announcements.

                    No idea yet what is/was going on, so will report back when we know more.

                    Much thanks to you both (and others that have weighed in) on helping to figure this out.

                    Comment


                      #25
                      Originally posted by Tomgru View Post
                      we were able to disable that Virtual switch, and Sonos was back up and running immediately, including announcements.
                      Excellent!

                      Comment

                      Working...
                      X