That is a smart plug for a lamp - completely unrelated to the built-in light on the door opener.
That said, the lamp control does work with this SmartApp.
1 Like
I use this same light controller and it integrates well into SmartThings via Brianâs awesome SmartApp.
Thank you brbeaird for your hard work!
Is this smart app supposed to work with new smartthings app?
I recently got sensors and changed the settings so that I no longer created separate Open and Close switches. But now, how do I simply send a âcloseâ command? In my scene, I add the door, turn it âonâ (oddly enough) to enable the switch commands. The âpress momentaryâ option is off, âDoorâ is not set, and âGarage Doorâ is set to closed. But if the door is already closed, it actually opens the garage door even though I said âclosedâ. I canât figure out the correct setting here.
I pushed a small update today to account for an API change where the device control endpoint is now apparently case-sensitive and requires lower case. If youâre getting errors trying to open or close doors, try pulling down that update and see if it fixes it for you.
3 Likes
As an update - I have confirmed with some other developers on other platforms with MyQ integrations that this new intermittent error issue is on the MyQ API side and is affecting anything hitting those endpoints. Someone has also discovered that it looks like the API is upgrading again (from v5 to v6). Presumably, switching to v6 will fix these errors, but from what I have heard, this will once again be a fairly significant change, so it may be awhile before I can get the info and then refactor the app here to work with the new version. Iâll keep things updated here.
8 Likes
Where do they, Chamberlain, publish their API?
I didnât start having errors until I updated to the latest 3.1.5. My goodnight automation sends a close command and that registers an error.
They donât. Everything we (and other projects) have is from reverse engineering.
I feel very confident the update did not cause the errors you are seeing now. It was my attempt to fix those errors, but it did not help as the issue is on the MyQ side. All the other MyQ integration projects (Home Assistant, Homebridge, etc.) are dealing with this right now. It sounds like some people have begun the process of reverse-engineering the latest version so we can make changes to account for it.
Still, you can always revert to whatever version you want in GitHub by clicking the âcommitsâ link and viewing the code at an earlier version.
3 Likes
I reverted to 3.1.4 and the doors began working again.
I was lazy and I left mine at 3.1.5, and it started working again on its own. Looks like the server side corrected whatever fault they were experiencing. The litmus test would be returning to 3.1.5 to see if the problem is reproducible for you.
I tested the two doors about two minutes before reinstalling 3.1.4 to confirm they still werenât working, so if what I saw was a result of a server-side correction then there was some strangely fortuitous timing. However, it wouldnât be the first time something like that has happened.
Also, largely because I trust that @brbeaird knows what heâs talking about, almost immediately after I posted I decided I would reinstall 3.1.5 to test it again as you suggest, but unfortunately I ran out of play time. I will hopefully be able to do that tomorrow.
1 Like
Hey Brian,
I have an intermittent error - every other time I try and use smartthings (via alexa) to open/close my door, I get an internal server error. See attached.
Using the latest 3.1.5. Itâs random - sometimes it works 4-5x in a row, then will fail 1-2x in a row. Any ideas?
Yep - read a few posts up. Itâs random for everyone due to API changes being gradually rolled out on the MyQ side. It apparently comes and goes without an obvious pattern. I was seeing it a couple times a day last week, but itâs been several day since Iâve run across it. Best we can do it sit tight until some other developers share how the V6 endpoints work.
1 Like
Thanks! Hats off to you! Thatâs hard!
Will the no-contact-sensor setup ever work with the new app? Iâm looking at either paying $4 per month to IFTT for my 3 garage doors, buying tilt sensors (and changing batteries for them) or using the old app.
I donât need status from within SmartThings, I just need to be able to control my garage doors from routines.
I still think it will, but I do not know when.
So I posted on another thread but having issues with this app and automations so maybe you all can help.
Converted to the new app back in October and everything had been working fine. Then last weekend with the app update the automations that I had based on arrival of a ST presence sensor started acting wonky. In the app it looks like the automations are no longer working based on the arrival of the sensor and what is even more odd is that when we leave and close the garage a few minutes after we are gone the garage opens again. Almost like something is arriving when it isnât.
I feel as if I read some scuttle about presence sensors not working as they had in the past but everything was working until the latest update for me. So if I canât use presence sensors for actions upon arrival how do I configure those actions? Does this not render the presence sensors useless?
Help! Thanks!
My presence-based rules are working, but I do them through the Smart Lighting SmartApp, not the actual âAutomationsâ function.