I actually had my IP address blocked by Chamberlain due to this issue. Had to go back and forth with the moderator about it, but their terms of service is written in such away that they can deny service if they don’t like what you are doing. Yes I recommend updating the polling frequency otherwise they will come and block your IP address.
I set my polling frequency to like 300 (every 5 minutes or so) to start with as I have one of the Ecolink tilt sensors installed. Which will report the door opening or closing directly to Vera without the delay of having to go through the MyQ gateway.
Gotta figure out how to add some of these variables to the MyQ advanced tab so it’s easier to set them. NO luck so far even by adding an entry in the S_MyQGateway.xml file. I’m fearing I have to delete the controller and GDO devices and re-install. Don’t want to risk that on my only (production) Vera at this time.
If Chamberlain would only provide an API so we can access our local MyQ/Assurelink controllers directly as that would solve all the issues. Looks like they want to retain control so they can start charging if they feel like it. Pity. It’ll probably take someone with a packet sniffer and far more knowhow than myself to decode what they send to your local gateway and reverse engineer it.
I found the tilt sensors unreliable. I get random false positive.
How does the Android app get notifications? Is it different?
Sent from my HTC6525LVW using Tapatalk
I’ve had no problems at all with my tilt sensor. I also have the myQ/Assurelink service send me an email when the door opens/closes and so far I’ve always gotten one from both Vera and MyQ. Vera first and MyQ anywhere from 1 to 15 minutes later.
I do not think the Android app gets notifications. You have to run it and log in to see your door status. It’ll tell you it has been open for X time or closed for X time.
The advantage of teh plugin over the app is that you can run a scan and have the door closed by Vera if you forget to close it. Or if you use Geofencing you could have Vera open it for you if you are coming home.
The Android app gets push notifications. I have been using it since the vera is not allowing me to control the doors, it is only showing status.
Sent from my HTC6525LVW using Tapatalk
I must be dense but I can’t find the push notification setting in the Craftsman Assurelink (Craftsman Version of MyQ) app on my phone.
I’m able to operate the door about 80% of the time via AuthomationHD. The remaining 20% there’s no response. Weirdly enough, when I go to the Assurelink app immediately after, there’s a bout a 50/50 chance of it actually getting the door to respond as well.
there should be a little calender looking thing with a check mark in it with a little + and you have to create a rule
Does this work on UI7? I loaded it and put in username and password and restarted my vera and all I get is MyQGateway : Authorization failed. I am using the same email and password that I am using on my phone app so I am not positive of what I am doing wrong.
Sorry answered my own question. I am using a Craftsman and didnt change the necessary files. It shows up now but I keep having this popup Can’t Detect Device and its not opening the door when I try.
I’m running it on Ui5 with no issues using Assurelink. If you are running it on Ui7, the not finding the device issue may be related to Ui7. I don’t think the original author has a Vera running UI7. I just ordered one from Amazon so I could check on Ui7 and test some of the plugins I use. (As well as having a backup in case my Vera 3 dies)
Once that come in, the MyQ/Assurelink plugin is one of the ones I will be testing.
BOFH thanks for the information. If you end up testing it please let me know.
We have a new how to for controlling MyQ garage door openers without the app.
I’m still not getting control of the doors via Vera… only Status. Anyone have this working?
I am new to this, but thanks a lot for the dev.
I installed everything and it picked up my child devices. However, it keeps restarting… I get…
Please Wait
Z-Wave configuring devices
Running Lua startup
During “please wait” the gateway has a red sign “can’t detect device”
Is this the 90 second polling or is something not right?
Are you running UI7, UI6 or UI5? There are problems with UI6 and UI7 with the plugin.
I’m using UI5 … is control from Vera working for you, or just status like on mine?
I have a parent MyQ device that shows last auth & last check time as well as a child device of type _door Lock that has on unlock (open) button and a Lock (close) button for my garage door.
Click the Reload button and keep a close eye on the little log window at the top of the dashboard. See any errors generated by the MyQ device when it initializes? Do you have a Liftmaster/Chamberlain MyQ system or a Craftsman Assurelink system? If the latter, did you make the changes to the plugin so it uses the App ID for Craftsman? As the default plugin only works for Chamberlain/Liftmaster.
Since I got my development Vera 3 in yesterday I’ve been tinkering with Macrho’s plugin. I’ve added another variable in the advanced section named ‘Brand’. Valid entries for that are Liftmaster, Chamberlain or Craftsman. My incarnation of the plugin reads that value and sets the ID’s and URL’s accordingly so you’ll go to MyQ for Liftmaster/Chamberlain with their ID and to Assurelink with their ID for Craftsman. I’m contemplating adding values for the authorization and check interval as well so they are also more easily user definable.
I haven’t figured out yet why sometimes the MyQ/Assurelink sites just seem to ignore the plugin’s open or close the door requests. Most of the time (but not always) a LUUP reload fixes this. So I have a scene for that I can run from my smart phone.
I installed the plugin. It seems like it’s working, but it created two children (that both get updated status) instead of one? I tried deleting one and it recreated itself.
I logged into mychamberlain.com and I only see my one device.
[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]I think you have the right solution but 4 hours is still way, way, way too long. From what I see the session expires within a few minutes.
I just modified the code to authorize on every request and it’s working reliably so far. I’ll report back after 48 hours to confirm for sure.
[quote=“cdtorres, post:161, topic:180826”]I actually had my IP address blocked by Chamberlain due to this issue. Had to go back and forth with the moderator about it, but their terms of service is written in such away that they can deny service if they don’t like what you are doing. Yes I recommend updating the polling frequency otherwise they will come and block your IP address.[/quote]I suspect you were blocked because they detected so many requests coming from expired security tokens. I’ve done web traffic analysis work for a very large company, and errors tend to get the most scrutiny. From what I can see the session now expires pretty quickly, so if Veras are polling every 60-90 seconds and not refreshing for 8 hours, that’s going to be a lot of errors and might raise some eyebrows. This activity might have had their developers scratching their heads wondering what the source of the errors are.
I also wouldn’t be surprised if the token duration was shortened to improve security.
Changing the code to authenticate for each request seems to have solved the -3333 errors and failures to open/close.
I’ve attached the version of the code I’m using if anyone wants to look at it. There are some changes:
- Authenticate on each request
- Change polling delay to 5 minutes
- After a command to open / close the door is sent, poll 30 seconds later (so you can see if the command was successful or not)
- Add door state 9 to be “Open”. It’s coded for 1 = open, but mine returns 9 for whatever reason.
- I have a hack limit to the 1st opener because I get a phantom second opener device created.