You suggest the plug-in, I will make the video
How about using Virtual outdoor temperature plugin?
You would get the variable you need like below, you need to add the correct seviceId and variable name and the device number. these can be found on the advanced-variable section, by clicking edit or if your browser allows you can hoover the mouse over the variable.
local varname = luup.variable_get("the sevice id of the variable", "thename of the variable", 666)
local text = "The temp is " .. varname .. " c"
http://wiki.micasaverde.com/index.php/Luup_Lua_extensions#function:_variable_get
The text at top show the serviceId and variable name.
HI,
How did you manage to solve your issue?
I face the same and as soon as I install the cookie file in Vera after rebooting Vera it will vanish.
Hi,
Sorry for late reply
Yes I did. Updating cookie file helped. Make sure that you clear all history on your Firefox (this is web browser I am using for creating cookie file anyway)
Every few weeks I have to update the cookie file anyway as plugin stops working. I am getting the SMS message Amazon security alert. Then I know that I need to update the file after the update everything works again.
If you have any questions I am happy to help.
Regards,
AJ
Do you have stable solution? I can not update and upload files for customers every few weeks.
The only reliable solution is to use MFA, as shown here: GitHub - thorsten-gehrig/alexa-remote-control: control Amazon Alexa from command Line (set volume, select station from tunein or pandora)
Unfortunately oathtool is not available as a package on a Vera system, but it is on a proper linux distro. I’m successfully running it on ubuntu.
1 Like
Hi, I way about to say @therealdb will be the best person to ask.
Hello, I would like to install jq on my Vera to be able to run routines and commands on Alexa as it is written in the github. I found several jq packages available on openwrt.org depending on the architecture of the device. So, does anybody know the one to use to install on Vera Plus ? It seems to use a MIPS processor but there are several ones and I don’t see any related to Vera or micasaverde brand devices. Thank you for your help.
I’m not sure what architecture is Vera’s one, but jq should be included into the upcoming 7.32 fw release, now in beta. the plug-in is already ready to use jq, if installed. I’ll probably offer a simpler way to install, via a flag/service action, for people not comfortable with ssh.
I have the basics working, but cannot figure out how to get announcements working. I don’t know how to install “jq” on the vera, perhaps that’s part of the issue. How do I get announcements working within vera?
I am using 7.31 and it’s not listed as an app in vera.
I tried to use different voices, and echo replies with “Sorry I’m having trouble accessing your Simon says NA skill right now”
luup.call_action(“urn:bochicchio-com:serviceId:VeraAlexa1”,“Say”,
{Text=‘Hello from Vera Alexa’,
Volume=50, GroupZones=“Kitchen”, Repeat = 3}, xxx)
Those features are only supported with Jq. It should be available with 7.32.
Thanks for your help. Everything seems to be working well. Now, I am looking at randomizing the replies given for certain tasks, as the family is tired of hearing “attention all residents, the garage door has been opened. No need to panic” 
1 Like
Hi
Thank you for the plugin and I was wonder if anyone has used Chrome to support the cookies file? If so do you have an easy way to find it?
Thanks
Hi @therealdb
Trying to install your plugin and have gotten as far as successfully creating the device. But I had a couple questions. What do I input for the variable “DefaultEcho”? Is that just the name for one of my echo devices in my Amazon account?
Also, I created a manually triggered scene and added your default TTS code. I changed the 666 to my device ID in vera, but what goes in GroupZones? Is that again the device name of one of the echos in my Amazon account? Right now if I run the scene it says the command is successfully sent, but I’m not hearing anything from my echo device.
Thanks!
Oath tool is not supported under Vera. I have it running on openluup for the very same reason.
Try to set debugmode to 1 and look at logs.
You are correct, this is the device name (or group) as reported by Alexa. It’s case sensitive.
Is Oath tool required for getting through MFA? I saw a note about using a URL and tasker to set a cookie. Is that an alternative? If so, how does that work?
(Sorry for all the questions.)
If you have One Time passcode via SMS enabled, cookie could be renewed this way.
Thanks to @Elcid, One Time Passcode are now supported. This makes easy to renew a cookie when dealing with 2-factory authentication (2FA). Amazon will send you a One Time Passcode via e-mail or SMS. You can use tasker/automate/whatever to send text with OTP to renew cookie with 2FA.
http://veraIP:3480/data_request?id=variableset&DeviceNum=666&serviceId=urn:bochicchio-com:serviceId:VeraAlexa1&Variable=OneTimePassCode&Value=OTPVALUE
(Taken from the readme).
I think the tasker/automate solution is probably the way to go for me. But I’ve never used either before. Can you explain in more detail how this works? Or point me to a URL that has a more general explanation?
Sorry again to bother you with questions. 