The Vera Community forums have moved!

Advanced => Plugins & Plugin Development => Programming => Sonos Plugin => Topic started by: lemrock on July 27, 2015, 08:37:13 pm

Title: [FIXED] Google TTS engine is no more working
Post by: lemrock on July 27, 2015, 08:37:13 pm
There was a software update for Sonos today and now the "Say" function does not work anymore. I get an error on the Sonos that says : Unable to play "Say.***.mp3"- file is encoded incorrectly". I have been sending the same command string and it has worked flawlessly:
   
luup.call_action(LS_SID, "Say", {Text=" ", Language="en", GroupZones="ALL",Volume=75, SameVolumeForAll="true"},SONOS). 

I even sent a txt string from the Sonos Plugin Device tab "TTS" and I get the same error.  Is there a cure for what ails my Sonos?
Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: lolodomo on July 28, 2015, 01:45:23 am
It is not working for me too this morning.
As it was working well the previous days, it has no link to a Sonos update even if an update was released by Sonos few days ago.
I hope Google has not closed its TTS service !!!
Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: MNB on July 28, 2015, 10:41:00 am
Ditto here.. I tried to do a simple TTS say with no speakee.. last night. How do we know if Google closed their TTS service and if so what is the alternate? Mike

It is not working for me too this morning.
As it was working well the previous days, it has no link to a Sonos update even if an update was released by Sonos few days ago.
I hope Google has not closed its TTS service !!!
Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: tomgru on July 28, 2015, 10:42:20 am
Ditto. Glad I saw this thread before I spent hours debugging:  :)
Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: SteveZ on July 28, 2015, 12:03:52 pm
Same here, I'm going to try to install osx in a virtual machine and use the osx tts server. I have a windows maching running all the time anyway for blue iris and plex anyway. I'll report back if I have any success.
Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: birchey on July 28, 2015, 12:38:09 pm
Its interesting as mine has stopped working as well on the Play 1's after update. I have also noticed that all the tts to mp3 sites are not working, could this be a Google issue? In The Sonos app i can see that it groups the zones ok and attempts to play with a "the track i not encoded correctly"



Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: lolodomo on July 28, 2015, 01:39:29 pm
We must test the Google URL first.
Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: RHINESEL on July 28, 2015, 03:08:32 pm
I did the update via the iOS app days ago and TTS worked.  I don't think it's related to the update but just a coincidence.
Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: lemrock on July 28, 2015, 03:42:05 pm
Anyone knows how to get a local OSX TTS server up and running?
Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: RHINESEL on July 28, 2015, 04:42:22 pm
I'll test tomorrow on a Playbar.  If it's the Play:1 update then it should play fine.  If it doesn't play we'll know it's another issue.
Title: Re: Say command isn't working after Sonos Play:1 software Update
Post by: lolodomo on July 28, 2015, 05:11:51 pm
I tried this URL as an example: http://translate.google.com/translate_tts?tl=fr&q=Test

And the result is that we have now to enter a Captcha code !!!!!!!!!!!!!!!!!!
So the service is not closed but is protected against robot !!!!!!
Title: Re: Google TTS is no more usable with the plugin !
Post by: lolodomo on July 28, 2015, 05:13:50 pm
I just renamed the topic !
That's really a big problem !
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on July 28, 2015, 05:25:03 pm
https://support.google.com/websearch/answer/86640?hl=en
Title: Re: Google TTS is no more usable with the plugin !
Post by: MNB on July 28, 2015, 08:12:26 pm
Oook, so is there a recovery schema to Google's change and/or is there an alternate solution? I take it we fall into the "Automated service" category? Mike

I just renamed the topic !
That's really a big problem !
Title: Re: Google TTS is now protected against robot and automation systems
Post by: watek2k on July 28, 2015, 09:27:21 pm
Same darn problem!!!
Title: Re: Google TTS is now protected against robot and automation systems
Post by: steets250 on July 28, 2015, 09:30:25 pm
For me it looks like entering the captcha is unblocking the TTS for my IP for multiple searches. Is that not the same for others?
Title: Re: Google TTS is now protected against robot and automation systems
Post by: watek2k on July 28, 2015, 10:10:46 pm
Seems to have only worked on my computer!!!!

http://api.microsofttranslator.com/V2/Http.svc/Speak?appId=SIGNUP_TO_GET_FREE&text=We%20Should%20Ditch%20Google%20TTS&language=en

Johnny
Title: Re: Google TTS is now protected against robot and automation systems
Post by: korttoma on July 29, 2015, 07:08:41 am
Seems like ivona is launching some kind of online TTS service maybe this can be an alternative?
I bet it will come with a prize tag though...

http://www.ivona.com/
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on July 29, 2015, 10:14:58 am
Seems to have only worked on my computer!!!!

http://api.microsofttranslator.com/V2/Http.svc/Speak?appId=SIGNUP_TO_GET_FREE&text=We%20Should%20Ditch%20Google%20TTS&language=en

Johnny

Microsoft Translator could be a free alternative to investigate.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on July 29, 2015, 02:11:44 pm
I read about Microsoft  Translator API this afternoon and I am now convinced that adding this TTS engine is doable.
For the user, that would be more difficult to setup because an account has to be created on a particular platform and a new application has to be declared by the user to get the identifiers that will be required by the plugin.
For the plugin itself,  the new thing is that a session token has to be obtained and renewed when necessary.

So I will add this new engine to the plugin. Should be available in few days.

Any idea if the Microsoft speech is as good as Google speech ?

Note that the account is free if you translate less than 20 000 characters per month. That's largely enough for few TTS messages per day.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: RichardTSchaefer on July 29, 2015, 02:31:58 pm
Or go back to Vera Alerts for Android (Or you can probably do something from Tasker) for free TTS on the Android device that works without a Internet connection.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: kazenami on July 29, 2015, 04:32:27 pm
Thanks to this, I've installed MaryTTS (http://mary.dfki.de/) on my Raspberry PI (that was only running the Hue Server for the Amazon ECHO Workaround). This is for those that don't have a 24/7 Mac server running. Hopefully it helps :D

Here's what I did (Full Steps).

1. SSH into Raspberry PI

$ cd Downloads
$ wget https://github.com/marytts/marytts/releases/download/v5.1/marytts-5.1.zip
Unzip the application to the /usr/bin directory

$ sudo unzip marytts-5.1.zip -d /opt
At this point it will not run unless the you have already installed Java 1.7 you can determine the current version of Java by executing:

$ java -version
Install the required version of Java (also add openjdk-7-jdk if you intend to do any java development):

