I will be back to add other features in the coming weeks. I’ll probably try to first implement a cookie backup strategy, then add the ability to execute any command. If anyone wants to beta-test this on openluup, just let me know.
that’s great. I have writtten an automate flow that will automatically forward the one time pass code to vera. The flow is not fully tested yet, as i am waiting for my cookie to expire. Once fully tested i will upload a copy to the automate community, and link to it here.
ok i have
installed jq
uploaded files to /etc/cmh-ludl/
created device
folder create by plugin called VeraAlexa
in that folder is the remote.sh script and i coppied the cookie file to that location.
sync’ed announcements for groups: tested on my 6 devices, it’s impressive
rich voice options, with the ability to pause, change emotions, etc
sounds (chimes, cars, dogs and much more)
I will incorporate these soon, as I’ll get a real benefit from them (ie: repeat announcements with one commands, instead of a queue). Unfortunately, this needs Jq, and it’s not offered in the plain text version.
Anyone running into this issue, every time I upload the new updated files from GitHub I lose TTS. Ive tried updating the cookie file, inputting a new OTP code and still can’t get TTS to work. Last time I uploaded the new files I had to create a new device to get Alexa to work, anyone recommend anything else?
50
02/22/20 10:14:27.532
luup_log:632: VeraAlexa(executeCommand@235): Response from Alexa.sh: “cookie does not exist. logging in … ERROR: Amazon Login was unsuccessful. Possibly you get a captcha login screen. Try logging in to https://alexa.amazon.ca with your browser. In your browser make sure to have all Amazon related cookies deleted and Javascript disabled! (For more information have a look at /storage/alexa/.alexa.login) To avoid issues with captcha, try using Multi-Factor Authentication. To do so, first set up Two-Step Verification on your Amazon account, then configure this script (or the environment) with your MFA secret. Support for Multi-Factor Authentication requires ‘oathtool’ to be installed.” <0x70837520>
Ouch. Let me test it again tomorrow. I should have time to release the new version with sync’ed announcements. If you can, please send some logs via PM.