directly with Vera and no subscription fee
I’ve discovered the Liftmaster/Chamberlain kits also works on Craftsman doors and an eg eBay it is cheaper than the Craftsman kit.
Look for 888LM wall control and 828LM gateway. Also availavle 825LM Light control module (Not supported by the plugin I believe)
A check every minute should be frequent enough to prevent timeouts from happening.
Very strange, is there anything I can do to help troubleshoot this? I dont have an internet connection at the moment (lesson learned, stay away from Comcast and go with Verizon) but let me know what I can do to help.
Not sure what you meant with the checking after an open or close action because the problem seems to occur after a long period of inactivity (perhaps the nightly lua reload?)
Actually, if the plugin does not want to work with the MyQ site (not opening or closing), a LUA reload will generally fix it (I have a luup reload scene just for that). It looks like the wait between authorization cycles may have to be shortened. I believe it’s set to 8 hours. Been to busy with other things to tinker with that.
macrho. You are my hero. Thanks for taking on this initiative. I was considering switching to the Linear Corp GD00Z so that I could run scenes with my garage doors. This keeps me from having to spend more money.
Now I just need to figure out how to make a scene with my alarm panel!
Thanks again!
I have both a garage door and gate connected to my gateway. I added device ID 49 to the list of definitions for GARAGE_DOOR_OPENER and added to test in the function inspectDevices. I now have control over both my garage door opener and the gate opener.
I am a bit concerned about the 90 seconds polling interval, Chamberlain may not like the frequent polling through their website. I did read in one of the posts a suggestion to increase polling after send and open/close command which seems to be a good compromise.
I would be nice to get some nicer logos to show the door/gate status similar to the Chamberlain website:
Congrates on the app.
This is awesome, thanks for your work on this!
I am having a small issue though. I usually try to open/close the doors from the mobile app and it seems like more often than not, it doesn’t work. I haven’t determined if the issue persists with the web interface as well because every time I’ve tried from the web interface, it has worked. After using the web interface, I can then use the mobile app as well, but then when I try again at a later time, it doesn’t work again (just has the spinning icon like it’s thinking, but it never does anything).
Any suggestions on how to troubleshoot this?
Thanks!
I’m trying to troubleshoot the issue I’ve been having where after a period of time the door status checks fail (and the plugin stops responding). I’ve tried BOFH’s suggestion to shorten the auth token time to 1 hour, and I see the token being refreshed. But again the door check has been stuck since 6:54 this morning.
A LUA reload will generally get things going again but that’s really not something I want to do every time I want to open/close my doors.
I’ve been looking at the LUA code and, as its like 15 years since I wrote my last piece of code, having a hard time trying to understand the logic.
What I dont quite understand is why the plugin would stop responding to open/close requests. I can understand the periodical check stopping because of whatever process kills off whatever timer but the moment I hit an open or close it should fire a new request to Liftmaster if my token is correct. Which seems to be the case as it keeps refreshing. I dont even get any of the errors back. I dont have access to the log file right this moment so I’ll dig into that when I get home but just wanted to pick the brains of more seasoned developers to understand the logic behind LUA.
Does anyone know where I can find the MyQ plugin for Vera???
it’s at the bottom of the first post in this thread
Lol…opps…forgot to login to see the attachment…thanks macrho 
@Macrho or BOFH
I hope you can help me out here as I’m way out of depth here.
I’ve been browsing the log files and found the following.
Every hour a security token update happens, as epected:
06 08/27/14 9:15:33.203 Device_Variable::m_szValue_set device: 76 service: urn:macrho-com:serviceId:MyQGateway1 variable: e[35;1mTimestampe[0m was: Wed 08:15 now: Wed 09:15 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2dfaf680>
50 08/27/14 9:15:33.240 luup_log:76: MyQ Gateway: Security token updated <0x2dfaf680>
Then at some point I see this error:
01 08/27/14 9:20:33.680 e[31;1mLuaInterface::CallFunction_Timer-5 function refreshDoors failed [string "module("L_MyQGateway_json", package.seeall)..."]:366: Unexpected character at Line 1 character 13: ] (93) when reading array ({ or [ or ' or " or number or boolean or null expected)
Context:
{"Devices":[],"ReturnCode":"-3333","ErrorMe
^e[0m <0x2dfaf680>
When that happens the Refreshdoors function starts to behave erratic. It either runs with the same error or it runs but only updates a single door (out of 2) but in reality it doesnt seem to be doing anything. Then I had a luapnp crash (did not hit save of reload):
e[7;36m2014-08-27 10:28:21 - LuaUPnP Terminated with Exit Code: 250e[1;00mAnd everything started working again.
I see that -3333 is a ‘login error’ but I cant quite place it as my internet connection was fine, it had just refrehsed the token minutes before so it seems the code is somewhat misleading as it actually does need a lua reload for things to start working again.
Any ideas?
[quote=“Vol, post:148, topic:180826”]I’m trying to troubleshoot the issue I’ve been having where after a period of time the door status checks fail (and the plugin stops responding). I’ve tried BOFH’s suggestion to shorten the auth token time to 1 hour, and I see the token being refreshed. But again the door check has been stuck since 6:54 this morning.
A LUA reload will generally get things going again but that’s really not something I want to do every time I want to open/close my doors.
I’ve been looking at the LUA code and, as its like 15 years since I wrote my last piece of code, having a hard time trying to understand the logic.
What I dont quite understand is why the plugin would stop responding to open/close requests. I can understand the periodical check stopping because of whatever process kills off whatever timer but the moment I hit an open or close it should fire a new request to Liftmaster if my token is correct. Which seems to be the case as it keeps refreshing. I dont even get any of the errors back. I dont have access to the log file right this moment so I’ll dig into that when I get home but just wanted to pick the brains of more seasoned developers to understand the logic behind LUA.[/quote]
Did anyone ever find an answer to the above issue? I have set this plugin up and am extremely grateful/excited about it. I’m using it with my assurelink but have the same periodic timeout issue as above. This is the first error message that I found in the log after the refresh stopped working:
[color=red]01 09/09/14 13:14:35.720 LuaInterface::CallFunction_Timer-5 function refreshDoors failed [string “module(“L_MyQGateway_json”,
package.seeall)…”]:366: Unexpected character at Line 1 character 13: ] (93) when reading array ({ or [ or ’ or " or number or boolean or null expected)
Context:
{“Devices”:[],“ReturnCode”:“-3333”,"ErrorMe[/color]
Any help would be greatly appreciated!!
Questions 
getting this in the status window at top of Vera web page…
MyQ Gateway : MyQ Gateway Unexpected Door Status: 3
Also, any way to change the Buttons from Locked/Unlocked to Open/Closed? And image from a lock to a garage door?
btw, just got this installed… loving it so far! Now I need to integrate a Garage Door automation app (or PLEG).
The ZIP file includes a MyQ image (MyQ_Gateway.png) and Macrho provides instructions on how to load that onto Vera.
You could modify that image to show a garage door.
The Locked/Unlocked status is because the plugin uses the standard Doorlock service ID which uses these status texts. I’m not sure if UI5 has a GarageDoorOpener service ID. Or Ui7RC for that matter as it does not seem to like the Iris GDO from what I am hearing.
Been using this for a few days and it seems the device will properly show status BUT it does not control the garage doors?
I can control the doors perfectly fine using the Android app from liftmaster.
Am I missing something in the config?
Sent from my HTC6525LVW using Tapatalk
mine worked also when I first installed it but now its not
I believe the delay between authorization cycles may be too long. I’ve cut mine in half to 4 hours and am waiting to see if that brings any improvement…
Generally if I can’t get the door to respond I run a ‘luup reload’ scene and when I try again to open the door most of the time it responds.
[quote=“BOFH, post:158, topic:180826”]I believe the delay between authorization cycles may be too long. I’ve cut mine in half to 4 hours and am waiting to see if that brings any improvement…
Generally if I can’t get the door to respond I run a ‘luup reload’ scene and when I try again to open the door most of the time it responds.[/quote]
did this help?
How do you change the setting?
Still testing as I only use my garage door twice a Inday.
In the L_MyQGateway.lua file change the value for the REFRESH_TOKEN_INTERVAL variable and upload the file back to Vera and reload LUUP.
Legal Disclaimer: I’m not responsible for any consequences experienced as a result of reading the above.