$ sudo apt-get install openjdk-7-jre
After installing the new java runtime (jre) it will still not be the default. To set the new jre to your default use:

$ sudo update-alternatives --config java

Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java 1061 auto mode
1 /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java 1061 manual mode
2 /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java 1051 manual mode

Press enter to keep the current choice
Having selected option 2 the java version should return something similar to:

$ java -version
java version "1.7.0_65"
OpenJDK Runtime Environment (IcedTea 2.5.1) (7u65-2.5.1-5~deb7u1)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
The runtime package delivers the scripts necessary to run the MaryTTS Server, which can be used via a browser of the client to synthesize speech. The server can be launched with:

$ /opt/marytts-5.1/bin/marytts-server.sh
This can then be used either through a browser or via the MaryTTS Client. The browser address will be:

http://(RaspPI_IP):59125
The MaryTTS Client, which is a Java GUI can be launched with:

$ /opt/marytts-5.1/bin/marytts-client.server
Launch the Server

2. Edit L_SonosTTS.LUA (Download Apps -> Develop Apps -> Luup files)

- edit the SAY_EXECUTE variable, replace the 5th line with the Google URL to:

http://(RaspPI_IP):59125/process?INPUT_TYPE=TEXT&OUTPUT_TYPE=AUDIO&FAKE=%s&INPUT_TEXT=%s&LOCALE=en_US&AUDIO=WAVE_FILE

* Please replace the (RaspPI_IP) with your device IP and make sure to put them inside the quotes.

- Upload, replace, restart LUUP.

3. Test and enjoy! Congrats, you're done. No more relying on other TTS servers.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: tomgru on July 29, 2015, 04:43:22 pm
I read about Microsoft  Translator API this afternoon and I am now convinced that adding this TTS engine is doable.
For the user, that would be more difficult to setup because an account has to be created on a particular platform and a new application has to be declared by the user to get the identifiers that will be required by the plugin.
For the plugin itself,  the new thing is that a session token has to be obtained and renewed when necessary.

So I will add this new engine to the plugin. Should be available in few days.

Any idea if the Microsoft speech is as good as Google speech ?

Note that the account is free if you translate less than 20 000 characters per month. That's largely enough for few TTS messages per day.

Speaking on behalf of Microsoft (I work there), i'm sure it's MUCH better!!!  ;D

Truthfully, i have no idea... and work no where near that side of the company. However, if you have any issues, let me know and i'll try to find a contact for you if possible!

Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on July 29, 2015, 06:03:19 pm
I will consider MaryTTS too.
Note that MaryTTS produces WAV files so this could be a problem with the Vera memory.
The quality of french voices looks not very good.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: SteveZ on July 29, 2015, 08:34:43 pm
I just wanted to report back that running OS X in a virtual box with the tts server installed does indeed work. there are many tutorials on how to do this. here are some links for anyone else interested.

http://www.macbreaker.com/2014/05/os-x-mavericks-in-virtualbox-with-niresh.html (http://www.macbreaker.com/2014/05/os-x-mavericks-in-virtualbox-with-niresh.html)

https://wolfpaulus.com/jounal/mac/ttsserver/ (https://wolfpaulus.com/jounal/mac/ttsserver/)
Title: Re: Google TTS is now protected against robot and automation systems
Post by: michelhamelin on July 29, 2015, 10:19:15 pm
1 -Maybe buy a cheap Android tablet
2-Install Imperihome ,(tts engine is working)
3-Plug line-out in to Sonos line-in

Sorry for bad explanation i m not very good in English writing.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on July 30, 2015, 12:48:26 am
I will not go in this direction but note that Google translation v2 is not so expensive if you don't use a lot of text. It depends on the number of characters: $20 for a million per month. It could result to less than $1 per month for our usage. But no free quota.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on July 30, 2015, 01:08:37 am
By the way, the Google translate API v2 seems to provide translate feature but no TTS feature !
Title: Re: Google TTS is now protected against robot and automation systems
Post by: watek2k on July 30, 2015, 08:44:53 am
Another one to throw into the hat is:

https://www.ivona.com

They are the voice behind Amazon Echo, I just signed up and you get 50'00 units per month for free but I dont have a clue what a unit is lol!

Though here is that we could eventually have Echo as a full time listener and a unified voice for the Vera created alerts......

Just a thought!

Thanks for the attention.

Johnny
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on July 30, 2015, 09:51:30 am
Another one to throw into the hat is:

https://www.ivona.com

They are the voice behind Amazon Echo, I just signed up and you get 50'00 units per month for free but I dont have a clue what a unit is lol!

Though here is that we could eventually have Echo as a full time listener and a unified voice for the Vera created alerts......

Just a thought!

Thanks for the attention.

Johnny

Are you sure it is free or that you have a free quota ?
Maybe it is free because at a beta stage ? What exactly afyer the beta stage ?

I found the explanation about how is calculated a unit:
Quote
Number of units is calculated by dividing number of characters in the input text by 200 and rounding up the result. SSML tags are removed from the calculation. There is no pre-paid model, so no upfront investment is needed to use the service.
http://developer.ivona.com/en/speechcloud/introduction.html
As I understand, each TTS request will cost 1 unit if your text is less than 200 characters.

Where did you find that there is a free quora ?

API looks a little more complex. But that is probably doable.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on July 30, 2015, 10:12:19 am
Ivona is using chunked data to provide the audio file.It is apparently not compatible with wget that we use until now to get the audio file. So implementing the use of this new engine would probably be more difficult and require more lua code.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: michelhamelin on July 30, 2015, 10:42:26 pm
Thanks to this, I've installed MaryTTS (http://mary.dfki.de/) on my Raspberry PI (that was only running the Hue Server for the Amazon ECHO Workaround). This is for those that don't have a 24/7 Mac server running. Hopefully it helps :D

Here's what I did (Full Steps).

1. SSH into Raspberry PI

$ cd Downloads
$ wget https://github.com/marytts/marytts/releases/download/v5.1/marytts-5.1.zip
Unzip the application to the /usr/bin directory

$ sudo unzip marytts-5.1.zip -d /opt
At this point it will not run unless the you have already installed Java 1.7 you can determine the current version of Java by executing:

$ java -version
Install the required version of Java (also add openjdk-7-jdk if you intend to do any java development):

$ sudo apt-get install openjdk-7-jre
After installing the new java runtime (jre) it will still not be the default. To set the new jre to your default use:

$ sudo update-alternatives --config java

Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java 1061 auto mode
1 /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java 1061 manual mode
2 /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java 1051 manual mode

