This works fantastic
2 Likes
Thanks for the reply - I have one of these on my front door, but didn't realize/pay attention that it had a tilt sensor as well. I placed my order.
1 Like
Just be sure you go into the device options and set the “use with garage door” option. I don’t recall exactly what the terminology is but it’s something along those lines (I’m away from home so I can’t double check). I know with the ST hub setup I had to delete the device and re-add it when I added the multipurpose sensor, not sure if that’s a needed step with HE.
I also followed recommendations on MyQ troubleshooting and set up a rule to refresh the tilt sensors state at some interval so the garage door open/closed indicator works more reliably. I can’t remember if that’s part of this thread or another
Sifting through this discussion, except for the price difference, it seems the Go Control Z-Wave system is a better solution than the Chamberlain. Easier implementation. Not cloud based so more secure which is important to me and the reason I went with Hubitat to start with. And I see nothing indicating there is any type of implementation problems with the Go Control as opposed to the Chamberlain. Is this an accurate analysis?
My time and security of the family would be worth the difference in the price if this is the case. Although I will need this solution X3 so that price difference will add up!
Longevity?
The Smartthings multi is half the price ($20) of the NYCE tilt sensor ($42).
I'm torn... I don't mind spending more for something that will stay connected and last.
Why don't you make your own locally controlled Garage Door opener?
It cost me ~$35 (Peanut plug, relay and sensor put together).
Thanks for the suggestion. I've ordered one Go Control for our most used door. I also ordered tilt switches for the other two doors just to keep track of them in the system. I was thinking I could add a dry contact relay and control those two with hubitat logic sometime in the future. But again I would like to stay with Z-Wave and would likely use this switch despite it's cost. Just seems a good solution with everything, including a manual button, in one package. https://www.amazon.com/Remotec-Zwave-Contact-Fixture-Module/dp/B00913ATFI/ref=sr_1_4?gclid=EAIaIQobChMI9LjZ1qbT5QIV5x6tBh2ogQw_EAAYASAAEgLDSvD_BwE&hvadid=234007171409&hvdev=c&hvlocphy=9027746&hvnetw=g&hvpos=1t1&hvqmt=e&hvrand=4942526173232079376&hvtargid=kwd-449854050877&hydadcr=8462_9619044&keywords=zwave+dry+contact+switch&qid=1572964849&sr=8-4
Then use a z-wave momentary switch or relay. The Remotec you linked to would work, as would the FortrezZ MIMOLite. Or, you can use any z-wave receptacle and write a momentary driver for it (or use Rule Machine).
Hello - I recently bought a MyQ hub to control my garage door. I quickly discovered that you can't trigger the door to open using google or IFTTT, which was what I wanted most from it. After finding this hubitat plugin for MyQ, I decided to join the Hubitat club. I've added the app and driver code, but am having trouble when trying to connect it to the MyQ. It says I can choose to use a door sensor to detect status or to create discrete on/off buttons. I didn't have a sensor available, so I chose the discrete on/off buttons, but when I continue past that step I get this error:
Summary
Installation Details:
There was a problem updating devices: java.lang.NullPointerException: Cannot get property 'deviceNetworkId' on null object. Line number: 668 Last successful step: Sensor Indexing
What am I doing wrong?
Hi Steve - whose app & driver are you using? You should be using the ones from @dman2306, which have been updated to work with the latest version of the MyQ API. Also, this version, will require you to use a contact or tilt sensor directly paired to Hubitat.
I think I downloaded from that repo, but using some direct links I found up a bit further in the thread, so now that I see the readme, it's possible I didn't get the right driver version.
So you're saying that all of the stuff on that github page about setting it up without a sensor is no longer accurate? I can add sensors at some point, I just wanted to get it working initially as a proof of concept before investing more into it. Just to be able to trigger the opener from the hubitat, without being able to see the status. Guess not.
Hubitat can definitely trigger open
$20 gets you what you need to satisfy the requirement for the driver (which is the same for SmartThings btw)
I see some posts above suggesting that the smartthings multisensor doesn't work for this anymore, is that right? What kind of $20 sensor would work for this use case? I'm trying to envision how I would install a contact sensor on the garage door..
I just set this up using the ST Multisensor and it works fine. It will get picked up using the native driver. You just need to set up the sensor and select the "Do you want to use this sensor on a garage door? (use without magnet) " option.
I have the ST sensor too, and it works fine.
This great! Would you mind posting a picture on how it's setup on your garage door? -Thanks!
Any reason we cant use the API to get open/closed states?
The only negative I see here is that we would have to poll the servers periodically to get state, whereas a sensor could provide state immediately. My guess is that the myq device pushes status to the cloud as it learns of it.
The MyQ EULA doesn’t permit this. It would certainly “work” but they have blocked IPs from accessing the api in the past, this happened with Smarthings years ago.
1 Like
I assume you mean because we would have to poll it frequently?
Yup. And if you set the frequency to be too long, say 5 minutes, then is it even valuable?
