Alexa TTS is sloooooooow
-
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 receivedAnother one or two manual resets of
Configuredlater, I finally get the expected idle phrase inLatestResponse:no alexa command receivedSo 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:VeraAlexa1This 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.
-
One day I'll reminisce about fixed-length fields in text files on old Applesoft DOS 3.3 floppy disks, wherein a single out-of-place comma could render the entire "database" unusable.
So yeah, I watch for that kinda stuff. That's why my default had been "Living Room" all this time (and I never thought to change that until this morning...glad I did!). -
Guys, Just something to watch out for coming up with your Alexa devices:
Amazon devices will soon automatically share your Internet with neighbors
Amazon's experimental wireless mesh networking turns users into guinea pigs.
-
therealdbreplied to LibraSun on May 30, 2021, 6:04 AM last edited by therealdb May 30, 2021, 2:09 AM
@librasun glad you’ve solved it. Sorry to be late to this party, but a combination of week-end and different time zones made is to blame.
I never thought of quotes, but it makes sense. My contribution to that is minimal, since we’re using an external bash script to do the work. I could add some warnings in our readme, but you’ll depend on something external. All that said, I have devices with quotes and I’ve never used as targets, and my VeraAlexa is still working…
-
@rafale77 said in Alexa TTS is sloooooooow:
Guys, Just something to watch out for coming up with your Alexa devices:
Amazon devices will soon automatically share your Internet with neighbors
Amazon's experimental wireless mesh networking turns users into guinea pigs.
Thanks. Not a hope in that working round here, but I'll be turning it off anyway.
C
-
Hmmm not a setting over here in Rightpondia....
C
-
Glad to hear! I am finding it quite bold that they are pushing this enabled this by default. Also it is not quite ready yet as they will be pushing the firmware updates. Just wanted to make sure you are aware.
31/35