Press enter to keep the current choice
  • , or type selection number: 2

Having selected option 2 the java version should return something similar to:

$ java -version
java version "1.7.0_65"
OpenJDK Runtime Environment (IcedTea 2.5.1) (7u65-2.5.1-5~deb7u1)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
The runtime package delivers the scripts necessary to run the MaryTTS Server, which can be used via a browser of the client to synthesize speech. The server can be launched with:

$ /opt/marytts-5.1/bin/marytts-server.sh
This can then be used either through a browser or via the MaryTTS Client. The browser address will be:

http://(RaspPI_IP):59125
The MaryTTS Client, which is a Java GUI can be launched with:

$ /opt/marytts-5.1/bin/marytts-client.server
Launch the Server

2. Edit L_SonosTTS.LUA (Download Apps -> Develop Apps -> Luup files)

- edit the SAY_EXECUTE variable, replace the 5th line with the Google URL to:

http://(RaspPI_IP):59125/process?INPUT_TYPE=TEXT&OUTPUT_TYPE=AUDIO&FAKE=%s&INPUT_TEXT=%s&LOCALE=en_US&AUDIO=WAVE_FILE

* Please replace the (RaspPI_IP) with your device IP and make sure to put them inside the quotes.

- Upload, replace, restart LUUP.

3. Test and enjoy! Congrats, you're done. No more relying on other TTS servers.


Please Can you Post  L_SonosTTS.LUA  corrected put the correction in capital letters
Thanks
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on July 31, 2015, 01:52:15 am
MaryTTS and Microsoft Translator should be available very soon, I am working on it since yesterday.
Maybe today  or tomorrow...
Title: Re: Google TTS is now protected against robot and automation systems
Post by: RHINESEL on July 31, 2015, 08:12:48 am
Thank you!  I actually miss Vera talking to me. #firstworldproblems
Title: Re: Google TTS is now protected against robot and automation systems
Post by: JS007 on July 31, 2015, 04:56:49 pm
https://support.google.com/websearch/answer/86640?hl=en

hmmm, sounds like they did this to block Hola traffic and inadvertently blocked this site too

glad this thread was here, save me from researching and thinking new vera release broke my system

who knows google may fix on their end too, as sure many apps blind people use are also effected

Title: Re: Google TTS is now protected against robot and automation systems
Post by: JS007 on August 01, 2015, 01:33:08 am
not sure if this helps anyone with a fix

but someone posted this online

https://github.com/zaf/asterisk-googletts/commit/ee23da1863a47733bef6a2aa57d3947787ca9985

got the link from this article

https://mojolingo.com/blog/2015/importance-of-vendor-relationships-in-apis/

Title: Re: Google TTS is now protected against robot and automation systems
Post by: JuniorJedi on August 01, 2015, 04:24:54 am
+1



Quote


Please Can you Post  L_SonosTTS.LUA  corrected put the correction in capital letters
Thanks
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on August 01, 2015, 05:57:46 am
I just committed changes. You can now use 2 new engines. Please switch to the 2 new topics.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on August 01, 2015, 06:07:03 am
not sure if this helps anyone with a fix

but someone posted this online

https://github.com/zaf/asterisk-googletts/commit/ee23da1863a47733bef6a2aa57d3947787ca9985

got the link from this article

https://mojolingo.com/blog/2015/importance-of-vendor-relationships-in-apis/

I will take a look. Maybe just changing the user agent in the request header could help...


The most important is that a good alternative (Microsoft) is now vailable. 8) So solving Google problem is less urgent.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on August 01, 2015, 07:18:46 am
The result of the wget command run by the plugin is:

wget: server returned error: HTTP/1.1 503 Service Unavailable
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lakewoodjazz on August 01, 2015, 09:11:22 am
I posted an FYI  in another thread but perhaps this is a better location.
Sonos tech support said their new update requires any sonos file to have a bandwidth of 16k minimum. He felt that is why Vera says "success" to a Google tts scene yet silence interrupts any streaming music. The say mp3 we are sending may be at a bandwidth of 16k or below.  I hope this helps because I miss my talking house. As a newbie to the forum I want to thank everyone for all the info you share so graciously.
Title: Re: Google TTS is now protected against robot and automation systems
Post by: BOFH on August 01, 2015, 09:54:54 am
Thanks Lolodomo. Next time I see a sale on Sonos I'll have to get me one. Trying to avoid using Google as much as possible as they have enough on me already. :)
Title: Re: Google TTS is now protected against robot and automation systems
Post by: lolodomo on August 01, 2015, 02:50:55 pm
not sure if this helps anyone with a fix

but someone posted this online

https://github.com/zaf/asterisk-googletts/commit/ee23da1863a47733bef6a2aa57d3947787ca9985

got the link from this article

https://mojolingo.com/blog/2015/importance-of-vendor-relationships-in-apis/

You are the best.

I have found in this code that several parameters were added in the HTTP request. And believe me, it works again 8)
I just need now to understand the meaning of these parameters "total", "idx", "client", ...
Title: Re: [FIXED] Google TTS engine is no more working
Post by: lolodomo on August 02, 2015, 06:00:35 am
I finally fixed the problem with Google API by just adding "&client=Vera" in the request !
Google TTS is back.

You have to update from this link: http://code.mios.com/trac/mios_sonos-wireless-music-systems/browser/trunk
You have to upload 4 files: I_Sonos1.xml + J_Sonos1.js + L_SonosTTS.lua + S_Sonos1.xml. Take them from the ZIP file.

As a bonus, you will discover that now you have languages per country in the UI, for example British Englsh and American English.
That is available for Google TTS, Microsoft Translator TTS and MaryTTS.
In scenes, use for example en-US or fr-CA. Of course you can continue using fr or en.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: wezley69 on August 02, 2015, 12:51:00 pm
I restored my system back to a few days before Google translation broke.  I then uploaded the new files you listed.  I checked the settings on the device and all looked fine.  From the TTS page I can't get the test to work.  Attached is the log.

Edit:  Working now.  Removed entire plugin, located latest zip 221.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: tomgru on August 02, 2015, 09:11:12 pm
this worked for me for Google.  Still no joy with MS.... appreciate the fixes!
Title: Re: [FIXED] Google TTS engine is no more working
Post by: brolin on August 03, 2015, 01:15:04 am
Hi,

This is how I update the 4 files.

I click on APPS-->Develop Apps-->Luup files and upload the 4 files as mentioned. I reload vera 3 and there is still no joy.

Do I have to uninstall the Sonos application and reinstall it? How do I reinstall it?

