Vera Alexa Plugin 7.32
-
@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)
-
CatmanV2replied to therealdb on Mar 25, 2021, 6:34 AM last edited by CatmanV2 Mar 25, 2021, 2:55 AM
@therealdb said in Vera Alexa Plugin 7.32:
@catmanv2 it’s in the Amazon doc I linked in readme. Also, sounds are very specific and you could send them but not in the same command with voice.
Thanks. I did look, I promise. I'll look again!<edit> Got it, eventually! Thanks.
C -
@librasun said in Vera Alexa Plugin 7.32:
@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)
Ahh per the Guru's words. Won't work with the speech. Thanks
C
-
I did some more digging, and discovered that:
WHEN I RUN THIS LUA
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e speak:'what is the temperature outside' -d 'Living Room'"}, 344)
Alexa speaks the sentence and VeraAlexa shows this LastResponse: "sending cmd:speak:what is the temperature outside to dev:Living_Room"
WHEN I RUN THIS LUA
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", "Say", {Text="what is the temperature outside", Repeat = 1}, 344)
Alexa DOES NOT speak the sentence and VeraAlexa shows this LastResponse: "sending cmd:speak:<s>what is the temperature outside</s><break time="0s" /> to dev:Living_Room "
Instead she utters, "Sorry, I'm having trouble accessing the Simon Says ??? Skill right now." then a bong tone sounds. Weird!Thus, I'll continue using the 1st construct to have Alexa speak sentences.
INSIGHT: I honestly believe the "Simon Says ???" Alexa mentions has to do with an error parsing <SSML> tags!!
-
If I use 'SAY' I need to specify a groupzone....
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<voice name="Raveena">Hello from Vera Alexa</voice>', Volume=40,GroupZones="Living Room dot"}, 22)
C
-
I tried to run that command verbatim(!) -- changing only my device # -- and get the same spoken "Sorry..." error as always. Really driving me bonkers!! Would love to use SSML in my workflow, but until this gets resolved, no go. Thanks for the suggestion(s), of course. I'm sure it's ME, not ALEXA.
-
Fun times. I took my own advice and completely removed VeraAlexa plug-in from my Vera Plus (making sure there were no hidden devices lurking, then executing a device > remove command via HTTP request in my browser). Rebooted, restarted MSR (so it would forget about deleted Entity), copied ZIP from Github, loaded files onto Vera, restarted Luup engine, created Device (it starts hidden!), restarted Luup engine again, see device in UI (no name), restart Luup yet again, see "Alexa" device, says "Configured=1" (yay!), update its "DefaultEcho" variable, etc., restart MSR in Docker, hard refresh all browsers.
And I'm back. Now HERE is the fun part... SOME of the "Say" commands work now, some ALMOST do, and others still do not.
WORKS // says "Hello from Vera Alexa"
luup.call_action("urn:micasaverde-com:serviceId:Sonos1", "Say", {Text="Hello from Vera Alexa"}, 345)
ALMOST WORKS // says "Domain" and stops
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<amazon:domain name="conversational">Hello from Alexa</amazon:domain>', Volume=10, Repeat = 1}, 345)
DOES NOT WORK // says "Sorry..." error message
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<voice name="Raveena">Hello from Vera Alexa</voice>', Volume=40,GroupZones="Living Room"}, 345)
I must be a bad person.
-
Yep, tried that. Changed GroupZones= to "Sonos Beam" (name of my Alexa-enabled Sonos device also known as "Living Room"), and still... silence.
But thanks for the tip to try!Oh wait! You're saying try piping the command to the SONOS service instead of the 'bochicchio' one... hold on... gonna try.
Answer: NOPE. Still same "Sorry, I'm having trouble accessing ___ skill right now."
-
@librasun said in Vera Alexa Plugin 7.32:
Fun times. I took my own advice and completely removed VeraAlexa plug-in from my Vera Plus (making sure there were no hidden devices lurking, then executing a device > remove command via HTTP request in my browser). Rebooted, restarted MSR (so it would forget about deleted Entity), copied ZIP from Github, loaded files onto Vera, restarted Luup engine, created Device (it starts hidden!), restarted Luup engine again, see device in UI (no name), restart Luup yet again, see "Alexa" device, says "Configured=1" (yay!), update its "DefaultEcho" variable, etc., restart MSR in Docker, hard refresh all browsers.
And I'm back. Now HERE is the fun part... SOME of the "Say" commands work now, some ALMOST do, and others still do not.
WORKS // says "Hello from Vera Alexa"
luup.call_action("urn:micasaverde-com:serviceId:Sonos1", "Say", {Text="Hello from Vera Alexa"}, 345)
ALMOST WORKS // says "Domain" and stops
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<amazon:domain name="conversational">Hello from Alexa</amazon:domain>', Volume=10, Repeat = 1}, 345)
DOES NOT WORK // says "Sorry..." error message
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<voice name="Raveena">Hello from Vera Alexa</voice>', Volume=40,GroupZones="Living Room"}, 345)
I must be a bad person.
I forgot entirely about the default echo. Mine was 3 floors away this morning.I don't have a Sonos so can't test that bit but
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<amazon:domain name="conversational">Hello from Alexa</amazon:domain>', Volume=10, Repeat = 1}, 22)
Works
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<voice name="Raveena">Hello from Vera Alexa</voice>', Volume=40}, 22)
Works.
I am not on Vera though. Openluup with full JQ AFAIK
C
-
Perhaps my never having used OpenLuup, that could be the key differentiator between my setup and yours and @therealdb 's?
I'm on a stock Vera Plus running 7.32 firmware. I'm sending all Lua commands via MSR for testing purposes.
54/119