openweather plugin ?

[LibraSun]

@therealdb said in Alexa guard via Vera-Alexa and spoken command support:

I'm seeing an "online" property that might be useful to you.

Heck, even if it just updates daily that might suffice. I just hate when I go to speak to an Alexa device and realize that it's been "offline" for days, and I've never come up with a suitable warning notification for that condition.

Thanks!

[rafale77]

Just curious, do you know why your alexa device went offline? When I had some, it was pretty rare and when it did happen, I recall that it would be because of an automated firmware update which failed to reboot the device or because of wifi/cloud issues. They were pretty rare (still one of the reasons why I hate the cloud for home automation with a passion) but was wondering if and why you had a higher frequency of these.

[LibraSun]

@rafale77 said in Alexa guard via Vera-Alexa and spoken command support:

Just curious, do you know why your alexa device went offline?

An alexa might drop out maybe four times a year or so. My hometown has a LOT of power outages, so I always assumed that was part of it. Other times, I'd just notice an Echo Dot sitting there with its light spinning. But the most recent occasion involved an accessory (that ironically includes a battery backup for a Dot, with built-in speaker) whose power light continued to glow even after it stopped providing current to the Dot.

So it's not one particular thing happening, it's rarely the same device, and it's never under my control. The reason I don't immediately notice the drop-out is that I'm never out of earshot of at least 3 Alexa devices in my small home.

[therealdb]

@librasun I don’t have children in this a plugin, so if you’re able to parse a json/text, I could save it in a variable for sure. Maybe something like this

DeviceName,online,volume
DeviceName,online,volume

Or similar.

[LibraSun]

@therealdb said in Alexa guard via Vera-Alexa and spoken command support:

@librasun I don’t have children in this a plugin, so if you’re able to parse a json/text, I could save it in a variable like DeviceName,online,volume

Yes, that's more than sufficient for my needs, since MSR can store HTTP replies and parse JSON objects with ease. Meraviglioso!

Of course, I'm sitting on my hands waiting for the next revision of Vera Alexa to come out, in hopes that the plug-in's basic functionality also returns. Version 0.94 only succeeds with the RunRoutine command, while all else is silent (the mirror opposite of 0.92).

I know you're very busy with other things, so no hurry either way!

[CatmanV2]

My dots only go offline when there are wifi issues or, I think, a couple have crashed maybe twice total since I started using them about 3 years back.

AltUI says I'm on 1.0 and speech is fine, no routines.

C

[therealdb]

@librasun it's done on my dev branch, but I'll need a more couple days to look at your problem. I'll probably release it later this week. it's not json based, but a simple comma-separated list, as I've anticipated before.

[therealdb]

0.95 is on GitHub. I've managed to fix your problems @LibraSun @CatmanV2 . Give it a try.

I've also added a new UpdateDevices action, that's updating a Devices variable. It's also updated every time a new action is executed. @LibraSun try it and let me know!

[LibraSun]

@therealdb said in Alexa guard via Vera-Alexa and spoken command support:

0.95 is on GitHub. I've managed to fix your problems

Ooh, exciting! I'll get right on that and report back ASAP.

(Planning to d/l the ZIP, unzip it, and drop the relevant files into Vera > Dev Apps > Luup Files > restart > Ctrl-F5 refresh > leave "Configured" = 1, "Debug" = 0, "Announcements" = 0 and then run my test suite from MSR (via Lua commands).)

THANKS, DB!

QUICK FEEDBACK: Did the above and so far, no improvement.

For instance, I send this to Vera from MSR:
"luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e weather -d 'Living Room'"}, 366)"

and get this response with no errors:

"sending cmd:weather to dev:Living Room type:A15ERDAKK5HQQG serial:eb48978706f5459f890ef0ec5aa9fce9 customerid:A3SL3Z0HELH3YG"

but still no audible sound. Will investigate, and likely go the "Configured=0" route to prompt any updates needing doing. (Did that, no improvement. Captured logs and sent to DB.)

[therealdb]

@librasun I've not tested RunCommand specifically. Routines and TTS are working for me. Off to test commands...

[CatmanV2]

Thanks. Just DL and unzip into the VeraAlexa folder, yes? Or Via AltApp store?

Cheers

C

[therealdb]

@therealdb

@catmanv2 said in Alexa guard via Vera-Alexa and spoken command support:

hanks. Just DL and unzip into the VeraAlexa folder, yes? Or Via AltApp store?

It should be the same.

I've tested RunCommand and it's working for me.

[CatmanV2]

Updated from GitHub Master. Have lose all TTS and recreating the .alexa.cookie does not resolve

C

[Pabla]

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

[CatmanV2]

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

[Pabla]

@catmanv2 Try disabling Javascript

[CatmanV2]

@pabla said in Alexa guard via Vera-Alexa and spoken command support:

@catmanv2 Try disabling Javascript

No different

C

[LibraSun]

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 Alexa

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

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

@therealdb I use MFA with my account