Title: Re: [FIXED] Google TTS engine is no more working
Post by: MNB on August 03, 2015, 01:36:08 pm
@loldomo,
Slow question, I've updated my files based on your latest, looking at the Sonos device>TTL tab; I can now see Google, Mary and Microsoft selections. I assume that all three are  now working? If that is the case do we're happy with the original Google translator do we need to populate the Mary and/or Microsoft entries? thanxs Mike

I finally fixed the problem with Google API by just adding "&client=Vera" in the request !
Google TTS is back.

You have to update from this link: http://code.mios.com/trac/mios_sonos-wireless-music-systems/browser/trunk
You have to upload 4 files: I_Sonos1.xml + J_Sonos1.js + L_SonosTTS.lua + S_Sonos1.xml. Take them from the ZIP file.

As a bonus, you will discover that now you have languages per country in the UI, for example British Englsh and American English.
That is available for Google TTS, Microsoft Translator TTS and MaryTTS.
In scenes, use for example en-US or fr-CA. Of course you can continue using fr or en.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: jonstrasser on August 03, 2015, 10:55:47 pm
Hi
Where are the zip files?   Or do I have to download the 4 files from the trunk 223 site and then zip them?
Thanks
Title: Re: [FIXED] Google TTS engine is no more working
Post by: SteveZ on August 04, 2015, 12:50:51 am
Hi
Where are the zip files?   Or do I have to download the 4 files from the trunk 223 site and then zip them?
Thanks

you need to download the entire zip folder, click on the zip archive button on the bottom of the page, you cannot download the individual files, they wont work. then unzip the the 4 needed files to a separate folder, upload those to your vera. make sure to check mark the relaod luup button

http://code.mios.com/trac/mios_sonos-wireless-music-systems/browser/trunk (http://code.mios.com/trac/mios_sonos-wireless-music-systems/browser/trunk)
Title: Re: [FIXED] Google TTS engine is no more working
Post by: lolodomo on August 04, 2015, 04:04:46 am
@loldomo,
Slow question, I've updated my files based on your latest, looking at the Sonos device>TTL tab; I can now see Google, Mary and Microsoft selections. I assume that all three are  now working? If that is the case do we're happy with the original Google translator do we need to populate the Mary and/or Microsoft entries? thanxs Mike

All three are working, at least for me. Problems are reported with Microsoft Translator by few of you.
Of course you have to setup engine only if you want to use it.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: MNB on August 04, 2015, 01:06:31 pm
@lolodomo,
Can you provide an example as to what the specific URL's should be for each engine (Google, Mary, Microsoft). thanxs Mike
Title: Re: [FIXED] Google TTS engine is no more working
Post by: RHINESEL on August 04, 2015, 02:20:15 pm
Will this plugin be updated through the App Store or do we need to do it manually?  I can wait a week for the app to auto update if need be.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: lolodomo on August 04, 2015, 04:51:59 pm
Will this plugin be updated through the App Store or do we need to do it manually?  I can wait a week for the app to auto update if need be.

Yes I will try to do it but probably not in the coming week.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: RHINESEL on August 04, 2015, 07:06:06 pm
Ok, no problem.  I'm patient for your great work!  If need be I'll do it manually but I'd rather the system do it itself.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: jonstrasser on August 04, 2015, 08:35:46 pm
google now working - thanks for the patch!
Title: Re: [FIXED] Google TTS engine is no more working
Post by: brolin on August 05, 2015, 12:10:46 am
Hi,

I need more help. I have not changed anything other than the 4 files as instructed.

I have updated the files and can see 'Mary TTS server URL' etc.
In the sonos plugin-->TTS, I entered the text of 'test' and click on 'say'.
At the sonos controller, I still get the error message of 'unable to encode...etc'

Please see attached pciture.

What am I not doing right?

Title: Re: [FIXED] Google TTS engine is no more working
Post by: jolerius on August 05, 2015, 03:57:26 pm
I am also still having the problems and cant play tts
Title: Re: [FIXED] Google TTS engine is no more working
Post by: kapstaad on August 05, 2015, 09:04:01 pm
For those having trouble with the zipped 4-file set offered by lolodomo several days ago, I can tell you it didn't work for me either.  I went to the repository http://code.mios.com/trac/mios_sonos-wireless-music-systems/browser/trunk (http://code.mios.com/trac/mios_sonos-wireless-music-systems/browser/trunk) and archived up the latest versions of just those 4 files (I_Sonos1.xml, J_Sonos1.js, L_SonosTTS.lua and S_Sonos1.xml), downloaded the zip, extracted it, and uploaded the files via "Apps->Develop Apps->Luup files->Upload", restarted Vera, and have been able to use Google and Microsoft successfully ever since.  YMMV but it's probably worth a shot ;)

PS - Make sure you don't have any "extra" versions of the 4 files in your /etc/cmh-ludl directory before you restart.  I had an extra L_SonosTTS.lua file (not gzip'd!).  Lua would load that file before any compressed version.  If you use the MiOS web interface via Develop Apps to upload, your uploaded files will be automagically gzip'd :)
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Stoosh on August 08, 2015, 12:33:13 pm
You guys are great, this fix worked perfectly, sure missed that morning weather update in my master bathroom!! :) :)
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Hippogriff on August 09, 2015, 10:10:24 am
I can confirm that I did what kapstaad stated and I have got Say functionality back now. Thank you.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: wezley69 on August 09, 2015, 11:46:35 am
Tried Trunk 225 and MS still doesn't work for me.  Attached is the log file.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: brolin on August 10, 2015, 03:46:47 am
Hi,

I tried again today by downloading the necessary files (zip and extract) and it works. Beautiful.

I noticed that today I downloaded the zip file 'trunk-225'. The one that doesn't work was 'trunk-221'

Hope it help someone...

Title: Re: [FIXED] Google TTS engine is no more working
Post by: Spudz72 on August 12, 2015, 03:56:29 pm
Something very strange happened today... I was having the same TTS issue when everything stopped working and then found out that it was google that made the changes to the API and then this duscussion thread.  I had planned to try the fix mentioned but just haven't had time.  Then all of the sudden this morning without any changes I was getting TTS alerts on my Sonos from Vera Scenes...  I though that was strange since I hadn't put the fix in yet.  I figured maybe google changed there mind on whatever they changed.  Well it only worked this morning. Now it is back to not working again..  Just wondered if anyone else noticed this? 
Title: Re: [FIXED] Google TTS engine is no more working
Post by: lakewoodjazz on August 12, 2015, 08:25:40 pm
Same here. My wife and I cheered  when we heard the house talk today!
Worked for about half a day then stopped.
Coincidently I got an email from vera support today that said the developer has posted a fix and if necessary they will apply the fix if I don't feel comfortable doing it. Michael Monoran Senior Customer Care Advocate has offered to do it once i enable remote tech support.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Spudz72 on August 12, 2015, 11:03:15 pm
Hi,

