when I tried to do the reset to default, it said I do not have permision
so went to a (user and account info) page so it would ask me to logon to vera, then tried it and now works again
so must be a permission thing about not being logged into vera, on the test tts page
then is stopped working again after a few tried, I am gonna do a fresh install of vera back to default as I just did a release right before this, maybe something is flaky
[quote=“lolodomo, post:10, topic:188264”]To be honest, I have not tested through a lua call but only through the plugin UI.
Is it working for you from within the UI (TTS tab of the plugin) ?
Did you upload the 4 updated files, reload and clear your WEB browser cache ?
Please enable the debug log to see if the new function is called.[/quote]
I tried reinstalling everything… and still no go. and when I watch the sonos dashboard, I don’t see an mp3 trying to be played at all. Notice in new logs it “can’t get session token”. Last logs: (do you need verbose logs?):
[quote=“JS007, post:21, topic:188264”]this is interesting
when I tried to do the reset to default, it said I do not have permision
so went to a (user and account info) page so it would ask me to logon to vera, then tried it and now works again
so must be a permission thing about not being logged into vera, on the test tts page
then is stopped working again after a few tried, I am gonna do a fresh install of vera back to default as I just did a release right before this, maybe something is flaky[/quote]
I did a fresh install of vera, then loaded backup, then plugin, then fix files and still having same issue… not sure what else to try
this is my firmware version : You are running the latest version: 1.7.1320
For you, that is perfectly clear, that is a problem of credentials.
What Vera model and Vera UI are you using ?
In case you are running UI7 and in case they introduced bugs firmware after firmware, please check that your 2 credentials information (ClientId and ClientSecret) are correctly set to variables in the advanced tab. Remember that for this advanced tab (at least with UI5), you have to clear your WEB browser cache to get an update.
If this is not a UI7 problem, then you just don’t set correctly your ClientID and ClientSecret, or maybe you don’t create your application as you should. You must get the first and the third information in the page which are named in French 'ID client" and “Secret du client”. We don’t care about the “Nom” and “URI de redirection” has to be set to https://microsoft.com
@JS007: just to understand, are you new with TTS and Sonos plugin ? I mean did it work for you correctly one day in the past with Google TTS engine and your Edge/UI7 ?
All this is just for me a clear remember that I should resist and avoid switching to UI7…
Ok, by the way, the error you get with SetCrossfadeMode is not normal. It is done just after TTS to restore the previous context. What Sonos model do you own ? That would be weird but maybe this feature is not supported by your Sonos model.
I committed few changes. If the TTS request failed, a control is done to check if the used language is available. So the logged error can be a little more detailed.
[quote=“hek, post:27, topic:188264”]Thank you @lolodomo! You are a saver.
Even if I had to sign up for a M$ account to get the speaking back.[/quote]
As I fixed Google at the same time, you will be able to compare the two and choose the best.
For French, I think I prefer Microsoft.
It is also interesting to try various country languages for example for English, voices are different.
This seems to stop working even when testing from the TTS page. Seems to work a few times there then stops. Reload is needed to have it work a few times. I set the volume level to 46 for testing from the same page.
Default language: en
Default Engine: Micorsoft
Google TTS: left as google
Microsoft Client ID: mine
Microsoft Client Secret: mine
I tried this in the scenes without success. I added Testing as the text, en as the language, engine as MICROSOFT, and the volume to 46. Nothing happens.
@JS007: just to understand, are you new with TTS and Sonos plugin ? I mean did it work for you correctly one day in the past with Google TTS engine and your Edge/UI7 ?
All this is just for me a clear remember that I should resist and avoid switching to UI7…
Ok, by the way, the error you get with SetCrossfadeMode is not normal. It is done just after TTS to restore the previous context. What Sonos model do you own ? That would be weird but maybe this feature is not supported by your Sonos model.[/quote]
Google was working up till a few days ago (been using for awhile flawlessly with Google)
when I first set to use Microsoft it worked, then after a few tries of changing language it stopped, the work a couple times after that login from above, but has not worked sense, not even afer a rebuild and reinstall
I copied in the four files from trunk-219 and it did work for a bit
the Sonos PLAY:1 Speaker is the one I use (ui7 edge fw:1.7.1320)
now I can not say it ever worked on this firmware version under Google as did not notice had stopped working until this vera release, in fact I thought the vera release broke google at first, not sure how to downgrade to test older vera firmware with new plugin code
ok, this one did not work, test 6, then the next one test 7 worked
no difference between configs, just change to 6 pressed say, then to 7 and pressed say, on 7 worked, on 4,5,6 did not (tried a about a dozen times after the working one and none worked again)
if you need more of log let me know, I saved it off
[quote=“lolodomo, post:28, topic:188264”][quote=“hek, post:27, topic:188264”]Thank you @lolodomo! You are a saver.
Even if I had to sign up for a M$ account to get the speaking back.[/quote]
As I fixed Google at the same time, you will be able to compare the two and choose the best.
For French, I think I prefer Microsoft.
It is also interesting to try various country languages for example for English, voices are different.[/quote]
is the new code still the link in the top post of this thread? trunk-219?
[quote=“JS007, post:32, topic:188264”][quote=“lolodomo, post:28, topic:188264”][quote=“hek, post:27, topic:188264”]Thank you @lolodomo! You are a saver.
Even if I had to sign up for a M$ account to get the speaking back.[/quote]
As I fixed Google at the same time, you will be able to compare the two and choose the best.
For French, I think I prefer Microsoft.
It is also interesting to try various country languages for example for English, voices are different.[/quote]
is the new code still the link in the top post of this thread? trunk-219?[/quote]
[quote=“lolodomo, post:38, topic:188264”][quote=“JS007, post:36, topic:188264”]ok, changed to new code 221 and google now works
Microsoft I get the “luup_log:144: Sonos: warning: Microsoft TTS: can’t get session token <0x7414c520>”
I am using the same client id and secret that was sometimes working on older code 219, so key should be ok[/quote]
Weird. Same problem as @tomgru.
What’s your client id ? Only letters are accepted if I correctly remember. No space.[/quote]
sent info on PM, feel free to test with them