Announcement

Collapse
No announcement yet.

TTS to Sonos stuck on one phrase

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

  • TTS to Sonos stuck on one phrase

    Hi, I have a quick question about something that has happened to me for second time in three weeks.

    I am trying to take it slowly with setting up everything just so it is easier to troubleshoot things. That said I had setup 4 events with "Speak Something" at the end to have confirmation that things are happening.

    First two are just announcements when door is locked or unlocked.
    Another 2 are announcements that thermostats were set to certain temperature at certain time.

    When I was setting these events up I noticed that at some point TTS to my SONOS was stuck on phrase "Front door unlocked" which was phrase from second event. It would not matter if I tried to change text or create new event. No matter what text I have entered in text to be spoken field it would repeat same phrase when testing the event.

    I tried to restart Homeseer with no luck.
    After all frustration I went to HomeSeer HS3\html\Sonos\Announcements folder and deleted Ann_Test_0.wav file as I thought it was just temp file. Later I restored the file as I would not hear anything. After messing with it for s while (restarts, playing with new events etc.) it started to work again. Not sure what did the trick.

    Now, three weeks later without doing any changes the same problem is back and all four actions say same phrase "Front door unlocked" and so does file in Announcments directory.

    Is that a bug? How do I fix it? I am using 3.1.0.16 Sonos plugin.
    Not sure if that is SONOS plugin issue or something else.

    Restart doesn't help.. Any suggestions?

    Thank you. Charles

  • #2
    Originally posted by Charles_cz View Post
    Hi, I have a quick question about something that has happened to me for second time in three weeks.

    I am trying to take it slowly with setting up everything just so it is easier to troubleshoot things. That said I had setup 4 events with "Speak Something" at the end to have confirmation that things are happening.

    First two are just announcements when door is locked or unlocked.
    Another 2 are announcements that thermostats were set to certain temperature at certain time.

    When I was setting these events up I noticed that at some point TTS to my SONOS was stuck on phrase "Front door unlocked" which was phrase from second event. It would not matter if I tried to change text or create new event. No matter what text I have entered in text to be spoken field it would repeat same phrase when testing the event.

    I tried to restart Homeseer with no luck.
    After all frustration I went to HomeSeer HS3\html\Sonos\Announcements folder and deleted Ann_Test_0.wav file as I thought it was just temp file. Later I restored the file as I would not hear anything. After messing with it for s while (restarts, playing with new events etc.) it started to work again. Not sure what did the trick.

    Now, three weeks later without doing any changes the same problem is back and all four actions say same phrase "Front door unlocked" and so does file in Announcments directory.

    Is that a bug? How do I fix it? I am using 3.1.0.16 Sonos plugin.
    Not sure if that is SONOS plugin issue or something else.

    Restart doesn't help.. Any suggestions?

    Thank you. Charles
    All seems to point to the "Text-to-Speech" function not working. The fact you always heard the same is because it is not being overwritten and when you delete it, you hear nothing so no file is being created.

    Up to very recently, I was under the impression that the speaker client on the HS PC was responsible for this (HS!!) function. Somebody pointed out that wasn't correct and that it might be the Windows text-to-speech function that is being called directly by HS. So check the windows text-to-speech settings, see if there is anything out of the ordinary there. Are you using a special voice for example?

    Could you also post a screen shot of your event to make sure the event was created properly.

    Dirk

    Comment


    • #3
      Hi Dirk, it has been working just fine for 2-3 weeks with correct TTS announcements for each event. Suddenly it started to say same thing on each event without any change to events or any other configuration.

      I have attached screenshot from event.

      To answer your question, no, I am not using anything special about TTS. I did not make any changes to TTS.
      Attached Files

      Comment


      • #4
        OK.. I think I figured out where the problem. I am using built-in task scheduler to start HS and it looks like it bypasses UAC or it doesn't give proper access control to overwrite the file. If I start HS manually it prompts me to UAC dialog and after HS starts everything works just fine.

        I guess I will have to find some software that will allow me to start HS automatically in windows 10 with proper write/read privileges.

        What is everyone using?

        Comment


        • #5
          I recently ran across this same issue - TTS not over writing previous announcements sent to the same speaker client. Driving me crazy until I read your posts. I am using Jon00 Restart and when HS3 has been started using that PI, the announcements don't work properly at all. I can't even create a new speaker client. I'll have to see how I can work around that issue. I have tested SONOS extensively using manual start and all announcements function properly. Incidentally, when I say manual start, I'm referring to a shortcut that starts HS3 in the HS3 directory. No worries about UAC. I also start HS3automatically without delay with a small bat file in the startup directory. If you don't need any delay, that works fine and will allow SONOS to work fine also.

          UPDATE: I was able to modify the HS3 startup bat file with a time delay, so the 'restart PI bat file isn't need. I fully tested SONOS TTS and all is working properly.
          Last edited by field888; October 26th, 2016, 11:45 AM.

          Comment


          • #6
            Originally posted by field888 View Post
            I am using Jon00 Restart and when HS3 has been started using that PI, the announcements don't work properly at all. I can't even create a new speaker client.
            FYI, That may be because you were not running the exe or shortcut as an administrator.
            Jon

            Comment


            • #7
              Kudos to Jon00 for the quick reply to this thread! I have to apologize to you, I changed the PI to CFguy's 'Restart' so this issue has nothing to do with your PI - sorry bout that.

              Comment


              • #8
                Originally posted by field888 View Post
                I recently ran across this same issue - TTS not over writing previous announcements sent to the same speaker client. Driving me crazy until I read your posts. I am using Jon00 Restart and when HS3 has been started using that PI, the announcements don't work properly at all. I can't even create a new speaker client. I'll have to see how I can work around that issue. I have tested SONOS extensively using manual start and all announcements function properly. Incidentally, when I say manual start, I'm referring to a shortcut that starts HS3 in the HS3 directory. No worries about UAC. I also start HS3automatically without delay with a small bat file in the startup directory. If you don't need any delay, that works fine and will allow SONOS to work fine also.

                UPDATE: I was able to modify the HS3 startup bat file with a time delay, so the 'restart PI bat file isn't need. I fully tested SONOS TTS and all is working properly.
                How you make the file?

                Comment


                • #9
                  Originally posted by Charles_cz View Post
                  OK.. I think I figured out where the problem. I am using built-in task scheduler to start HS and it looks like it bypasses UAC or it doesn't give proper access control to overwrite the file. If I start HS manually it prompts me to UAC dialog and after HS starts everything works just fine.

                  I guess I will have to find some software that will allow me to start HS automatically in windows 10 with proper write/read privileges.

                  What is everyone using?

                  This thread helped me debug my issue. Started moving to HS3 after years of procrastination :-)

                  You CAN use task scheduler to automatically start HS but you MUST setup directory in which HS3 is started (Start In (Optional) box): - it must be this, NO quotes and have to include final backslash: C:\Program Files (x86)\HomeSeer HS3\

                  Now Sonos TTS is working fine as it can overwrite the files.

                  This is clearly described in HS YouTube video - https://www.youtube.com/watch?v=n6mmLKPrmXU - what is confusing is that even without Start-in directory defined, HS3 worked fine for me including z-wave and vista alarm system plugins, even Sonos for music control. What did not work is Sonos TTS.

                  Comment

                  Working...
                  X