I need more help. I have not changed anything other than the 4 files as instructed.

I have updated the files and can see 'Mary TTS server URL' etc.
In the sonos plugin-->TTS, I entered the text of 'test' and click on 'say'.
At the sonos controller, I still get the error message of 'unable to encode...etc'

Please see attached pciture.

What am I not doing right?

I am frustrated.. I followed the instructions exactly, then rebooted my vera but can't play any TTS.  I see the new lines for other TTS Server URL but when I put in some txt and hit Say I get nothing.  My Sonos controller also gives the same error message.  I am having the exact same problem as above.  I see your next post says you got it working but what did you do different?  The files I downloaded were trunk-225. 

Someone help please. I decided I needed Sonos TTS so took the time to figure this out but no dice..  (I was teased this morning when TTS started working again without the fix, but then stopped again this afternoon)

Edit: When I put in some txt and his SAY button on Vera and have my Sonos App on my iPhone open it pops up and says "Unable to play 'Say.35.mp3' the track is not encoded correctly. 
Title: Re: [FIXED] Google TTS engine is no more working
Post by: lakewoodjazz on August 13, 2015, 10:55:06 am
Last night I loaded the 4 files from the trunk 225 zipped download and installed as lolodomo instructed.
IT WORKS! I am using google tts as before and all previous scenes are working again.
:)

What are the initials for the British English option?

Here's a sample luup code I use......

luup.call_action("urn:micasaverde-com:serviceId:Sonos1", "Say",
                 {Text="Door Open. Apartment Front Door Open", Language="en", GroupZones="ALL",
                  Volume=60, SameVolumeForAll="true"},
                 48)
Since my current usage for tts is with "ALL" (3) of my Sonos zones I have only installed one Sonos device (#48). If I want tts to work in scenes that are for specific locations do I need to install a Sonos2 and Sonos3 device and use it in the luup code?

Also, can I record and save my own voice verbiage as an mp3 and call it up from my nas in a scene?
THANKS!
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Spudz72 on August 13, 2015, 08:17:28 pm
Glad to hear it worked for you!  Don't understand why I did the same thing though and I get the not encoded correctly error!  I haven't heard from lolodomo so I figured I would contact Vera support and see what they have to say since another user on here mentioned they had done that. 

Last night I loaded the 4 files from the trunk 225 zipped download and installed as lolodomo instructed.
IT WORKS! I am using google tts as before and all previous scenes are working again.
:)

What are the initials for the British English option?

Here's a sample luup code I use......

luup.call_action("urn:micasaverde-com:serviceId:Sonos1", "Say",
                 {Text="Door Open. Apartment Front Door Open", Language="en", GroupZones="ALL",
                  Volume=60, SameVolumeForAll="true"},
                 48)
