Vera Alexa Plugin 7.32
-
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. -
@elcid said in Vera Alexa Plugin 7.32:
@librasun Have you tried to install JQuery on the vera, it's is now available with 7.32
Uh oh, I thought "jq" was a package included with 7.32? I'd scoured @therealdb 's notes and ReadMe, seeing references to "jq" (never once thinking that meant "JQuery").
How does one "install" "jQuery" on Vera??
-
ssh in and run
opkg update
opkg install jq -
@librasun The plug-in will take care of it. So, just set configured to 0 and it will install it.
I've had a very busy week, but tomorrow I'll have more time to re-try from scratch. Keep in mind that this is using some internal amazon stuff and the chances that they changed something is high. Anyway, it should not create <s>... unless you have announcements enabled. I'll take a deeper look tomorrow. I've tested with 7.32 beta, but not this build, and it worked, but I've not tested all the possibile variants.
-
Also if anyone in the future has Cookie issues, you must turn of JavaScript in Firefox to get the correct cookie file, I didn't and it wasn't working.
-
@pabla said in Vera Alexa Plugin 7.32:
Also if anyone in the future has Cookie issues, you must turn of JavaScript in Firefox to get the correct cookie file, I didn't and it wasn't working.
Does this apply to Chrome as well? And if so, do you mean "Disable Javascript" for all sites, forever? Or just while VeraAlexa plug-in is configuring itself?
(Because I did none of that.
-
@librasun I am not sure if it applies to chrome but I assume it would, because when you disable JavaScript and login you get the Captcha login screen (which is what you are trying to bypass).
Yes temporarily disable JavaScript until you have got the cookie file.
-
Elcidreplied to Pabla on Mar 25, 2021, 5:35 PM last edited by Elcid Mar 25, 2021, 1:38 PM
@pabla I never turn off JS, I use Export Cookies Addon to export to a txt file. I will add i do it on Android Firefox I login to layala.amazon.co.uk. Once logged in i export amazon.co.uk to text file. I then copy the contents to .alexa.cookie
-
@pabla said in Vera Alexa Plugin 7.32:
Yes temporarily disable JavaScript until you have got the cookie file.
Perhaps wise advice, but I'm gonna sit on my hands for now if only because the .alexa.cookie file manifested without any fuss when I first installed the plug-in. I took that as a sign that all is well.
Unless advised otherwise and/or someone explains how to examine the cookie file to know I got the "wrong" one?
65/119