Vera Alexa Plugin 7.32
-
@therealdb said in Vera Alexa Plugin 7.32:
@catmanv2 you need announcements on. Do you have them enabled?
Aye. UseAnnouncements = 1 (And I get lovely synced announcements across the house)
C
-
@pabla said in Vera Alexa Plugin 7.32:
@librasun I am probably the least qualified person on this thread to answer this question but I will give it a try. Maybe confirm that your Living Room Alexa device isn't called Living Room Echo or something, cause that will be the name you'll have to use.
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", "Say", {Text="Hello from Vera Alexa", Volume=10, GroupZones="Living Room" }, 344)
Funny, I've tried precisely that command before (and just tried again for the 10th time), and it always produces a spoken error response:
"Sorry, I'm having trouble using the Simon Says skill right now." (or something very similar)I am also getting the feeling that GroupZones are somehow different from -d (Device), but I have no GroupZones set up. Only a bunch of Echo devices with names like "Living Room", "Master Bedroom", "Hall Bathroom", etc.
Will continue reading docs and these replies to learn more.
THANKS FOR THE HELPING HAND! -
I don't even get an error. Might it be because I don't have the Simon Says skill?
Would be interested in understanding how to use some of the audio effects if anyone might have suitable syntax? Also anyone got a list of commands?
C
-
It's just odd to me that the "RunCommand" version (with "Speak") - works great for me! - works better than the purpose-built "Say" approach - produces seemingly unrelated verbal error I can't follow.
All I really need is for someone smarter than me to spell out clearly (like for a kindergartner) HOW the command strings are composed. Normally, I can work from examples, and DB's docs contain plenty, but none of them seem to fit my intentions (i.e. use MSR to run Lua on Vera to say something through a specific Echo at a specified volume, which seems so simple and straightforward).
Maybe as a group we should focus our attention, as DB suggests, on crafting a workable set of documentation so we're all clear.
-
Same here
C
-
BONUS If we play our cards right, and nail down all the options, we could beg @toggledbits to create a "Notify" template on MSR specifically for VeraAlexa.
-
I think @therealdb or someone should port that plugin's approach into an MSR
Notifier
, which could then be used universally and without the Vera dependency. It's probably the easiest extension API in MSR: "I'm here, and here's the data I need from the UI" and "here's the data you asked for and the configuration file data, send a notification". One JavaScript class, two methods, and you're done.But for now, is there something missing from the default entity that you might need?
-
@toggledbits OK for me. I don't think it's a lot of work to do, considering that you just need to execute a bash script with the right parmaters passed in
In fact, as I said, I'm running into my own system, and the vera is sending the request via UDP (and HTTP before) and it's working perfectly. But since a lot of people asked for it in the Vera OS, I tried to port it anyway and it's working, even if I didn't spend a lot of time into the Vera UI, because I'm not that proficient and because it was considered legacy 2 years ago...
Again, happy to make it user-friendly and MSR-integrated.
-
@librasun said in Vera Alexa Plugin 7.32:
Funny, I've tried precisely that command before (and just tried again for the 10th time), and it always produces a spoken error response:
"Sorry, I'm having trouble using the Simon Says skill right now." (or something very similar)Well, say is just a shortcut for a generic command. It's strange say it's not working, since it's basically sending
-e speak:'%s' -d %q
, where %s is the text, %q is the device. -
@elcid said in Vera Alexa Plugin 7.32:
@catmanv2 Here is a link to the amazon SSMl mark up syntax
Ta. I've tried I really have
C
-
@librasun said in Vera Alexa Plugin 7.32:
BONUS If we play our cards right, and nail down all the options, we could beg @toggledbits to create a "Notify" template on MSR specifically for VeraAlexa.
Heh. I've not looked at MSR yet, but the Alexa action in Reactor works like a charm...
C
-
@therealdb I've been meaning to toss you some cappuccino money for a while now, to thank you for your vast efforts in support of the Vera community.
Think I found you on PayPal under your @<your-full-name>, would that be the right and best place? (And are Euros better than USD?) -
@librasun thanks, but I have a job (well, I’m joking with my colleagues that I’m probably doing 6-7 jobs at once) and I’m doing this for the pleasure to give back and find new friends (and because I used to travel a lot and this year I had a lot of free time). So, as I’ve already said to others (@Pabla is here too) I’d appreciate if you could donate to groups trying to create a more inclusive environment, ie promoting a dev career for girls or minorities. Thanks
-
@elcid said in Vera Alexa Plugin 7.32:
@catmanv2
When i tried SSML, I seem to remember it only worked with announcements.Maybe, I have it with conversional accent and I’m loving it. It’s very natural.
-
So I've got this working:
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<voice name="Kendra"><lang xml:lang="en-AU">Hello from Vera Alexa</lang></voice>', Volume=40,GroupZones="Living Room dot"}, 22)
But can't for the life of me get the sound effects:
<audio src="soundbank://soundlibrary/animals/amzn_sfx_bear_groan_roar_01"/> </speak>
For example. Also does anyone have a list of the available voices?
TIA
C
-
@catmanv2 said in Vera Alexa Plugin 7.32:
But can't for the life of me get the sound effects:
Funny, that's one thing I've got working no problem:
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e sound:amzn_sfx_trumpet_bugle_04 -d 'Living Room'"}, 344)
43/119