Since my current usage for tts is with "ALL" (3) of my Sonos zones I have only installed one Sonos device (#48). If I want tts to work in scenes that are for specific locations do I need to install a Sonos2 and Sonos3 device and use it in the luup code?

Also, can I record and save my own voice verbiage as an mp3 and call it up from my nas in a scene?
THANKS!
Title: Re: [FIXED] Google TTS engine is no more working
Post by: lakewoodjazz on August 13, 2015, 09:13:11 pm
Yep its working alright. 
It was me that got vera support to ffer help.
"Michael Monoran Senior Customer Care Advocate offered to do it once i enable remote tech support."
Good luck!
I find it pretty strange it worked by itself for half a day.......
Title: Re: [FIXED] Google TTS engine is no more working
Post by: brolin on August 13, 2015, 11:49:25 pm
Hi,

I didn't do anything extra. Just the same steps again.
Once the 4 files were uploaded, I switched off Vera, walked away (you know the feeling) and came back minutes later to restart it.

Started the sonos controller in my android so that I can see any error message.  Went into local vera web, typed some text and click on 'say' and it just worked... No additional steps were involved between my 1st attempt and 2nd attempt...

Title: Re: [FIXED] Google TTS engine is no more working
Post by: Spudz72 on August 14, 2015, 10:46:29 am
I give up!  I have now uploaded the same 4 files again exactly as before and then rebooted vera and still when I try TTS say command it says file not encoded correctly.  Now I did notice you said you had "switched off" vera.  I didn't actually unplug it I just used the Settings/Net & Wifi/Reboot option which should do the same thing as it says it is rebooting vera and it takes about 5 mins.  So then I tried unplugging it for 10 seconds and plugging it back in and then tried again but the same thing. 

Vera support has not replied yet...  My background is IT so the steps are not exactly difficult, and clearly I am not the only one that has had the same issue, so not sure what to think. 

I would love it if the developer (lolodomo) would chime in with any ideas or thoughts? 

Thanks in advance

Hi,

I didn't do anything extra. Just the same steps again.
Once the 4 files were uploaded, I switched off Vera, walked away (you know the feeling) and came back minutes later to restart it.

Started the sonos controller in my android so that I can see any error message.  Went into local vera web, typed some text and click on 'say' and it just worked... No additional steps were involved between my 1st attempt and 2nd attempt...
Title: Re: [FIXED] Google TTS engine is no more working
Post by: SteveZ on August 14, 2015, 11:14:09 am
Spudz, Are you downloading the entire zip archive and then unziping the files on your computer? the files will not work if you download them directly.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Spudz72 on August 14, 2015, 11:42:29 am
Spudz, Are you downloading the entire zip archive and then unziping the files on your computer? the files will not work if you download them directly.

Yes that is exactly what I did.  I had saw someone else post about this before I had attempted it so made sure to do that.  My exact steps are below.

1. Downloaded the zip file from trunk225 site.
2. Unzipped the file to my windows computer, which created a folder called trunk
3. Inside trunk folder was a folder called "services" plus 11 other files (8 .png files, and 11 other files)
4. I created a folder within the trunk folder called "updates" and then moved the 4 updated files (I_Sonos1.xml, J_Sonos1.jsp, L_Sonos1.lua, S_Sonos1.xml) to this folder just so it was easier to only upload those 4 files and not accidentally some others
5. On Vera UI7 interface went to Apps/Develop Apps/Luup Files and then uploaded these 4 files and made sure Restart Luup after upload was checked off" 
6. Clicked Done after each upload.
7. Rebooted my veralite. 

Tell me what I did wrong?  Not getting it...
Title: Re: [FIXED] Google TTS engine is no more working
Post by: SteveZ on August 14, 2015, 11:59:19 am
That all sounds correct, only the 4 files are required when running the latest version 1.3 I think. if you were not running the latest version you might try uploading all of them except the services folder or the UI4.json, they are not required. another common problem is having the secure vera check marked in the vera settings. make sure that is unchecked.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Spudz72 on August 14, 2015, 12:12:43 pm
That all sounds correct, only the 4 files are required when running the latest version 1.3 I think. if you were not running the latest version you might try uploading all of them except the services folder or the UI4.json, they are not required. another common problem is having the secure vera check marked in the vera settings. make sure that is unchecked.

That's what I read also.  I know the updated files have been uploaded because I can see the extra TTS options like MaryTTS and Microsoft and OSX TTS etc.  They weren't showing before I uploaded these 4 files.  I do not have secure vera checked either and never have.  I can't find where that option is but my vera is open just by going to the IP address so I assume it is not turned on..

Lastly I am not on the latest UI7 firmware from a few weeks back.. haven't updated yet.  I'm still on 1.7.599 but don't think that has anything to do with it?
Title: Re: [FIXED] Google TTS engine is no more working
Post by: SteveZ on August 14, 2015, 12:22:03 pm
you have tts engine and default engine both set to google and the google tts url set to http://translate.google.com

Title: Re: [FIXED] Google TTS engine is no more working
Post by: Spudz72 on August 14, 2015, 12:41:49 pm
you have tts engine and default engine both set to google and the google tts url set to http://translate.google.com

Yes sir!  See attached of what my TTS screen looks like and also what my phone shows on my sonos app when I put in some txt and click SAY command which use to work before google changed things..

Title: Re: [FIXED] Google TTS engine is no more working
Post by: SteveZ on August 14, 2015, 12:50:16 pm
I have no idea, something must be corrupt. I would upload all 10 files from the trunk 225, you dont need the png, UI4.json or the services folder. might take two uploads to get them all. after you upload the second set click the reload luup check box.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Spudz72 on August 14, 2015, 01:15:31 pm
I have no idea, something must be corrupt. I would upload all 10 files from the trunk 225, you dont need the png, UI4.json or the services folder. might take two uploads to get them all. after you upload the second set click the reload luup check box.

That was it!  It finally works now!  Yay! 

All I did was upload all the other 7 files as I had already uploaded the other 4 updated files about 4 or 5 times (also the D_Sonos1_UI4.json file since I selected it by accident).  I rebooted and now it all works again.  So something must have somehow got corrupt with one of the other 7 files.

Happy now!  Thanks for everyone's input!
Title: Re: [FIXED] Google TTS engine is no more working
Post by: lolodomo on August 15, 2015, 06:16:46 am
The file D_Sonos1_UI4.json should not be uploaded by UI5 and UI7 users. I would suggest to ssh to the Vera and to delete it.

There is no need to reboot the Vera after uploading files, a simple luup reload is ok.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Spudz72 on August 15, 2015, 08:33:49 pm
The file D_Sonos1_UI4.json should not be uploaded by UI5 and UI7 users. I would suggest to ssh to the Vera and to delete it.

There is no need to reboot the Vera after uploading files, a simple luup reload is ok.

Seems to be working fine but of course if you say it should be deleted I will do so.  I have successfully SSH'd into my veralite to do this but not sure where this file I need to delete is located exactly?  This is the first time I have ssh'd into my veralite.  If you could give me the path that would be most appreciated. 
Title: Re: [FIXED] Google TTS engine is no more working
Post by: chacquie on August 17, 2015, 08:37:32 pm
I'm still experiencing Google TTS outage.  I don't even see the Microsoft TTS or MaryTTS text boxes so I think I have an update issue.  Any advice on how to proceed would be greatly appreciated. 

Here is what I've done so far:

REM --  I'm on UI5 v1.5.622 .
1.  I have downloaded the zip files from trunk 225.
2.  I have SCP'd into my Vera and deleted 10 files related to the Sonos plugin from etc\cmh-ludl\ (did not have the UI4 json file).
3.  I have reloaded the trunk 225 files with the AVTransport, GroupRenderingControl, and RenderingControl first with no lua reload followed by the remaining files with a lua reload.

No joy so I completely removed all 10 files, uninstalled plugin, killed browser session
4.  Loaded Sonos Controller from Mios Marketplace.
5.  Did discovery and setup process.
6.  Verified all looks good from the TTS checklist with the exception of #9.

Device still does not have the additional fields for the new TTS services and TTS testing through the TTS tab does not work.  I get the "xxxxx is not encoded correctly" message from Sonos application.  All other Sonos functionality is working.

I'm at the end of my ideas.  Thanks in advance for anyone that can offer any suggestions. 
-Paul
Title: Re: [FIXED] Google TTS engine is no more working
Post by: SteveZ on August 17, 2015, 10:42:32 pm
Did you download the whole zip file by using the zip archive link at the bottom of the trunk 225 page? You cannot download the files individually
Title: Re: [FIXED] Google TTS engine is no more working
Post by: chacquie on August 17, 2015, 10:57:38 pm
Yep, that is what I did.  I see I wrote "files" and that was misleading.  It was just a single zip file and it was extracted to "tags_1.3-225\tags\1.3"
Title: Re: [FIXED] Google TTS engine is no more working
Post by: SteveZ on August 17, 2015, 11:42:00 pm
You don't need to delete the existing files, doing the upload will overwrite them. Not sure why it's not working though. Now that you reinstalled it from the app store you are back at the version 1.3 with the broken google TTS, uploading the new 4 files and checking the reload luup box before hitting go should work.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: lemrock on August 18, 2015, 02:05:04 am
chacquie, I'm having a similar problem. I uploaded the 4 files from trunk 225 and did a luup reload. Everything appeared to work correctly. The Google support was back and working and the Microsoft voice (after setup) was working. Then things went wrong after about two days and I hadn't changed anything. Any txt I was sending started to repeat, meaning typing in the Say box "hello" came back as "hello hello hello". The repeats were there no matter if I used Google or Microsoft. I unloaded the plugin and uploaded the 4 files from trunk 225 but this time the Microsoft settings were gone and the Google voice didn't work. SO I loaded the 4 files from trunk 219 and the Microsoft settings came back and works but the Google voice doesn't work for me anymore. I'm still getting the repeats ans don't know how to fix that.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: lemrock on August 19, 2015, 09:01:19 pm
Everything is fixed now. It turns out I had delete to reload the Sonos application on my PC. So now the repeats are gone and Google voice is back.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: chacquie on August 19, 2015, 10:16:49 pm
Thank you for the input.  I'll give trunk 219 a try.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: chacquie on August 19, 2015, 10:35:55 pm
I am up and running now.  I had to go to trunk 221.  My changes weren't showing initially because I had a browser session buried behind some other windows and I think I had some caching going on.  Thanks for the assist.  My home is now talking smack to my wife again..  ;)
Title: Re: [FIXED] Google TTS engine is no more working
Post by: nortish on August 26, 2015, 06:02:39 pm
Thanks!
Worked for me after doing as Spudz72. Had to upload all the files except Ui4 and the service folder.

Many thanks for your great work guys!
Title: Re: [FIXED] Google TTS engine is no more working
Post by: morto1 on September 05, 2015, 12:56:53 am
downloaded the zip, extracted the 4 files and uploaded to vera2 all works sweet now, cheers for your help
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Kryckmeister on November 14, 2015, 01:58:05 pm
I had to uninstall cuz an update wasn't possible. So I have installed 1.4, no dice. I tried with the file you mention, still nothing. I see nothing happening anymore in the app in Vera nor in my phone. Everything else works in the app works. The music won't stop, it's like they don't connect when it comes to TTS but all other commands work perfectly.

I have no idea what to do. Please, help me out!
Title: Re: [FIXED] Google TTS engine is no more working
Post by: RHINESEL on November 15, 2015, 10:40:13 pm
After the fix, Google did something else again.  Google TTS is very spotty.  It works and doesn't without rhyme or reason.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Kryckmeister on November 16, 2015, 03:07:05 pm
I had support help me out. Tried two of my Sonos products, worked fine. Tried to change language and since then, nothing works anymore.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: ykamenet on November 17, 2015, 09:46:18 am
Switch to Microsoft TTS. It works with no issues. The voice is male and may not be as pleasant as the google TTS one, but once I switched I had no issues since - works perfectly.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: tomgru on November 17, 2015, 11:06:22 am
Switch to Microsoft TTS. It works with no issues. The voice is male and may not be as pleasant as the google TTS one, but once I switched I had no issues since - works perfectly.

+1.

And since I also have Amazon Echo... with Alexa (female voice)... it now sounds like a married couple in my house :-)
Title: Re: [FIXED] Google TTS engine is no more working
Post by: rafale77 on November 17, 2015, 11:57:14 am
On MSFT, change the language. The Aussie and Canadian accents are female... :)
Title: Re: [FIXED] Google TTS engine is no more working
Post by: JS007 on November 17, 2015, 03:19:15 pm
I had support help me out. Tried two of my Sonos products, worked fine. Tried to change language and since then, nothing works anymore.

