Announcement

Collapse
No announcement yet.

No audio to speaker clients

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

    No audio to speaker clients

    Am switching from HS2Pro to HS3Pro SEL. None of the HSTouch speaker clients on the network, including Windows and Android platforms produce any output although no errors show in the log. These devices all work both with HS2Pro and HS3Pro on Windows. I put in a Helpdesk ticket but we're both still puzzled as to why this is happening. Anyone else notice this?

    KV
    Current Date/Time: 12/23/2015 4:23:24 PM
    HomeSeer Version: HS3 Pro Edition 3.0.0.208
    Linux version: Linux hometrollerSEL 3.16.0-031600-generic #201408031935 SMP Sun Aug 3 23:56:17 UTC 2014 i686 i686 i686 GNU/Linux System Uptime: 0 Days 1 Hour 43 Minutes 26 Seconds
    IP Address: 192.168.1.130
    Number of Devices: 167
    Number of Events: 28

    Enabled Plug-Ins
    3.0.0.68: HSTouch Server
    3.0.5723.28727: UltraWeatherWU3
    3.0.1.25: Z-Wave
    Last edited by KirkVistain; December 23, 2015, 09:00 PM.

    #2
    Are you using Text to Speech or just playing a wav file?

    a quick Wav file test is to create an event that plays a sound. Upload a .wav file and see if that works?
    HS4Pro on a Raspberry Pi4
    54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
    Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

    HSTouch Clients: 1 Android

    Comment


      #3
      Wav files don't play either

      Thanks for the tip. I checked that and wav files don't play either. The thing is that the HS3Pro log doesn't indicate any error. It thinks it sent the info. Smells like a bug in the HSTouch plugin.

      Kirk

      Comment


        #4
        where is the wave file in the hstouch client filesystem

        Carrying on with trying to get the HSTouch3 clients to talk when commanded by the Hometroller SEL: Does anyone know where the tts wave file sent by the HSTouch3 server ends up in a default windows hstouch3 client installation?

        Thanks,

        Comment


          #5
          Originally posted by KirkVistain View Post
          Carrying on with trying to get the HSTouch3 clients to talk when commanded by the Hometroller SEL: Does anyone know where the tts wave file sent by the HSTouch3 server ends up in a default windows hstouch3 client installation?

          Thanks,
          Windows installs use the speaker app installed on the Windows PC.
          💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

          Comment


            #6
            The wave_files folder is where the TTS ends up, but I dont think that's the problem.

            Can you SSH to your HomeTroller and see if flite is working? Just type flite --help and see if you get a response...


            Code:
            login as: homeseer
            homeseer@192.168.0.xxx's password:
            Linux RPi2 3.18.5-v7+ #225 SMP PREEMPT Fri Jan 30 18:53:55 GMT 2015 armv7l
            
            The programs included with the Debian GNU/Linux system are free software;
            the exact distribution terms for each program are described in the
            individual files in /usr/share/doc/*/copyright.
            
            Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
            permitted by applicable law.
            Last login: Thu Dec 31 15:30:58 2015 from 192.168.0.xxx
            homeseer@RPi2 ~ $
            homeseer@RPi2 ~ $ flite --help
            flite: a small simple speech synthesizer
              Carnegie Mellon University, Copyright (c) 1999-2009, all rights reserved
              version: flite-1.4-release December 2009 (http://cmuflite.org)
            usage: flite TEXT/FILE [WAVEFILE]
              Converts text in TEXTFILE to a waveform in WAVEFILE
              If text contains a space the it is treated as a literal
              textstring and spoken, and not as a file name
              if WAVEFILE is unspecified or "play" the result is
              played on the current systems audio device.  If WAVEFILE
              is "none" the waveform is discarded (good for benchmarking)
              Other options must appear before these options
              --version   Output flite version number
              --help      Output usage string
              -o WAVEFILE Explicitly set output filename
              -f TEXTFILE Explicitly set input filename
              -t TEXT     Explicitly set input textstring
              -p PHONES   Explicitly set input textstring and synthesize as phones
              --set F=V   Set feature (guesses type)
              -s F=V      Set feature (guesses type)
              --seti F=V  Set int feature
              --setf F=V  Set float feature
              --sets F=V  Set string feature
              -ssml       Read input text/file in ssml mode
              -b          Benchmark mode
              -l          Loop endlessly
              -voice NAME Use voice NAME
              -lv         List voices available
              -add_lex FILENAME add lex addenda from FILENAME
              -pw         Print words
              -ps         Print segments
              -pr RelName  Print relation RelName
              -v          Verbose mode
            HS4Pro on a Raspberry Pi4
            54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
            Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

            HSTouch Clients: 1 Android

            Comment


              #7
              New developments: windows spkr client works

              Thanks for the help, guys. I was able to get a windows speaker client to work with the SEL. Still, the android HSTouch clients don't talk, but at least I know that the Hometroller SEL installation is talking on port 10400. It had been set for port 5782. I don't know why.

              Now my speaker clients are reported as:
              Speaker HOMETROLLERSEL (192.168.1.130) : ANDROID
              Speaker HOMETROLLERSEL (192.168.1.130) : LRDROID
              Speaker HOMETROLLERSEL (192.168.1.130) : ICSZILLA
              Speaker HOMETROLLERSEL (192.168.1.130) : LAZYDROID3
              Speaker HEXZILLA (192.168.1.113) : DEFAULT

              This puzzles me a little, since all the android speakers show the hometroller SEL address while the speaker client that actually works shows the address of the client NOT the server.
              I'll keep plugging away.
              Thanks again for the help,
              Kirk

              Comment


                #8
                PROBLEM SOLVED - installed flite on Hometroller SEL

                Thanks, rmasonjr. Installing flite fixed the problem.
                Kirk

                Comment

                Working...
                X