I have the old style MyQ/Craftsman setup and when I use the MyQ plugin to close the door, the lights on the opener blink and the ‘siren’ on the wall control goes on as well. I’m wondering if this new wireless one needs some additional parameters for the strobe and siren to come on. Unless JoeyD did some major changes to the plugin since I last worked on it, it’s basically accessing the MyQ servers spoofing as being the MyQ/Craftsman app so the server should send the same commands to the opener as if the actual app was connected.
That’s the behaviour on mine as well.
I'm wondering if this new wireless one needs some additional parameters for the strobe and siren to come on. Unless JoeyD did some major changes to the plugin since I last worked on it, it's basically accessing the MyQ servers spoofing as being the MyQ/Craftsman app so the server should send the same commands to the opener as if the actual app was connected.
Nope…I’m doing nothing different. My thoughts are along the same lines as yours. This type of model must take additional arguments in the command syntax in order to turn on the warnings. Do you know how tomtcom and I would be able to capture the url / command that is sent from the web app (www.mychamberlain.com) so we can inspect for the difference in command when opener is tripped?
I’ll answer my own question…(I need to run up my post count to 100 anyway to become a normal forum “member” so I can again attach files / screenshots in my posts.) 
I worked out how to do this using firefox browser tools. Ihave been able to verify that the command that the web-app sends to the gateway to close a garage door with my style opener only consists of a single “setDeviceAttribute” command that sets the “desireddoorstate” to a value of 0.
So we should be able to see if tomtcom’s device has additional commands or arguments.
Attached are a few screenshots (UI7) for version 1.5
- Devices including myQ light
- myQ Setup page showing successful authorization
- myQ Setup page showing invalid authorization
Wow! Damn nice job there JoeyD. The plugin migrated to the major leagues with that…
I only wish the UI was a bit more flexible without having to learn javascript. From what I understand, even UI5 has some better basic functionality. For example, in UI7 you cannot visually see if a button is “selected”, which is why I have to but a label next to the buttons to let the user know which option has been selected.
It’s functional, but not particularly pretty.
I’ll answer my own question…(I need to run up my post count to 100 anyway to become a normal forum “member” so I can again attach files / screenshots in my posts.)
I worked out how to do this using firefox browser tools. Ihave been able to verify that the command that the web-app sends to the gateway to close a garage door with my style opener only consists of a single “setDeviceAttribute” command that sets the “desireddoorstate” to a value of 0.
So we should be able to see if tomtcom’s device has additional commands or arguments.[/quote]
Ok, I don’t have Firefox installed but I can do that so we are working with the same tools.
Just tell me what you do to get the attributes and I’ll do the same and report back.
Alright tomtcom…let’s give it a shot!
-
First start with your garage door physically open.
-
Next, with the CHROME browser, log into mychamberlain.com with your id and password. After you are logged in and can see your garage door switch, hit ctrl+shift+I. This pulls up the Developer Tools.
-
Click on the Network tab.
-
When you are ready to close the garage door, Clear the network log, then in the left hand pane click the garage door button to actually close your garage door.
-
Now, near the top of the network log you should see at least one entry for “setDeviceAttribute”. Click on it. (click on the text ‘setDeviceAttribute’)
-
Click on the headers tab
-
Expand the section titled “Request Payload”.
I’ll want to know the contents of that section (screenshot), and if there is more than one ‘setDeviceAttribute’ command issued when you close the door, the contents of Request Paylod for those as well.
For reference, there is only one setDeviceAttribute command sent when I close my own garage door.
See attached screenshots when referencing the instructions.
Do we have PIN codes setup yet? I may have missed it.
And thank you JoeyD -you have inspired me to start contributing…
No work has been done yet with respect to PIN codes. Can you be more specific about the type of PIN code support you’re looking for? From what I can tell, there is not really anything to support.
I believe that myQ allows you to set a pin within their mobile app (iOS or android) that you can manage to force you to enter in the PIN whenever you open and close the garage door remotely. (This pin is separate and can be used independently from your login ID and password). However, this appears to be managed on the mobile app itself…it’s not part of the server side authentication.
If you mean to be able to manage PIN codes on remote garage door keypads…there is no myQ garage door key-pad that I’m aware of. Would be a nice device for them to add though…
Looks like version 1.5 is now available from the App store.
@JoeyD Thanks for your work on this! I just re-installed the plugin (I didn’t want to wait for the auto update) and my light showed up. I can’t wait to test it tonight. Thanks again!!
Will it auto update ( checked) or should I uninstall the old and reinstall the 1.5?
It should auto update…but I don’t know how often or how consistent that process is.
There’s no harm in uninstalling your current version and installing the new one.
[quote=“JoeyD”]Alright tomtcom…let’s give it a shot!
-
First start with your garage door physically open.
-
Next, with the firefox browser, log into mychamberlain.com with your id and password. After you are logged in and can see your garage door switch, hit ctrl+shift+I. This pulls up the Developer Tools.
-
Click on the Network tab.
-
When you are ready to close the garage door, Clear the network log, then in the left hand pane click the garage door button to actually close your garage door.
-
Now, near the top of the network log you should see at least one entry for “setDeviceAttribute”. Click on it. (click on the text ‘setDeviceAttribute’)
-
Click on the headers tab
-
Expand the section titled “Request Payload”.
I’ll want to know the contents of that section (screenshot), and if there is more than one ‘setDeviceAttribute’ command issued when you close the door, the contents of Request Paylod for those as well.
For reference, there is only one setDeviceAttribute command sent when I close my own garage door.
See attached screenshots when referencing the instructions.[/quote]
Thanks. I’ll try to do it soon and report back.
Ugh…I just realized that I gave you instructions for using the Chrome browser, not firefox! However, I can provide instructions for firefox and / or Internet Explorer if desired. Just let me know.
UI5 Plugin was installed as beta, not from the store. Re-installed from the store. Worked like a charm.
UI7 Plugin version v1.2 with Auto Update checked. Didn’t update, not even after I unchecked and rechecked.
Installed 1.5 version and on the device used your setup section. Piece of strawberry shortcake.
For some reason on neither UI it is showing the MyQ icon for the master device…
I think I know where the ‘add pincode’ posts came from. UI7 sees it as a door lock and one of the options at the top for that kind of device is ‘Add pincode’. Which is not supported by the MyQ device. UI5 also has that option but it is not as prominent.
Ugh…I just realized that I gave you instructions for using the Chrome browser, not firefox! However, I can provide instructions for firefox and / or Internet Explorer if desired. Just let me know.[/quote]
No I’ll stick with Chrome. I was going to have to install FireFox so that is one less thing. Thanks!
Ugh…I just realized that I gave you instructions for using the Chrome browser, not firefox! However, I can provide instructions for firefox and / or Internet Explorer if desired. Just let me know.[/quote]
No I’ll stick with Chrome. I was going to have to install FireFox so that is one less thing. Thanks![/quote]
Unfortunately it’s the same as yours.
I filtered on setDevice to make sure. I did another round of open/close. Other than 1 and 0 nothing was different and no other things came through but get messages.
How do you find out which version of the plugin you’re running on UI5?
Nevermind, I found out. You have to look on the Apps page and not within the device settings.