make sure you selected the 2,000,000 Characters (I assume your using MS TTS)

https://datamarket.azure.com/dataset/bing/microsofttranslator

if your using google, it's hit and miss because google of side issues

Title: Re: [FIXED] Google TTS engine is no more working
Post by: tomgru on November 20, 2015, 08:33:24 pm
On MSFT, change the language. The Aussie and Canadian accents are female... :)

where did you change this.  I can't find it on the site?
Title: Re: [FIXED] Google TTS engine is no more working
Post by: rafale77 on November 20, 2015, 08:49:54 pm
On MSFT, change the language. The Aussie and Canadian accents are female... :)

where did you change this.  I can't find it on the site?

You change it within the vera plugin: change the language from "en" to "en-CA" on the TTS page of the Sonos device.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Kryckmeister on November 21, 2015, 02:52:55 am
I had support help me out. Tried two of my Sonos products, worked fine. Tried to change language and since then, nothing works anymore.

make sure you selected the 2,000,000 Characters (I assume your using MS TTS)

https://datamarket.azure.com/dataset/bing/microsofttranslator

if your using google, it's hit and miss because google of side issues
Thanks for input. I always used Google, and my native tounge worked pretty smoothly for a long time. Now I can't even use En-us.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: tomgru on November 21, 2015, 11:35:15 am
On MSFT, change the language. The Aussie and Canadian accents are female... :)

where did you change this.  I can't find it on the site?

You change it within the vera plugin: change the language from "en" to "en-CA" on the TTS page of the Sonos device.

Beautiful.  thanks. 
Title: Re: [FIXED] Google TTS engine is no more working
Post by: JS007 on November 21, 2015, 03:11:36 pm
I had support help me out. Tried two of my Sonos products, worked fine. Tried to change language and since then, nothing works anymore.

make sure you selected the 2,000,000 Characters (I assume your using MS TTS)

https://datamarket.azure.com/dataset/bing/microsofttranslator

if your using google, it's hit and miss because google of side issues
Thanks for input. I always used Google, and my native tounge worked pretty smoothly for a long time. Now I can't even use En-us.

I liked the google tts too, but they just have not been reliable anymore

I switched to ms tts with the "en-CA", and it has been very reliable

instructions for setting up the ms tts are in the first post here (in case anyone looking for)

http://forum.micasaverde.com/index.php/topic,33223.0.html

To setup the engine, you will have first to do step 1 and step 2 described here: https://www.microsoft.com/translator/getstarted.aspx
You have more details here: https://msdn.microsoft.com/en-us/library/mt146806.aspx (you have to do step 1 to 4)
As a result, you will get your credentials.
Then, you just have to set your client id and client secret in the TTS tab of the plugin.

The quality of the speech is very good, even better than Google for French. The speech is just a little too fast in my opinion. Microsoft server seems to be very fast to provide the MP3 file.

In your scenes, you have to use "MICROSOFT" to identify this engine.

just make sure you select the 2 million free characters per month, I did not when I first set up and that gave me a lot of grief trying to figure out why not working right
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Kryckmeister on December 21, 2015, 02:45:08 am
Did all that...I assume Client ID is the Customer ID and Account Key is the Microsoft Client Secret.

Reloaded and rebooted, and it's quiet.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Autom8 on January 19, 2016, 10:58:47 pm
I don't suppose the solution to using Google as the TTS has anything to do with this solution that was noticed on a Fibaro forum?  I noticed this feature also stopped working as soon as the Sonos firmware updated.

Not that it matters greatly, the MS TTS works just fine.

Quote
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.

http://forum.fibaro.com/index.php?/topic/19687-tts-sonos/page-2
Title: Re: [FIXED] Google TTS engine is no more working
Post by: upinatem on March 05, 2016, 02:03:33 pm
Did all that...I assume Client ID is the Customer ID and Account Key is the Microsoft Client Secret.

