Alexa TTS is sloooooooow
-
@therealdb said in Alexa TTS is sloooooooow:
@catmanv2 yep, same for me yesterday. Today it seems to be back to normal latency.
Mine's been like this for some time. Just checking again and the same 10 second delay somewhere
C
-
try to update the .sh script. They released a new version yesterday, and they specifically changed the TTS part. It's working good for me, even if they removed announcements, it's still working with announcements for me
-
@therealdb said in Alexa TTS is sloooooooow:
try to update the .sh script. They released a new version yesterday, and they specifically changed the TTS part. It's working good for me, even if they removed announcements, it's still working with announcements for me
Do you have a link perchance? I can't find anything newer than Jan..
Cheers
C
-
-
@therealdb said in Alexa TTS is sloooooooow:
@catmanv2 https://github.com/thorsten-gehrig/alexa-remote-control
My thanks, as ever
C
-
Announcements still work fine, but still 10 second delay <shrug>
C
-
And as anticipated, my system remains completely silent. I did update the .SH file just now to v.0.18, but no change.
However, I am noticing some (potential) weirdness in Vera Log which perhaps are not anomalies, but I'm pasting below just in case. I just leave VeraAlexa in 'Debug' mode all the time now. The command I had issued (from MSR) was:
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e textcommand:'tune in wwoz' -d 'Living Room'"}, 366)
Log contained the following, and I'm wondering why, for starters, most (not all) of my Echo devices are listed twice? why the response from .SH is ""? why the
setVar
/Devices
line references a device other thanLiving Room
? whyLatestResponse
appears empty? etc.:08 05/29/21 9:40:44.577 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunLua <0x70dc2520> 08 05/29/21 9:40:44.577 JobHandler_LuaUPnP::HandleActionRequest argument Code=luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e textcommand:'tune in wwoz' -d 'Living Room'"}, 366) <0x70dc2520> 08 05/29/21 9:40:44.577 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=0 <0x70dc2520> 08 05/29/21 9:40:44.577 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x70dc2520> 08 05/29/21 9:40:44.578 JobHandler_LuaUPnP::HandleActionRequest argument action=RunLua <0x70dc2520> 08 05/29/21 9:40:44.578 JobHandler_LuaUPnP::HandleActionRequest argument _r=1622299244559 <0x70dc2520> 08 05/29/21 9:40:44.578 JobHandler_LuaUPnP::HandleActionRequest device: 366 service: urn:bochicchio-com:serviceId:VeraAlexa1 action: RunCommand <0x70dc2520> 08 05/29/21 9:40:44.579 JobHandler_LuaUPnP::HandleActionRequest argument Command=-e textcommand:'tune in wwoz' -d 'Living Room' <0x70dc2520> 50 05/29/21 9:40:44.580 luup_log:366: VeraAlexa[0.97@366](setVar@120):setVar("urn:bochicchio-com:serviceId:VeraAlexa1","OneTimePassCode","",366) old value "" <0x70dc2520> 50 05/29/21 9:40:44.581 luup_log:366: VeraAlexa[0.97@366](runCommand@395):Executing command [runCommand]: "-e textcommand:'tune in wwoz' -d 'Living Room'" <0x70dc2520> 50 05/29/21 9:40:44.601 luup_log:366: VeraAlexa[0.97@366](setVar@120):setVar("urn:micasaverde-com:serviceId:HaDevice1","CommFailure","0",366) old value "0" <0x70dc2520> 50 05/29/21 9:40:44.602 luup_log:366: VeraAlexa[0.97@366](setVar@120):setVar("urn:bochicchio-com:serviceId:VeraAlexa1","LatestResponse","",366) old value "" <0x70dc2520> 50 05/29/21 9:40:44.603 luup_log:366: VeraAlexa[0.97@366](@308):Response from Alexa.sh: "" <0x70dc2520> 50 05/29/21 9:40:44.622 luup_log:366: VeraAlexa[0.97@366](setVar@120):setVar("urn:bochicchio-com:serviceId:VeraAlexa1","Devices","Anne's Alexa Apps, false,2f69293cc2c749f6854ad6c5b41aef43,MSHOP\ Kitchen, true,F00718703203T4,ECHO\ Yoga Room, true,90LF1071750H8V,ECHO\ Hall Bathroom, true,90LF1071750H7N,ECHO\ Everywhere, true,56c846877e416eaa3425d163619011,WHA\ Downstairs, false,095239c8124c46834ded97b5c947b7,THIRD_PARTY_AVS_MEDIA_DISPLAY\ Master Bedroom, true,70RR138143018W,ROOK\ Workshop, true,90LF1071750H4G,ECHO\ Guest Room, false,90U50991541T31,ECHO\ Alexa App for PC, false,0CE90F27F69FFF703570DE6C20E7BA,REAVER\ Fire Tablet, true,W0TC039353F2SX,TABLET\ Libra's Sonos Beam, true,89f9dcc0ab4085bcb59494f81c3726,THIRD_PARTY_AVS_SONOS_BOOTLEG\ Living Room, true,48978706f5459f890ef0ec5aa9fce9,THIRD_PARTY_AVS_MEDIA_DISPLAY\ Libra's Ezlo Voi, false,eea63a85e2419498871004faca7e4d,UNKNOWN\ This Device, true,60b747dc4ce292626be49b7c3d41,VOX\ Libra's Alexa Apps, false,56FEC32487,AMAZONMOBILEMUSIC_ANDROID\ ",366) old value "Anne's Alexa Apps, false,69293cc2c749f6854ad6c5b41aef43,MSHOP\ Kitchen, true,F00718703203T4,ECHO\ Yoga Room, true,90LF1071750H8V,ECHO\ Hall Bathroom, true,90LF1071750H7N,ECHO\ Everywhere, true,56c846877e416eaa3425d163619011,WHA\ Downstairs, false,095239c8124c46834ded97b5c947b7,THIRD_PARTY_AVS_MEDIA_DISPLAY\ Master Bedroom, true,70RR138143018W,ROOK\ Workshop, true,90LF1071750H4G,ECHO\ Guest Room, false,90U50991541T31,ECHO\ Alexa App for PC, false,0CE90F27F69FFF703570DE6C20E7BA,REAVER\ Fire Tablet, true,W0TC039353F2SX,TABLET\ Libra's Sonos Beam, true,89f9dcc0ab4085bcb59494f81c3726,THIRD_PARTY_AVS_SONOS_BOOTLEG\ Living Room, true,48978706f5459f890ef0ec5aa9fce9,THIRD_PARTY_AVS_MEDIA_DISPLAY\ Libra's Ezlo Voi, false,eea63ae2419498871004faca7e4d,UNKNOWN\ This Device, true,60b747dc4ce292626be49b7c3d41,VOX\ Libra's Alexa Apps, false,56FEC32487,AMAZONMOBILEMUSIC_ANDROID\ " <0x70dc2520> 08 05/29/21 9:40:58.658 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunLua <0x6d5c2520> 08 05/29/21 9:40:58.658 JobHandler_LuaUPnP::HandleActionRequest argument Code=luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e weather -d 'Living Room'"}, 366) <0x6d5c2520> 08 05/29/21 9:40:58.658 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=0 <0x6d5c2520> 08 05/29/21 9:40:58.659 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x6d5c2520> 08 05/29/21 9:40:58.659 JobHandler_LuaUPnP::HandleActionRequest argument action=RunLua <0x6d5c2520> 08 05/29/21 9:40:58.659 JobHandler_LuaUPnP::HandleActionRequest argument _r=1622299258640 <0x6d5c2520> 08 05/29/21 9:40:58.660 JobHandler_LuaUPnP::HandleActionRequest device: 366 service: urn:bochicchio-com:serviceId:VeraAlexa1 action: RunCommand <0x6d5c2520> 08 05/29/21 9:40:58.660 JobHandler_LuaUPnP::HandleActionRequest argument Command=-e weather -d 'Living Room' <0x6d5c2520> 50 05/29/21 9:40:58.661 luup_log:366: VeraAlexa[0.97@366](setVar@120):setVar("urn:bochicchio-com:serviceId:VeraAlexa1","OneTimePassCode","",366) old value "" <0x6d5c2520> 50 05/29/21 9:40:58.662 luup_log:366: VeraAlexa[0.97@366](runCommand@395):Executing command [runCommand]: "-e weather -d 'Living Room'" <0x6d5c2520>
NOTE: All names and S/N's redacted for privacy (so may appear inconsistent in listing)
-
Hmmm, I have debug set to one and my log looks nothing like that....
This is the LuaUPnP.log yes?
C
-
@catmanv2 said in Alexa TTS is sloooooooow:
This is the LuaUPnP.log yes?
Yes. I get a very verbose response set like that in Vera's LuaUPnP Log every time I attempt one of the Lua commands I use for testing. Some worked with previous revisions, others not, but right now ... literally nothing works for me.
I'm wondering if maybe I have too many Alexa devices defined in my account... or something else unique to "me" that's causing VeraAlexa to choke.
Whenever I update any component of the VeraAlexa plug-in (whether through WinSCP or by dragging files into App > Develop), I always set "Configured" back to
0
and restart Vera, so things have a chance to settle. The cookie is safely there, and "Configured" always sets to1
without any trouble.It's as if the plug-in wants to work, but simply doesn't, for me.
-
@librasun are you on Vera or OpenLuup?
What's in your .alexa.devicelist.all? If you've got duplicate entries it's probably worth deleting it and letting it re-create.
I've just realised my 'new' Echo is not listed, but it's in the guess bedroom so doesn't get used.
C
-
To answer your question, I inspected the contents of my .alexa.devicelist.json file (I see no 'all' file like you mentioned), and found -- after putting it through a JSON Pretty Print converter and filtering for accountName -- just a single copy of each device on my account.
Egads, though, the file is 931 lines long, lol!
If you're suggesting I delete that file, I'm game, but am generally loath to take stabs in the dark like that until I have more data.
-
AFAIK you should have:
.alexa.devicelist.txt
.alexa.devicelist.all
.alexa.cookie
.alexa.devicelist.jsonI think the lack of some or more of these could be part of your issue. Are you on Vera still? I forget
Totally get what you mean about deleting stuff. I tend to rename ;). My understanding is they should be created automagically.
C
-
Yep, am still on Vera Plus. I'll do the rename you suggest IF I can find the .all file in question. Weird that I haven't seen it yet in WinSCP (which is definitely showing me any hidden/system files).
When I do a search for alexa starting at Vera's root directory, here are the results (am I seeing duplicates?):
/etc/cmh-ludl/L_AmazonAlexaHelper.lua.lzo /storage/cmh-ludl/L_AmazonAlexaHelper.lua.lzo /etc/cmh-ludl/alexa.png.lzo /etc/cmh-ludl/D_VeraAlexa1.xml.lzo /etc/cmh-ludl/I_VeraAlexa1.xml.lzo /etc/cmh-ludl/L_VeraAlexa1.lua.lzo /etc/cmh-ludl/S_VeraAlexa1.xml.lzo /storage/cmh-ludl/alexa.png.lzo /storage/cmh-ludl/D_VeraAlexa1.xml.lzo /storage/cmh-ludl/I_VeraAlexa1.xml.lzo /storage/cmh-ludl/L_VeraAlexa1.lua.lzo /storage/cmh-ludl/S_VeraAlexa1.xml.lzo /storage/alexa/.alexa.cookie /storage/alexa/.alexa.devicelist.json /storage/alexa/alexa_remote_control.sh.old /storage/alexa/alexa_remote_control.sh /storage/alexa/.alexa.cmd /storage/alexa/.alexa.volume.4256c846877e416eaa3425d163619011 /storage/alexa/.alexa.volume.90F00718703203T4 /storage/alexa/.alexa.volume.d889f9dcc0ab4085bcb59494f81c3726 /storage/alexa/.alexa.volume.eb48978706f5459f890ef0ec5aa9fce9 /storage/alexa/.alexa.volume.G070RR138143018W /storage/alexa/.alexa.volume.G090LF1071750H4G /storage/alexa/.alexa.volume.G090LF1071750H7N /storage/alexa/.alexa.volume.G090LF1071750H8V /storage/alexa/.alexa.volume.G0W0TC039353F2SX
-
I'm going the nuclear option now... deleting 'Alexa' device from Vera, removing ALL "Alexa" files from Vera (except the two belonging to "Helper"), rebooting, installing fresh VeraAlexa from Github repo, restarting Luup, creating device, restarting/refreshing, logging into Alexa.Amazon.com, configuring. turning on Debug, restarting/refreshing, etc., etc.
Will report back momentarily...
Took some real calisthenics to get the Cookie file again, but it's back, and VeraAlexa is now rebuilding my Devices list.
Modifying my MSR test suite to reflect newly assigned device number... then will run some test Lua...
After silent result, I immediately spotted this in Vera's log:
JobHandler_LuaUPnP::HandleActionRequest can't handle service: urn:bochicchio-com:serviceId:VeraAlexa1 <0x70376520>
Despite "Configured" insisting itself to
1
, and the cookie file (and devices.json) being present, I continue to see this inLatestResponse
:cookie does not exist. logging in ... device list does not exist. downloading ... no alexa command received
Another one or two manual resets of
Configured
later, I finally get the expected idle phrase inLatestResponse
:no alexa command received
So am resuming tests. First one out of the chute gives the same error condition in Log:
JobHandler_LuaUPnP::HandleActionRequest can't handle service: urn:bochicchio-com:serviceId:VeraAlexa1
This is the point I normally go jump off a tall bridge. Bye!
-
OK, well that's a problem :(. (The log not the bridge)
Perhaps our guru on Alexa TTS can assist. I'm probably not going to be much help as I'm OpenLuup....
C
-
I've just come back from the dead, in order to report some modest successes since my past post.
- I switched my "Default Echo" from "Living Room" to "Libra's Sonos Beam" (same device!!) and she finally spoke.
- Further testing revealed that I can get other devices to speak and react to commands, so that's promising. This points to somehow my "Living Room" (the previously working device in 0.92) had become unwelcome by 0.97 and 0.98.
- Now, for some reason -- maybe because I tested some "informal phrasing" -- Alexa answers me casually with "Aye, aye, captain!"
[That was unexpected yet humorous!]
So, as it stands, pretty much my entire checklist of test routines appears to be working, and I am happy to rejoin the living.
Thanks for the moral support from everyone. Glad I don't have to give up entirely on VeraAlexa!!
-
@therealdb after all of today's failures and successes with VeraAlexa, I find this one Lua command does not produce the desired results (namely, tuning in radio station WWOZ through "Tune In"), as Alexa normally would when these words are spoken aloud:
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e textcommand:'tune in wwoz' -d 'Sonos Beam'"}, 370)
// alexa responds "I'm not sure what video you want"
Do you think I'm doing something wrong? Or is Tune In not compatible somehow with this plug-in?
Thanks for any suggestions!
EDIT: Think I've solved it, by adding the words "radio station" before the call letters:
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e textcommand:'tune in radio station wwoz' -d 'Sonos Beam'"}, 370)
//works, desired station plays
-
Can't get a multi-quote but:
- Apostrophes in device names. That sounds like a bad idea. No idea how the system is going to react to that.
- Aye aye captain: I want this. How can I make it happen
C
-
You and I think alike; I since took pains to eliminate any apostrophes from my Device Names (both in the Alexa app, officially, as well as very carefully in the .JSON file and in the plug-in itself). Pretty sure that was a problem. I even attempted to escape the apostrophe (
\'
) but VeraAlexa didn't respond. As a matter of fact, when unable to decipher the assigned device, VeraAlexa seems to select another one (in my case, "Kitchen", the last one used during testing) as the default. Kinda unexpected.@therealdb is this something that the plug-in needs to contend with going forward? After all, Amazon lets you name devices however you want, subject to few constraints, and often without the user's input. For example, "Libra's Ezlo Voi" was created not directly by me, but by my Ezlo Plus / VeraMobile app / who-knows-what service.
17/35