[quote=“ypodolyan, post:460, topic:180826”][quote=“tomtcom, post:459, topic:180826”][quote=“ypodolyan, post:458, topic:180826”]I have some issues with plugin.
Logged in to Vera today and see that Last Auth was on Sunday and Last Check was on Sunday and message that myQ failed to authenticate. Went to myQ setup and clicked on UPDATE without changing user name or password, the number of doors changed to 2 again (correct) and Last Auth changed to today (Wed) and current time. Question: if myQ fails to authenticate, won’t it try again later? It seems that it didn’t try and got stuck in inoperable mode. My automation depends on it and I had no idea it failed as I didn’t get any notification.
Even after update and successful authentication, Last Check is still Sunday. Why did it not do the check after successful authentication?[/quote]
Did you load the new lua file from a few posts back? You might have made a one time successful authentication but the app stops because a few authentication mechanisms changed.
Load that file if you haven’t and check again.
Also, for today I did have 2 false alerts of the garage opening and closing when it didn’t. Just letting others know.[/quote]
Yes, I did load new lua file.
So, after Last Auth was OK, Last Check wouldn’t change until I explicitly reloaded Luup.[/quote]
What do you have in your variables? See my screenshot especially refresh interval. The lowest is 2 minutes (120 seconds).
I have the same vars (except 1 more door and Liftmaster instead of Chamberlain).
[quote=“tomtcom, post:461, topic:180826”][quote=“ypodolyan, post:460, topic:180826”][quote=“tomtcom, post:459, topic:180826”][quote=“ypodolyan, post:458, topic:180826”]I have some issues with plugin.
Logged in to Vera today and see that Last Auth was on Sunday and Last Check was on Sunday and message that myQ failed to authenticate. Went to myQ setup and clicked on UPDATE without changing user name or password, the number of doors changed to 2 again (correct) and Last Auth changed to today (Wed) and current time. Question: if myQ fails to authenticate, won’t it try again later? It seems that it didn’t try and got stuck in inoperable mode. My automation depends on it and I had no idea it failed as I didn’t get any notification.
Even after update and successful authentication, Last Check is still Sunday. Why did it not do the check after successful authentication?[/quote]
Did you load the new lua file from a few posts back? You might have made a one time successful authentication but the app stops because a few authentication mechanisms changed.
Load that file if you haven’t and check again.
Also, for today I did have 2 false alerts of the garage opening and closing when it didn’t. Just letting others know.[/quote]
Yes, I did load new lua file.
So, after Last Auth was OK, Last Check wouldn’t change until I explicitly reloaded Luup.[/quote]
What do you have in your variables? See my screenshot especially refresh interval. The lowest is 2 minutes (120 seconds).[/quote]
FYI, I just had a new Liftmaster 8550W installed to replace my aging Genie + MyQ Wireless setup. This is apparently a very new model with built in wifi (no longer need a separate gateway module).
The 8550W seems to use a new deviceID. Recommend modifying:
I have a three Liftmaster openers with a Liftmaster gateway, they are all a few years old and work from the MyQ app and website. I installed the plugin and applied the fix. I no longer gets Authentication errors but no child devices were created. I have tried several times, but same results. Setup screen shows my user name, password and “Selected Brand:Liftmaster” but also the following
“Number of garage doors / gates found:Opener brand not configured:”
I have restarted the Veraedge and reloaded Luup several times, still no child devices.
I pushed cybrmage fixed lua version and requested an approval for the new plugin version from micasa guys. It usually takes a day or two to get it, afterwards everybody should get version 1.9 of the plugin that works well against more strict MyQ validation.
I got the plugin update 1.9. I have a Chamberlain MyQ that is currently operating a Craftsman garage door motor/opener. The 3rd party application works, but when I put in the Brand “Craftman” and my login credentials, it still fails and says the myQ authorization fails. I then quickly change the brand to Chamberlain or Liftmaster with same credentials, and the “Last Auth” actually puts the time. After that nothing happens.
Is there anything I am doing wrong. How would I get this plugin to authenticate properly.
[quote=“kornev, post:467, topic:180826”]I pushed cybrmage fixed lua version and requested an approval for the new plugin version from micasa guys. It usually takes a day or two to get it, afterwards everybody should get version 1.9 of the plugin that works well against more strict MyQ validation.
I will keep you posted about approval progress.[/quote]
Cybrmage & Kornev,
Can I suggest you guys start another thread so you can control Post #1… and keep Post #1 updated with the latest changes/fixes/etc?
The brand that the plug-in is looking for is the brand of the MyQ gateway, not the brand of the garage door opener itself. So in your case, set the plugin to Chamberlain and make sure you have chamberlain and not craftsman credentials to use.
Has anyone been able to sort out why during a new install under UI7 plugin authenticates but does not detect or create child devices? I have also attempted to remove and recreate the device through MyQ without luck.
You may have a newer MyQ device with an ID that the plugin does not recognize. If you can find the ID, it’s not hard to update the plugin with it. Download the L_MyQGateway.lua file from your Vera to your computer and open it up in a text editor. Then look for the local GARAGE_DOOR_OPENER variable and add the device ID if it’s not there. The local GATEWAY_DEVICE variable containes ID’s for the gateways. Once edited, save and upload back to Vera, then do a LUUP reload.
Removal of the old device and install of the new one took about 3 hours. Once I got through the not-straightforward MyQ setup, I installed this plugin in my Vera and it is working great! I changed the RefreshInterval to 30 in the parent device. I hope that is not a problem?
Thanks so much for all of the hard work that went into this!
Thank you for the information. Putting Chamberlain didn’t work, until I uninstalled the application and reinstalled it. I also noticed that if you “link” Nest or perhaps Wink (in Chamberlain 3rd party app), the device ID’s may effect getting the correct child device id’s and not put them in Vera’s UI. So I unlinked them, uninstalled plugin, rebooted Veralite, and started from scratch. Either or, it is working now and is working well thus far.
I doubt this is the cause, as I used this without issue before my upgrade to UI7 and even since. i will investigate, but also thinking it may be related to Wink or Nest, so going to disable all these connections and start from scratch
I doubt this is the cause, as I used this without issue before my upgrade to UI7 and even since. i will investigate, but also thinking it may be related to Wink or Nest, so going to disable all these connections and start from scratch[/quote]
So I can confirm like jadragescu that my Nest being linked to the MyQ device through the iPhone app was the issue. I removed the Nest from the account on the app, then reinstalled the app on Vera. Devices worked immediately. Was able to re-add Nest afterwords.
I was trying to add the pin code in the “Add pin code” tab. After entering the PIN name and Pin Code and hit Save pin code, it does nothing. It will not save and I’ve even tried to reload the engine. Any ideas?
There is no pin code for a MyQ device. The plug in creates a ‘lock’ device which by default has a pin code setup for those locks that support it. Such as Schlage and Yale door locks. MyQ openers do not support a pin via the app or the plugin. Only via a physical pin pad directly connected (wired or wireless) to the opener itself.
The praise does not go to me unfortunately. This plug-in has been a community effort. my meager contribution was adding support for Craftsman Assurelink openers.
Hi all, I’m really lost at this. I have been able to figure out the rest of the quirks with this app from this thread but I’m stuck at having Vera control the garage door. I can control the MyQ through my iPhone without issue. I have the app installed in Vera and can log into it correctly (selecting Chamberlain as that is adapter I have), however I can’t control it from Vera, nor will it update the open/close status in Vera if I control it from the app on my phone.
Everything is fully updated, and I tried to uninstall and reinstall the MyQ app on Vera a few times. I even restarted my VeraLite but I can’t get Vera to control the door opener. Any help that someone could give would be great as I’ve spent a couple hours on this already and I can’t figure it out.
Tried a quick search and didn’t seem like anyone else is having my problem. I have the myq plugin working perfectly with two garage doors… my only issue is that they show up with the door lock icon… i tried changing D_DoorLock1.json to D_GarageDoor1.json and my device just disappeared. I’ve reinstalled the plugin and have it working again, but does anyone know how to successfully change that icon in ui7?