Reloaded and rebooted, and it's quiet.

I got stuck on this too. It's not the same. I found in the instructions on how you have to set this up.
From the Microsoft Azure page you need to click on Developers on the left (https://datamarket.azure.com/developer/applications)

From there you can create the Client ID. The account Key will be filled in. You can just put in https://microsoft.com for the redirect URI
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Kryckmeister on April 02, 2016, 12:46:07 pm
Thanks. Now it at least works a bit.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: rchamp26 on December 30, 2016, 01:11:49 pm
HI there, finally got a sonos play for xmas. Downloaded and installed upnp plugin and sonos plugin and followed instructions. I can control sonos (play, pause, skip, mute, volume, etc) but tts seems to not work.

The tts is set to Google english. In the Web page tts ui tab, there is only a say button but no area to enter text. I tried the lua test code in develop apps using my device id and also doesn't work. It pauses music, is silent for a few second, then skips to next song. It apears the tts isn't processing.

I attempted to use the Microsoft alternative instead, but azure marketplace is being discontinued on 12/31/2016 and existing accounts will be discontinued in april, so doesn't appear to be worth the effort.

Last, I tried downloading the latest trunk 230 from the repo and uploading the fIles manually but that didn't seem to make a difference either.

Any ideas?
Title: Re: [FIXED] Google TTS engine is no more working
Post by: mrslother on February 20, 2017, 08:11:35 pm
I have given up on the entire cloud effort for TTS. Google changes their APIs way too frequently causing disruptions and Microsoft's is just annoying to create & maintain. I find the cloud unacceptable since I use the TTS over sonos to alert my family on security issues like the garage door opens or someone left a door unlocked.

So, I wrote my own service to run on an a Windows IIS server on my network. It is written in .net and works well enough for me. I have it running on an old WinServer 2008R2 VM. Of course the IIS box has to have have Microsoft's TTS engine installed. I added additional high quality voices (ATT Natural Voices; http://rentanadviser.com/en/affiliates/att_natural_voices/att_natural_voices.aspx) so that it sounds less computer generated.

I configure the sonos plugin to use the OSX TTS server setting and point it to my IIS box. It isn't all that fancy but does the job.

PM me if you are interested.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: BOFH on February 21, 2017, 03:10:47 pm
Interesting. Would that work on Windows HomeServer 2011 as well? The TTS part is installed on it as it's basically a very neutered version of Server 2008.

I'm definitely interested as I to would prefer to keep it all local.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: wezley69 on February 23, 2017, 10:31:40 pm
Responsive  http://responsivevoice.org/   it works well.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: BOFH on February 24, 2017, 12:16:24 pm
There is an updated version of the Sonos plugin that has support for responsivevoice built in floating around on these forums. I believe it is in the Sonos MS plugin thread.
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Matsohl on March 04, 2017, 08:14:29 am
Hi, bougth my first Sonos speaker today and I can control it from Vera but the tts only worked for 10 minutes. Now nothing happens but I can still control it. What can I do, I want my Vera to speak to me  ???
 
Title: Re: [FIXED] Google TTS engine is no more working
Post by: Matsohl on March 04, 2017, 08:23:22 am
Responsive  http://responsivevoice.org/   it works well.

How do you use it?
Title: Re: [FIXED] Google TTS engine is no more working
Post by: BOFH on March 04, 2017, 10:17:14 am
Forum Search is your friend: http://forum.micasaverde.com/index.php/topic,33223.msg312329.html#msg312329
Title: Re: Google TTS is now protected against robot and automation systems
Post by: pdipesh11 on April 30, 2017, 01:45:57 am
Thanks to this, I've installed MaryTTS (http://mary.dfki.de/) on my Raspberry PI (that was only running the Hue Server for the Amazon ECHO Workaround). This is for those that don't have a 24/7 Mac server running. Hopefully it helps :D

Here's what I did (Full Steps).

1. SSH into Raspberry PI

$ cd Downloads
$ wget https://github.com/marytts/marytts/releases/download/v5.1/marytts-5.1.zip
Unzip the application to the /usr/bin directory

$ sudo unzip marytts-5.1.zip -d /opt
At this point it will not run unless the you have already installed Java 1.7 you can determine the current version of Java by executing:

$ java -version
Install the required version of Java (also add openjdk-7-jdk if you intend to do any java development):

$ sudo apt-get install openjdk-7-jre
After installing the new java runtime (jre) it will still not be the default. To set the new jre to your default use:

$ sudo update-alternatives --config java

Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java 1061 auto mode
1 /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java 1061 manual mode
2 /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java 1051 manual mode

Press enter to keep the current choice
  • , or type selection number: 2

Having selected option 2 the java version should return something similar to:

$ java -version
java version "1.7.0_65"
OpenJDK Runtime Environment (IcedTea 2.5.1) (7u65-2.5.1-5~deb7u1)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
The runtime package delivers the scripts necessary to run the MaryTTS Server, which can be used via a browser of the client to synthesize speech. The server can be launched with:

$ /opt/marytts-5.1/bin/marytts-server.sh
This can then be used either through a browser or via the MaryTTS Client. The browser address will be:

http://(RaspPI_IP):59125
The MaryTTS Client, which is a Java GUI can be launched with:

$ /opt/marytts-5.1/bin/marytts-client.server
Launch the Server

2. Edit L_SonosTTS.LUA (Download Apps -> Develop Apps -> Luup files)

- edit the SAY_EXECUTE variable, replace the 5th line with the Google URL to:

http://(RaspPI_IP):59125/process?INPUT_TYPE=TEXT&OUTPUT_TYPE=AUDIO&FAKE=%s&INPUT_TEXT=%s&LOCALE=en_US&AUDIO=WAVE_FILE

* Please replace the (RaspPI_IP) with your device IP and make sure to put them inside the quotes.

- Upload, replace, restart LUUP.

3. Test and enjoy! Congrats, you're done. No more relying on other TTS servers.
Hi, I don't have sonos, is there any way I can connect Bluetooth speaker to Raspberry PI for announcement

thanks in advance

Thanks,
Dip
Title: Re: [FIXED] Google TTS engine is no more working
Post by: BOFH on April 30, 2017, 10:53:12 am
The commands that the Sonos plugin sends out to communicate with the speaker are Sonos specific and as such won't work with eg a Bluetooth speaker. You might be able to hack 'maryTTS (since it's http) to output to the locally attached speaker by sending it the correct HTTP command string directly without going through the plugin.