Jump to content

Chamberlain/Liftmaster MyQ & ISY Integration Complete - Should I Release It?


cam

Recommended Posts

Posted

I've been working on integrating the Liftmaster MyQ Cloud platform with the ISY994.  As you know the ISY Networking module is very limited in its capabilities so I developed a platform where I can send/receive garage door statuses from MyQ and push them into an ISY (via the REST API) as variables so that I can use the ISY to perform operations - including closing/opening the doors.

 

Would this service be valuable to a wide audience?  Just trying to gauge the interest.  Unfortunately it needs to run in an another environment (which costs money) but considering building this service and charging a minimal fee. 

Posted

Reach out to io_guy and see if it can be integrated into nodelink.... That way the MyQ stuff will be represented as actual nodes rather than variables.... :)

Posted

Reach out to io_guy and see if it can be integrated into nodelink.... That way the MyQ stuff will be represented as actual nodes rather than variables.... :)

 

I agree that the integration between ISY and MyQ would be excellent if the garage doors where exposed as nodes - but I'm new to ISY and its ecosystem (and who/how to contact).  I assume the ISY API supports creating nodelinks - I'm using the Elk module which exposes my motion sensors as nodes so I know it can be done...

Posted

I would be interested if nodes would be available.

Likewise, I already have this working using some of the existing Python stuff on a Pi and the network module. When 5.x becomes stable I would look for a cleaner implementation as a poly node.

  • 2 weeks later...
  • 3 weeks later...
  • 2 weeks later...
Posted

I've been working on integrating the Liftmaster MyQ Cloud platform with the ISY994. As you know the ISY Networking module is very limited in its capabilities so I developed a platform where I can send/receive garage door statuses from MyQ and push them into an ISY (via the REST API) as variables so that I can use the ISY to perform operations - including closing/opening the doors.

 

Would this service be valuable to a wide audience? Just trying to gauge the interest. Unfortunately it needs to run in an another environment (which costs money) but considering building this service and charging a minimal fee.

I'm interested too.
  • 2 months later...
Posted

I'm actively working on it. The backend software is mostly done. I purchased a dedicated server, SSL certificate, etc. Actively working on a UI to allow users to register/login and schedule MyQ events (e.g. Automatically close any open garage door at 11PM, automatically close doors if left open for longer than X minutes/hours). For those that wish to integrate garage door state with their ISY I can update variables. My system will also allow users to register their cell phones to send/receive text commands/alerts. For example, you could register your parent/sibling/babysitter's mobile device and allow them to text a command like "open garage door". In fact, planning to expand that concept to ISY. For instance, I have a Zwave deadbolt on front door and I/kids/wife can send a text to "open front door"...

 

I'm going to need some "beta" testers and will post to this thread when I'm ready... Scope creep is killing me because I keep dreaming up more things to add but I need to wrap up what I've done already and release it

Posted

I just set up an IFTTT using the my chamberlain emails as a trigger, a state variable and a program to to get notifications after 11PM if the door is still open (it also flashes the upstairs landing light :-) ). To add the ability to actually shut the door would be great. 

Posted (edited)

I actually developed a add in for my RTI remote control system to control MyQ Chamberlain and Liftmaster GDOs. Was a pain to get the SSL and url properly working without them timing out. If you need any help feel free to PM me.

 

I also suggested MyQ to be put into IO Guys NodeLink.

Edited by Scottmichaelj
  • 4 weeks later...
Posted

At last, I finally have a beta version ready for testing...  My primary goal/purpose for building this service was end-user simplicity.  If my wife has to download an app to close the garage door it'll never happen.  I have amazing ISY programs that do amazing things but my wife/kids struggling launching an app, website, etc. to run those programs.  The primary goal of my service was to make it as easy as possible for my wife/kids to interact with my automated home - no app required.  My wife can now text a simple command and magically our house comes to life :-)  

 

Here are some highlights of the service I built:

  • Allow MyQ users to configure a night time setting, which will automatically close any open garage doors (e.g. at 11 PM).  Never leave your garage doors open at night again :-)
  • Allow MyQ users to receive text alerts when their garage door has been opened for longer than a specified time - with the ability to have the system automatically close the garage door when replying back to the text message alert (no app required!)
  • Allow MyQ users to send text commands to:  1) check if the garage doors are open.  2) Open all garage doors.  3) Close all garage doors
  • Allow ISY users to send text commands to run any ISY program.
  • The admin user can add other user's mobile numbers (e.g. kids, babysitter, nanny, etc.) and allow them to interact with their MyQ or ISY via text commands (no app required).

I plan on expanding the capabilities - especially around ISY capabilities and integration - but welcome and/all who would like to try it as-is.  I'd like to keep it to a small number of folks willing to try it out and provide feedback as I'm sure there are many issues I'll need to resolve.  

 

Please PM me if you would like to try the service...

 

Thanks!

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

  • Forum Statistics

    • Total Topics
      37.1k
    • Total Posts
      371.5k
×
×
  • Create New...