Alexa guard via Vera-Alexa and spoken command support
-
Yep same here. I really don't want to enable MFA on my Amazon account. Given this was working earlier I guess it's a change that could be reverted (although I didn't save the last script!)
Oh and I'm not getting a Captcha challenge on accessing the Amazon host on Firefox
C
-
Yep same here. I really don't want to enable MFA on my Amazon account. Given this was working earlier I guess it's a change that could be reverted (although I didn't save the last script!)
Oh and I'm not getting a Captcha challenge on accessing the Amazon host on Firefox
C
-
In case anyone's keeping score (on what works and what doesn't), I've always used this setup:
Vera Plus
Control from MSR via Lua commands
No MFA on Amazon account
Chrome browser in Windows 10
Never disabled Javascript
"UseAnnouncements" = 0
Primary echo device is a Sonos Beam with built-in Alexaand got these results in each version:
0.92 = speak/say, weather, tune in all good, but NO routine (error)
0.94 = runRoutine OK but NO speak/say, weather, tune in (no errors in Log)
0.95 = same as 0.94 (i.e. silence despite clear signs plug-in is trying to produce output) -
Same here I keep getting
50 04/27/21 10:32:06.865 luup_log:952: VeraAlexa[0.92@952](@279):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." <0x6ce0c520>
Even though I have tried getting a cookie file multiple times, oddly enough even though I used the Github files from today my plugin still show 0.92
@pabla it’s casual, since I’ve not really changed anything regarding cookies. It will trigger a captcha from time to time, based on Amazon’s algorithm to detect logins. It usually will auto fix after a couple of days, but MFA is a better strategy long term.
-
@pabla it’s casual, since I’ve not really changed anything regarding cookies. It will trigger a captcha from time to time, based on Amazon’s algorithm to detect logins. It usually will auto fix after a couple of days, but MFA is a better strategy long term.
@therealdb I use MFA with my account
-
@pabla it’s casual, since I’ve not really changed anything regarding cookies. It will trigger a captcha from time to time, based on Amazon’s algorithm to detect logins. It usually will auto fix after a couple of days, but MFA is a better strategy long term.
@therealdb said in Alexa guard via Vera-Alexa and spoken command support:
@pabla it’s casual, since I’ve not really changed anything regarding cookies. It will trigger a captcha from time to time, based on Amazon’s algorithm to detect logins. It usually will auto fix after a couple of days, but MFA is a better strategy long term.
I've never had it fail to be repaired by replacing the cookie
C
-
@therealdb I use MFA with my account
-
In case anyone's keeping score (on what works and what doesn't), I've always used this setup:
Vera Plus
Control from MSR via Lua commands
No MFA on Amazon account
Chrome browser in Windows 10
Never disabled Javascript
"UseAnnouncements" = 0
Primary echo device is a Sonos Beam with built-in Alexaand got these results in each version:
0.92 = speak/say, weather, tune in all good, but NO routine (error)
0.94 = runRoutine OK but NO speak/say, weather, tune in (no errors in Log)
0.95 = same as 0.94 (i.e. silence despite clear signs plug-in is trying to produce output) -
@therealdb oh so the plugin wont work for me on Vera if I have MFA enabled?
-
I also appear to have a new VeraAlexa instance in 'No Room' with the wrong settings and that's the instance that's getting the Login failure as its last response. The original instance has the last speak response from earlier in the day.
<edit>
Deleted the new instance and TTS is restored with a new cookie and MFA turned offC
-
@librasun ok, so announcement set to 0. Why?
Could you please try with it set to 1? If it’s working, I have a plan to follow.@therealdb said in Alexa guard via Vera-Alexa and spoken command support:
@librasun ok, so announcement set to 0. Why?
Could you please try with it set to 1? If it’s working, I have a plan to follow.Answer: Never had any reason to change it from "0" to "1" is my best answer. I have tried it with "UseAnnouncements" set to "1" with no improvement, but will do so again now and edit this post accordingly.
UPDATE: Made no difference.
-
@therealdb said in Alexa guard via Vera-Alexa and spoken command support:
@librasun ok, so announcement set to 0. Why?
Could you please try with it set to 1? If it’s working, I have a plan to follow.Answer: Never had any reason to change it from "0" to "1" is my best answer. I have tried it with "UseAnnouncements" set to "1" with no improvement, but will do so again now and edit this post accordingly.
UPDATE: Made no difference.
@librasun said in Alexa guard via Vera-Alexa and spoken command support:
@therealdb said in Alexa guard via Vera-Alexa and spoken command support:
@librasun ok, so announcement set to 0. Why?
Could you please try with it set to 1? If it’s working, I have a plan to follow.Answer: Never had any reason to change it from "0" to "1" is my best answer. I have tried it with "UseAnnouncements" set to "1" with no improvement, but will do so again now and edit this post accordingly.
I guess it's only really useful if you want your 'Everywhere' TTS to be in sync.
C
-
@librasun said in Alexa guard via Vera-Alexa and spoken command support:
@therealdb said in Alexa guard via Vera-Alexa and spoken command support:
@librasun ok, so announcement set to 0. Why?
Could you please try with it set to 1? If it’s working, I have a plan to follow.Answer: Never had any reason to change it from "0" to "1" is my best answer. I have tried it with "UseAnnouncements" set to "1" with no improvement, but will do so again now and edit this post accordingly.
I guess it's only really useful if you want your 'Everywhere' TTS to be in sync.
C
-
I could in theory look at the device.json and use it to construct something, like a Devices variable or similar. Not sure how often this is updated, and I'm not sure if you could find something useful inside. For example, I'm parsing it to detect the alarms. I'm seeing an "online" property that might be useful to you.
@therealdb said in Alexa guard via Vera-Alexa and spoken command support:
like a Devices variable
Well done! And for anyone seeking to parse the comma-delimited list of Alexa devices that
Devices
returns, here's a stab I took using MSR Expressions which you may find helpful:devStatus
:= getEntity( "vera>device_366" ).attributes.x_vera_svc_bochicchio_com_VeraAlexa1.Devices
// where366
represents your Vera Alexa plug-in device_numdevArray
:= each i in split( devStatus, "\n" ) : split( i, "," )
// returns an array of 4-element arrays, one for each device...
// [dev_name, online_status, dev_id, dev_features] -
@catmanv2 well, it’s using a different endpoint, so it could be impacted. I’ll take a deeper look tomorrow.