Vera Alexa Plugin 7.32
-
The test unit I tried (and which serves as the Default output device for VeraAlexa) is indeed a Sonos Beam with Alexa built in. However, it has not (yet) mattered which device I try with, Echo, Dot, etc., nor have things improved when I refer to the default unit as "Living Room" or "Libra's Sonos" (both entries appear in Amazon's enumeration of devices on my account).
Nor have things improved if I substitute the SONOS service in place of the BOCHICCHIO one.
-
FWIW I get total silence. I'm not that bothered but just as a data point
C
-
Those codes that @therealdb posted worked fine for me oddly enough, I don't know how they weren't working earlier.
Edit: I have only tested with my Echo not any of my Sonos devices yet
-
I ran his updated code again twice - once with "UseAnnouncements" set to 0, once set to 1 - targeting my Echo device ('Kitchen') and received silence both times. Kept DebugMode = 1 throughout, but don't see any overt errors.
But I AM troubled by the weird red text mentioning "MONGOOSE" always occurring the millisecond before my Lua code runs... anyone know why it's ALWAYS there?03/26/21 13:24:43.474 Mongoose mg_read start (null) <0x6f5c2520> 01 03/26/21 13:24:43.475 Mongoose mg_read middle (null) 762 <0x6f5c2520> 01 03/26/21 13:24:43.475 Mongoose mg_read end (null) 762 <0x6f5c2520> 01 03/26/21 13:24:43.475 Mongoose mg_read after pull (null) 0 <0x6f5c2520> 08 03/26/21 13:24:43.476 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunLua <0x6f5c2520> 08 03/26/21 13:24:43.476 JobHandler_LuaUPnP::HandleActionRequest argument post_data=id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunLua&Code=function%20say(text%2C%20r%2C%20volume%2C%20zone)%0A%20%20luup.call_action(%22urn%3Abochicchio-com%3AserviceId%3AVeraAlexa1%22%2C%20%0A%20%20%20%22Say%22%2C%0A%20%20%7B%0A%20%20%20Text%20%3D%20%27%3Camazon%3Adomain%20name%3D%22conversational%22%3E%27%20..%20text%20..%20%27%3C%2Famazon%3Adomain%3E%27%2C%0A%20%20%20Repeat%3D%20r%20or%201%2C%0A%20%20%20Volume%3Dvolume%20or%2050%2C%20%0A%20%20%20GroupZones%3D%20zone%0A%7D%2C%20345)%0Aend%0A%20%0Asay(%27I%20really%20didn%E2%80%99t%20know%20how%20this%20morning%20was%20going%20to%20start.%20And%20if%20I%20had%20known%2C%20I%20think%20I%20might%20have%20just%20stayed%20in%20bed.%27%2C%201%2C%2050%2C%20%27Kitchen%27) <0x6f5c2520> 08 03/26/21 13:24:43.476 JobHandler_LuaUPnP::HandleActionRequest argument id=lu_action <0x6f5c2520> 08 03/26/21 13:24:43.476 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x6f5c2520> 08 03/26/21 13:24:43.477 JobHandler_LuaUPnP::HandleActionRequest argument action=RunLua <0x6f5c2520> 08 03/26/21 13:24:43.477 JobHandler_LuaUPnP::HandleActionRequest argument Code=function say(text, r, volume, zone) luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", "Say", { Text = '<amazon:domain name="conversational">' .. text .. '</amazon:domain>', Repeat= r or 1, Volume=volume or 50, GroupZones= zone }, 345) end say('I really didn’t know how this morning was going to start. And if I had known, I think I might have just stayed in bed.', 1, 50, 'Kitchen') <0x6f5c2520> 08 03/26/21 13:24:43.479 JobHandler_LuaUPnP::HandleActionRequest device: 345 service: urn:bochicchio-com:serviceId:VeraAlexa1 action: Say <0x6f5c2520> 08 03/26/21 13:24:43.480 JobHandler_LuaUPnP::HandleActionRequest argument GroupZones=Kitchen <0x6f5c2520> 08 03/26/21 13:24:43.480 JobHandler_LuaUPnP::HandleActionRequest argument Text=<amazon:domain name="conversational">I really didn’t know how this morning was going to start. And if I had known, I think I might have just stayed in bed.</amazon:domain> <0x6f5c2520> 08 03/26/21 13:24:43.480 JobHandler_LuaUPnP::HandleActionRequest argument Repeat=1 <0x6f5c2520> 08 03/26/21 13:24:43.480 JobHandler_LuaUPnP::HandleActionRequest argument Volume=50 <0x6f5c2520> 50 03/26/21 13:24:43.481 luup_log:345: VeraAlexa[0.92@345]:addToQueue({ Volume="50", Text="<amazon:domain name=\"conversational\">I really didn’t know how this morning was going to start. And if I had known, I think I might have just stayed in bed.</amazon:domain>", Repeat="1", GroupZones="Kitchen" }) <0x6f5c2520> 50 03/26/21 13:24:43.482 luup_log:345: VeraAlexa[0.92@345](addToQueue@234):addToQueue(2): 0 - true <0x6f5c2520> 50 03/26/21 13:24:43.483 luup_log:345: VeraAlexa[0.92@345](addToQueue@251):addToQueue(3): 1 <0x6f5c2520> 50 03/26/21 13:24:43.483 luup_log:345: VeraAlexa[0.92@345](addToQueue@254):addToQueue(4): playing <0x6f5c2520> 50 03/26/21 13:24:43.484 luup_log:345: VeraAlexa[0.92@345](checkQueue@206):checkQueue: 1 in queue <0x6f5c2520> 50 03/26/21 13:24:43.485 luup_log:345: VeraAlexa[0.92@345](checkQueue@214):checkQueue: play next <0x6f5c2520> 50 03/26/21 13:24:43.486 luup_log:345: VeraAlexa[0.92@345](setVar@126):setVar("urn:bochicchio-com:serviceId:VeraAlexa1","OneTimePassCode","",345) old value "" <0x6f5c2520> 50 03/26/21 13:24:43.487 luup_log:345: VeraAlexa[0.92@345](sayTTS@323):Executing command [TTS]: "-e speak:'<amazon:domain name=\"conversational\">I really didn’t know how this morning was going to start. And if I had known, I think I might have just stayed in bed.</amazon:domain>' -d \"Kitchen\"" <0x6f5c2520> 50 03/26/21 13:24:45.930 luup_log:345: VeraAlexa[0.92@345](setVar@126):setVar("urn:micasaverde-com:serviceId:HaDevice1","CommFailure","0",345) old value "0" <0x6f5c2520> 50 03/26/21 13:24:45.931 luup_log:345: VeraAlexa[0.92@345](setVar@126):setVar("urn:bochicchio-com:serviceId:VeraAlexa1","LatestResponse","sending cmd:speak:<amazon:domain name=\"conversational\">I really didn’t know how this morning was going to start. And if I had known, I think I might have just stayed in bed.</amazon:domain> to dev:Kitchen type:A1MPSLFC7L5AFK serial:2f69293cc2c749f6854ad6c5b41aef43 customerid:A3SL3Z0HELH3YG",345) old value "sending cmd:speak:<amazon:domain name=\"conversational\">I really didn’t know how this morning was going to start. And if I had known, I think I might have just stayed in bed.</amazon:domain> to dev:Kitchen type:A1MPSLFC7L5AFK serial:2f69293cc2c749f6854ad6c5b41aef43 customerid:A3SL3Z0HELH3YG" <0x6f5c2520> 50 03/26/21 13:24:45.932 luup_log:345: VeraAlexa[0.92@345](@279):Response from Alexa.sh: "sending cmd:speak:<amazon:domain name=\"conversational\">I really didn’t know how this morning was going to start. And if I had known, I think I might have just stayed in bed.</amazon:domain> to dev:Kitchen type:A1MPSLFC7L5AFK serial:2f69293cc2c749f6854ad6c5b41aef43 customerid:A3SL3Z0HELH3YG" <0x6f5c2520> 50 03/26/21 13:24:45.933 luup_log:345: VeraAlexa[0.92@345](sayTTS@337):Queue will be checked again in 11.726 secs <0x6f5c2520> 50 03/26/21 13:24:56.101 luup_log:345: VeraAlexa[0.92@345](checkQueue@206):checkQueue: 0 in queue <0x73a03520> 50 03/26/21 13:24:56.102 luup_log:345: VeraAlexa[0.92@345](checkQueue@210):checkQueue: queue is empty <0x73a03520>
-
therealdbreplied to LibraSun on Mar 26, 2021, 7:00 PM last edited by therealdb Mar 26, 2021, 5:59 PM
@librasun said in Vera Alexa Plugin 7.32:
But I AM troubled by the weird red text mentioning "MONGOOSE" always occurring the millisecond before my Lua code runs... anyone know why it's ALWAYS there?
It’s a fix they did in 7.32. No worries.
As for the echo remaining silent, open l_*.lua and set devmode variable to 1, then reload luup. It will be verbose during logging, posting the entire sh command. You could try to capture it and run directly via ssh, to see the complete response.
-
This post is deleted!
-
Vera beta, not VeraAlexa I assume?
So glad I stopped with it! There's so much I should do with OpenLuup but I lack both the imagination and the skill, but thanks to all on here, have a rock solid system!
C
-
LibraSunreplied to therealdb on Apr 15, 2021, 2:27 PM last edited by LibraSun Apr 15, 2021, 10:28 AM
@therealdb Has the 'runroutine' action been deprecated?
I just tried sending:
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", "RunRoutine", {RoutineName="Time for Cooking", GroupZones="Living Room"}, 345)
and got back this error:
ERROR: unknown command "automation:Time for Cooking"!
...along with all the possible valid options...
/storage/alexa/alexa_remote_control_plain.sh [-d <device>|ALL] -e <pause|play|next|prev|fwd|rwd|shuffle|repeat|vol:<0-100>> | -b [list|<"AA:BB:CC:DD:EE:FF">] | -q | -n | -r <"station name"|stationid> | -s <trackID|'Artist' 'Album'> | -t <ASIN> | -u <seedID> | -v <queueID> | -w <playlistId> | -a | -m <multiroom_device> [device_1 .. device_X] | -lastalexa | -l | -h -e : run command, additional SEQUENCECMDs: weather,traffic,flashbriefing,goodmorning,singasong,tellstory, speak:'<text>',sound:<soundeffect_name>, textcommand:'<anything you would otherwise say to Alexa>' -b : connect/disconnect/list bluetooth device -q : query queue -n : query notifications -r : play tunein radio -s : play library track/library album -t : play Prime playlist -u : play Prime station -v : play Prime historical queue -w : play library playlist -a : list available devices -m : delete multiroom and/or create new multiroom containing devices -lastalexa : print serial number that received the last voice command -login : Logs in, without further command -l : logoff -h : help
In brief, I see no reference (except in the ReadMe back at GitHub) to the 'RunRoutine' action, neither does trying to execute a routine through the 'textcommand' method. Any suggestions?
-
@librasun routine is a shortcut for -e automation:'ABC'.
In my experience, no space will work better, and sometimes you'll have to replace with _. ie 'Time_for_Cooking'
I'm using routines daily, to trigger things (ie, when the alarm is off, when we are going to bed to read my calendar, weather, and house status via a virtual device on HA-bridge, etc) and it's working no problem since day 1.
-
I'll gladly give that a whirl, thanks again. Sorry to always take up your time with such mundane things like this!!
-
Sadly, not a single time has either version ("RunRoutine" or "-e automation:") of this construct worked. It always, always claims it's an unknown command (as I shared earlier). I've used precisely the syntax from the docs, and this thread, and only those. Makes me wonder what the heck is going on.
About to resume giving up. My only hope at this juncture was to have Vera kick off an Alexa routine. She can speak, start (non-routine) commands, make music, give the weather, etc. But not this one thing. Argh.
-
Here ya go:
device #345 DebugMode 1 BinPath /storage/alexa Username xxxxxxxxxxxx Password xxxxxxxxxxxx DefaultEcho Living Room DefaultVolume 50 AnnouncementVolume 50 Language en-us AlexaHost pitangui.amazon.com AmazonHost amazon.com UseAnnoucements 0 DefaultBreak 3 OneTimePassCode CommFailure 0 CurrentVersion 0.92 LatestResponse ERROR: unknown command "automation:Time_for_Cooking"! /storage/alexa/alexa_remote_control_plain.sh [-d Configured 1
-
@catmanv2 said in Vera Alexa Plugin 7.32:
Oddly there is a bugle_03 and that doesn't work either
Nor 01 or 02 and they are in exactly the same format.C
Check out the part of this documentation that describes:
"Unfortunately, you have to try out the possible sound library entries . Of the four possible trumpet sounds, only the one shown above works, for example. You can see what sounds there are when you add "tones" to a routine." -
@therealdb somehow, on my own, I unearthed an update to
alexa_remote_control_plain.sh
(v0.17c -- I had been using v0.17a (now safely backed up!) until today), and it seems one step closer to honoring theRunRoutine
verb. At least it doesn't throw errors in the Log or in the Variables section. Still total silence, though!Here's how it looks in the LuaUPnP log:
08 04/15/21 18:31:59.634 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunLua <0x6e6ec520> 08 04/15/21 18:31:59.634 JobHandler_LuaUPnP::HandleActionRequest argument Code=luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", "RunRoutine", {RoutineName="Time for Cooking", GroupZones="Living Room"}, 345) <0x6e6ec520> 08 04/15/21 18:31:59.635 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=0 <0x6e6ec520> 08 04/15/21 18:31:59.635 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x6e6ec520> 08 04/15/21 18:31:59.635 JobHandler_LuaUPnP::HandleActionRequest argument action=RunLua <0x6e6ec520> 08 04/15/21 18:31:59.635 JobHandler_LuaUPnP::HandleActionRequest argument _r=1618529519635 <0x6e6ec520> 08 04/15/21 18:31:59.636 JobHandler_LuaUPnP::HandleActionRequest device: 345 service: urn:bochicchio-com:serviceId:VeraAlexa1 action: RunRoutine <0x6e6ec520> 08 04/15/21 18:31:59.636 JobHandler_LuaUPnP::HandleActionRequest argument GroupZones=Living Room <0x6e6ec520> 08 04/15/21 18:31:59.636 JobHandler_LuaUPnP::HandleActionRequest argument RoutineName=Time for Cooking <0x6e6ec520> 50 04/15/21 18:31:59.638 luup_log:345: VeraAlexa[0.92@345](setVar@126):setVar("urn:bochicchio-com:serviceId:VeraAlexa1","OneTimePassCode","",345) old value "" <0x6e6ec520> 50 04/15/21 18:31:59.638 luup_log:345: VeraAlexa[0.92@345](runRoutine@348):Executing command [runRoutine]: "-e automation:\"Time for Cooking\" -d \"Living Room\"" <0x6e6ec520>
Should I uninstall the plug-in and re-install it from scratch from your GitHub repo? I'm assuming you keep updating it based on new releases, and now I'm worried that simply pasting the contents of v0.17c into the existing
.sh
file on Vera may not have been the best approach. (Seemed smart at the time.)EDIT: It wasn't a smart idea, since everything stopped working (i.e. no Alexa commands would do anything any more), so I swapped back the v0.17a version of the
.sh
file on Vera.