Announcement

Collapse
No announcement yet.

HS3 Speaker only Client?

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

  • #31
    I am running two speaker clients today on one VM (Mini version Windows Server) talking to two HS3 boxes running in Linux Ubuntu 64bit with HS3 Pro running on it.

    Also running speaker dot exe on W7e, W10 and XPe Homeseer touch clients with no issues.

    Tested speaker client on W10 Home and enterprise edition to work fine. W10 enterprise build was tweaked a bit.

    Personally a while ago just copied the HS3 directory over and run speaker dot exe. I then deleted all of the files not needed but today do not recall which of those files have been deleted. Today you can just download speaker dot exe from the download section. Didn't touch the firewall stuff in W2003.

    What do you see in the speaker client log window when starting speaker dot exe in Windows 10?
    Attached Files
    Last edited by Pete; August 26th, 2016, 06:59 AM.
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
    Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

    Comment


    • #32
      Originally posted by amr42 View Post
      Speaker client is running fine, and all files listed in this post are local to client. On Windows 10 Home Edition.

      I have config file set with HS server IP address, port number.

      Port is open thru firewall on HS server for speaker client (10401)

      What am I missing?
      Making some assumptions, your speaker client you are having issues with is running on a MS windows based device. If so, please do the following on the windows device. I recommend initial test within your local network, i.e. same subnet. Then try external.

      1. Open a command (dos) prompt via Windows Key + R, enter cmd in the open field. A black window should open.

      2. run the following command to confirm the windows device can communicate to your HS server on port 10401.
      telnet hs.ip 10401 and depress the enter key

      You should see the following and the telnet client should hang - which is good.
      Code:
      len@dell:~$ telnet serv1 10401
      Trying 192.168.1.36...
      Connected to serv1.
      Escape character is '^]'.
      If you do not get "Connected to serv1. Escape character is '^]'." then something is blocking network connectivity.

      If you do get "Connected to serv1. Escape character is '^]'." then from a network viewpoint, all is well. You exit this telnet session by pressing control+], then 'quit' after you get the telnet prompt.

      Comment


      • #33
        The Windows Media Player is required by the speaker client. Did you load the add on to your server that includes this option?
        -Rupp
        sigpic

        Comment


        • #34
          Originally posted by Pete View Post
          I am running two speaker clients today on one VM (Mini version Windows Server) talking to two HS3 boxes running in Linux Ubuntu 64bit with HS3 Pro running on it.

          Also running speaker dot exe on W7e, W10 and XPe Homeseer touch clients with no issues.

          Tested speaker client on W10 Home and enterprise edition to work fine. W10 enterprise build was tweaked a bit.

          Personally a while ago just copied the HS3 directory over and run speaker dot exe. I then deleted all of the files not needed but today do not recall which of those files have been deleted. Today you can just download speaker dot exe from the download section. Didn't touch the firewall stuff in W2003.

          What do you see in the speaker client log window when starting speaker dot exe in Windows 10?
          Same window (Speaker.EXE is running), just cannot connect to server.


          "8/25/2016 10:36:18 AM:Error attempting to connect to server, please check your connection options:
          The host failed to connect. Timeout occured. 15000" every 30 seconds

          Comment


          • #35
            Originally posted by lveatch View Post
            Making some assumptions, your speaker client you are having issues with is running on a MS windows based device. If so, please do the following on the windows device. I recommend initial test within your local network, i.e. same subnet. Then try external.

            1. Open a command (dos) prompt via Windows Key + R, enter cmd in the open field. A black window should open.

            2. run the following command to confirm the windows device can communicate to your HS server on port 10401.
            telnet hs.ip 10401 and depress the enter key

            You should see the following and the telnet client should hang - which is good.
            Code:
            len@dell:~$ telnet serv1 10401
            Trying 192.168.1.36...
            Connected to serv1.
            Escape character is '^]'.
            If you do not get "Connected to serv1. Escape character is '^]'." then something is blocking network connectivity.

            If you do get "Connected to serv1. Escape character is '^]'." then from a network viewpoint, all is well. You exit this telnet session by pressing control+], then 'quit' after you get the telnet prompt.
            OK, using putty I confirm I CANNOT telnet to 192.168.1.210:10401 (this is IP:Port of HS3 server).

            Win Media Player on Server? Speaker Client works just fine on server...

            Comment


            • #36
              Win Media Player on Server?

              Yes here on the Homeseer embedded, W7E and W10 clients.

              Initially though when first testing it was just missing files and would exit on start.

              That you get it running but not connecting still appears to be a network / firewall type of issue. Disable the firewall on both sides and try again.
              - Pete

              Auto mator
              Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
              Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

              Comment


              • #37
                Originally posted by amr42 View Post
                OK, using putty I confirm I CANNOT telnet to 192.168.1.210:10401 (this is IP:Port of HS3 server).
                Same telnet command via putty works from the server to the server?

                Comment


                • #38
                  Duh! Found it...

                  I had the Connect local box checked (since the files came from the server)...

                  Now Connected!

                  Thanks to all!

                  Comment


                  • #39
                    I am having an issue where i can only run 6 instances of speaker.exe at a time. at one point i saw a forum post that said that its caused by having an older version of the speaker client, but i have the newest one that comes with homeseer. Has anyone else had this issue and know how to fix it?

                    Comment

                    Working...
                    X