Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Question

Posted

Hay has anyone any idea why the text to speak is no longer working - about 8 weeks ago it needed an adjustment in the LUA code but again it has stopped?

Recommended Posts

  • 0
Posted

I also tested google translator directly from a http connection without involving Sonos to discard Google malfunction and I got not errors.

You may get the "excesive use from your IP" message if the http request is invalid.

 

Try this on your browser:

 

Please login or register to see this link.

 

or

 

Please login or register to see this link.

 

and see if you get it through.

 

I can get through (no errors), still having the same issue playing TTS commands.... 

  • 0
Posted

That confirms my fears. Google is not the problem. Most likely the problem is that the new Sonos 5.5 release has implemented some changes in the API and our virtual device must be updated accordingly in order to build the streams in the way the new API expects.

So, we need the VD architect here... Krikroff, do you feel like having a quick glance to the new Sonos release?

  • 0
Posted

actually google is the problem.

I think they limited it to 2 or 3 requests a day.

At least for me after 2 or 3 requests with a browser the site basicly disappears (404 error)

Doesn't matter if your request is valid or invalid

  • 0
Posted

Which browser are you using?

If you try to pass a stream request to Google Translator using UTF-8 (my second example) over MS Internet Explorer 11 you will be rejected to the well known blocking page. With this browser you must use Non UTF-8 code (my first example)

If you use Google Chrome or last version of Mozilla Firefox, both ways should work... for an unlimited number of times.

  • 0
Posted

If you use Google Chrome or last version of Mozilla Firefox, both ways should work... for an unlimited number of times.

Confirmed, works unlimited times in Chrome for me.

  • 0
  • Inquirer
  • Posted

    Our systems have detected unusual traffic from your computer network. Please try your request again later

    This was using  chrome 

    Please login or register to see this link.

    • 0
  • Inquirer
  • Posted

    The captcha message displayed when the 

    Please login or register to see this link.

     was used (after 5 attempts) 

    • 0
    Posted

    Our systems have detected unusual traffic from your computer network. Please try your request again later

    This was using  chrome 

    Please login or register to see this link.

     

    i get this aswell.

    when i try and click on the link using my mobile data signal it works all the time.

    this suggests that it is a google issue registering requests from the same IP

    • 0
    Posted

    Well, meanwhile someone finds the way to adapt the scene to Sonos 5.5 release, or Sonos releases a new version that performs like the old one, I have found a way to overcome the problem, changing only three lines of code. I have tested it for 48h and it is working fine.

    The idea is as follows:

    Since, like I posted somewhere above in this thread, when TTS stops working, if you remove the "ie=UTF-8" character set definition in the Sonos.PlayTTS function of the Virtual Device (main loop), the TTS starts working again... until something else (internet radio or locally stored files) is played through Sonos. Then it fails to play TTS again, until you replace back "ie=UTF-8".

    Unfortunately, I have not found a simple way to verify automatically if the message actually plays or not. Therefore, what I have done is a small modification in the code that sends both requests to the API: one with the standard charset, and a second one with the UTF-8.

    Since only one of those will work at a time, Sonos will not repeat the message.

    The only drawback I have seen so far is that the messages take a little longer to pass through, and there may be one or two more interruptions in the music than expected but… it works.

    For those who are also struggling with the stream examples I posted before, this workaround may not work. It seems that these users have also some networking issue.

     

    These are the modifications to be done in the virtual device’s main loop script:

     

    In Sonos.PlayTTS function:

     

    Change line:

    Please login or register to see this code.

    with line:

    Please login or register to see this code.

    A few lines below those, change line:

    Please login or register to see this code.

    with line:

    Please login or register to see this code.

    In Sonos.process function:

    Under line:

    Please login or register to see this code.

    Add line (both lines must exist):

    Please login or register to see this code.

    That's it. Welcome back Sonos TTs. I hope it works for you.

    Although I hate the only Spanish voice available at Google, it is good to have the announcements back 

    Please login or register to see this image.

    /emoticons/default_icon_smile.gif" alt=":-)" /> 

    • 0
    Posted

    Hello Brik, This workarround looks great. unfortunately my LUA code in thee VD looks different ;-(

    • 0
    Posted

    I know there are several flavours of Krikoff's VD but I thought that lua basics were similar in all of them. Are you using on of those or do you have a complete different solution developed  by someone else?

    • 0
    Posted

    Tested and works perfectly! Thanks!

    • 0
    Posted

    Is your solution still working?

    • 0
    Posted

    To be honest, I don't know. I found out several weeks ago that Krikoff updated his VD using an alternative TTS engine, different to Google Translator and I switched my scenes to that solution.

    It can be found here (registration needed): 

    Please login or register to see this link.

    • 0
    Posted

    See

    Please login or register to see this link.

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Answer this question...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...