Do you guys mean UI7 firmware issues? I’m still on UI5… any issues there?
Guys, I requested approval for new plugin version (1.3) that has all the recent changes including those made by JoeyD (thanks!).
PS He should join the ranks of MyQ plugin developer soon, so hopefully it will go a lot smoother from now on.
PPS Anyone else stuck with 1.7.439 version of firmware? Vera kept saying I am on the latest version, even though there is clearly a new firmware available.
@Kornev: Somehow Vera3 does not seem to realize there is an update. I had the same problem.
Thanks to SWFIRE271 in another thread, here’s the direct link to put in the advanced box under Firmware:
http://download.mios.com/rt3662_betafirmware/rt3662_Luup_ui7-1.7.481-en-mios.squashfs
I can confirm JoeyD’s json fix resolves the blank advanced tab issue under that release.
I just updated successfully using BOFH link (thanks!) immediately run into advanced tab issue and fixed it using updated json by JoeyD.
Just to give everybody an update latest plugin version is still pending approval by micasa. They are really slow this time, probably because of the holidays. I’ll let everybody know as soon as it’s available and it is safe to update.
Hello, I’m completely new to the Vera community (and new to Home Automation) - so maybe I’m not doing something correctly.
I just bought a Veraegde and received it today. I don’t have any devices yet but I do have the Sears Assurelink (I believe same as MyQ) Garage Door opener, so I thought I’d try to connect it.
I appear to be having the problem Joey is explaining above - the my Settings, Advance and Device Options are not populating. Therefore I cannot select my brand, input my username and password.
I downloaded the file Joey added above. But I do not get any different results. I downloaded it under - Develop Apps tab, and LUUP Files. The file now shows in that list. Do I need to do anything different at this point?
I’m running Veraedge, Firmware 1.7.906, and have a Sears Garage door opener (that I can use the Craftsman app to open and close)
Any help would be greatly appreciated.
Thanks
UPDATE - I was trying to do this using Safari on a Mac. I switched over and repeated the entire process on IE using windows and now the Brand/Username/Password show up under the Advance tab. I went back to the Mac and on Safari I clicked on the Advance tab and nothing happens. If I open in Chrome on my Mac I can open the Advance tab - is this sometimes normal with Safari?
Current problem - Now that I can input everything - it tells me Authorization Failed. I’m guessing it might be due to I have a Craftsman Assurelink. For Brand - do I put in ‘Craftsman’. I’ve also input my username and password. Is there anything else I need to do?
UPDATE 2 - OK, now I feel like an idiot. I kept checking everything…then I realized when I clicked on the username and password cell, it put a space in front of whatever I typed. Now everything works great. Thanks for all the time put in.
Brilliant.
Installed 1.2 from the app store. Uploaded the modified json just posted a page back. Works very well.
The Imperihome app which I’m sure many are familiar with had an update adding a new icon for a garage door showing closed/open with some fake car.
When the garage is closed, I have the ON highlighted green and the garage door on the icon is showing open where you can see the fake car.
When the garage is open, I have the OFF highlighted red and the garage door on the icon is showing closed.
How do I know if the icon was made improperly from the Imperihome app or perhaps the device state should be reversed? But that would clash I suppose with the on/off switch where we usually associate green with good and armed such as the standard deadbolt lock and unlocked is red or off state.
Any ideas or comments to that?
I’ve been working on a mini-revamp of the MyQ plugin. Note that version 1.3 (the version with the fixed json) is still under review by mios, and I hope to be able to publish version 1.4 shortly after. I’m assuming we won’t have any movement on app approvals until after this weekend though.
In any case, here are the upcoming changes for 1.4:
-
New UI Tab to update the required settings (door opener brand, user name, password.) This will hopefully make it easier for new users as the settings will be front and center rather than having to find items in the “advanced” tab.
-
When you update the settings, it will automatically re-initialize the plug-in and verify if all is well or not.
-
myQ lighting devices and gates should now be properly supported. Lights will be added as standard binary lighting switches (on / off). Gates should work just like the existing garage doors currently do (using the lock device.)
Most of the work is done, but I currently don’t have a myQ lighting device so I can give it a decent test first. I expect to pick one up on Saturday, then hopefully early next week it will be ready for release.
Wow that sounds great. Thanks JoeyD
[quote=“tomtcom, post:266, topic:180826”]The Imperihome app which I’m sure many are familiar with had an update adding a new icon for a garage door showing closed/open with some fake car.
When the garage is closed, I have the ON highlighted green and the garage door on the icon is showing open where you can see the fake car.
When the garage is open, I have the OFF highlighted red and the garage door on the icon is showing closed…
Any ideas or comments to that?[/quote]
Because the plug-in uses the door lock device, it makes sense that “locked” = “door closed”. Technically it associates a device status of “0” for “open” (device off), and “1” for “closed / locked / on”. This is consistent with the rest of the UI for Vera, where a multi-switch thrown to the right indicates that a device is “powered on” or a door is “locked.” (makes most sense for a garage door that is in a closed state to equate to “locked.”)
My hunch is imperihome assumes that a status value of 1 indicates “door open”…but the opposite is actually true.
[quote=“JoeyD, post:269, topic:180826”][quote=“tomtcom, post:266, topic:180826”]The Imperihome app which I’m sure many are familiar with had an update adding a new icon for a garage door showing closed/open with some fake car.
When the garage is closed, I have the ON highlighted green and the garage door on the icon is showing open where you can see the fake car.
When the garage is open, I have the OFF highlighted red and the garage door on the icon is showing closed…
Any ideas or comments to that?[/quote]
Because the plug-in uses the door lock device, it makes sense that “locked” = “door closed”. Technically it associates a device status of “0” for “open” (device off), and “1” for “closed / locked / on”. This is consistent with the rest of the UI for Vera, where a multi-switch thrown to the right indicates that a device is “powered on” or a door is “locked.” (makes most sense for a garage door that is in a closed state to equate to “locked.”)
My hunch is imperihome assumes that a status value of 1 indicates “door open”…but the opposite is actually true.[/quote]
Understood, and that was my same thinking. Appreciate the response and all is well with the plugin so thanks for the continued updates, it is very much appreciated!
No problem…most of the heavy lifting was already done by the previous authors / contributors. I’m just happy to be able to contribute to a plug-in that I use myself. 
I saw you had another thread discussing the icon for the Vera web UI. I have also placed the MyQ.png file in the correct location but I never see it used.
If you find a method that works, I’ll certainly be a tester of it.
A fix for that is included in the upcoming 1.4 release. Note, however, that since the icon is local, you will only be able to see it when accessing your network locally.
If you don’t want to wait, replace the “default_icon” line in your current json with the following:
"flashicon": "icons\/MyQGateway.png",
"default_icon": "..\/..\/..\/icons\/MyQGateway.png",
And place the MyQGateway.png icon into the following location:
/www/cmh/skins/default/icons
This way, it should work with both UI5 and UI7. I would attach the icon file here, but the message borad is not accepting attachments at the moment. Note there is no underscore in the icon name…I think a previous version of the plug-in might have used an icon with a different name.
[quote=“JoeyD, post:273, topic:180826”]A fix for that is included in the upcoming 1.4 release. Note, however, that since the icon is local, you will only be able to see it when accessing your network locally.
If you don’t want to wait, replace the “default_icon” line in your current json with the following:
"flashicon": "icons\/MyQGateway.png",
"default_icon": "..\/..\/..\/icons\/MyQGateway.png",
And place the MyQGateway.png icon into the following location:
Understood, thanks!
/www/cmh/skins/default/icons
This way, it should work with both UI5 and UI7. I would attach the icon file here, but the message borad is not accepting attachments at the moment. Note there is no underscore in the icon name…I think a previous version of the plug-in might have used an icon with a different name.[/quote]
New here, hopefully someone can set me straight. I installed a Chamberlain GDO which came with a MyQ Gateway (model is CIGBU). Everything works fine including the iOS app and web access, so now I am trying to tie it into my VeraLite and not having success yet.
I uploaded the lastest JSON file and can now see the Advanced tab, so I am able to set up the variables. I verified username and password work (with either mychamberlain.com or myliftmaster.com) but I get MyQGateway : Authorization failed when the Luup reloads. I have tried changing the model in the XML from 828LM to CIGBU, as well as various spellings of LiftMaster and Chamberlain for the Brand, but nothing is working yet.
I guess I’ll try removing the device and creating it again?
Thanks
[quote=“jcmaule, post:260, topic:180826”]Uploaded the new file and now I can see the advanced details. THANKS!!
Found another problem though, when I enter the Username, Password and Brand and then exit the advanced options (click on back) the 3 fields were not saved. I clicked back on the advanced tab and the changes are not there. Another thing is that the fields for these 3 items appear like a line (not a textbox).
UPDATE: While writing this I found that if you click on “Reload Engine” button from the bottom after entering the values, the fields are saved. Two new devices are added and after testing them the first one created works like a charm. Great plugin. I’ve left the previous text in case others are facing the same problem…
Have a safe trip JoeyD and thanks much for the updated file, everybody have happy holidays!![/quote]
Hi jcmaule,
I’m having the same problem as you are and I’m new to this. The question that I have is how do you upload the new plugins.
Thanks in advance.
After testing and a little debugging, I’m happy to report that myQ lighting devices now work as expected. Upon initialization, a new binary light will appear in your device list that will have the same name that you gave it when you set it up with your myQ gateway.
You can rename the device after it’s created if you want.
I don’t have a gate opening device, but technically it will be recognized just like a garage door opener and should just work.
These updates will be included in the version 1.4 release. For those of you that have lighting devices and used this plug-in prior to version 1.4, you may alreadyhave extra non functional “lock” devices established for each of your lighting devices. After installation of 1.4, you will need to delete these non-working lock devices so the plug-in can properly re-implement the binary light device instead.
I will try and code in a warning message if you have an existing device that is not the correct type.
MyQ plugin v 1.3 (with JoeyD JSON fix) was just approved by Micasa and as of today can be loaded directly from app store.
PS 1.4 is going to be awesome, now that we have JoeyD on plugin dev team
BTW I run today into the same authentication issue some of you were having. Apparently some combination of browser/browser plugins/newest UI7 UI (still need to figure out what component is at fault) in some weird circumstances submits field value as HTML instead of a plain text
Here is what I had in my log:
06 01/05/15 11:59:22.905 Device_Variable::m_szValue_set device: 117 service: urn:macrho-com:serviceId:MyQGateway1 variable: Password was: now: <font color="#222222" size="2"><span style="line-height: normal;">DoElVU7fcJWRmMIT0pVR</span></font><br> #hooks: 0 upnp: 0 skip: 0 v:0xc04b90/NONE duplicate:1 <0x2ea57680>Obviously this is wrong because it was trying to set my password value to <font color="#222222" size="2"><span style="line-height: normal;">DoElVU7fcJWRmMIT0pVR</span></font><br> instead of just DoElVU7fcJWRmMIT0pVR
PS And no this is not my real password, although it does look very similar
I have the myq where you affix the level/gyroscope? unit on the garage door and the plugin box on the ceiling.
Is the light on that plugin box supposed to stay on instead of just flash? It’s not the separate remote light. It flashes when I use the myq app but no other way like this plugin it doesn’t light up.