openweather plugin ?

[CatmanV2]

@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]

@pabla I have mfa and it’s working great for me, but it need the oathtool.

[therealdb]

@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.

[Pabla]

@therealdb oh so the plugin wont work for me on Vera if I have MFA enabled?

[CatmanV2]

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 off

C

[LibraSun]

@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.

[CatmanV2]

@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

[therealdb]

@catmanv2 well, it’s using a different endpoint, so it could be impacted. I’ll take a deeper look tomorrow.

[LibraSun]

@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
// where 366 represents your Vera Alexa plug-in device_num

devArray := 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]

@therealdb

Really appreciate it!

C