I have asked about the MyQ quite a few times. Unfortunately, it looks like Liftmaster/Chamberlain don’t have an open API for it which is what SmartThings needs to be able to talk to it. Don’t see them working together anytime soon, which sucks.
It is a nice unit. However, I don’t like that it uses a button battery in the tilt sensor. I’m tired of managing batteries let alone the different styles that can’t use rechargables. Wish they had an option for a wired sensor.
Beck - Its usually pretty easy to hack the battery sensors to take a low voltage adaptor instead. I have a bunch of posts on it in the Vera forums. I have a bunch of moisture and motion sensors hooked up through the leads in a pre-existing security system, which go down to a battery-backed adaptor.
Beck you are right about the tilt sensor battery being annoying. On my Vera, I used a magnetic sensor for closed and another for open – I could power both from the other side of the track. That gave me more input on the door status as well.
With this thing it looks like I could do something similar, by putting a high powered magnet on the other side of it to force the switch into an open state when the door is up.
However, since it looks like these guys (Linear) caught a C+D, I’m returning it to Lowes. Not worth the effort on a dead end device
We have plans to integrate it. I have the device in the lab. Whats holding us back right now is we are missing a Z-Wave Movable Barrier Command Class. It is a specialized message that adds security onto it. We need to get that added before we can integrate it.
The lame support answer I can give for a timeline is, we have so many things that are high priority and since this will take a platform dev, it kinds pushes it out to a month or 2 timeline.
@urman has there been any progress on the implementation of the z-wave Barrier Operator Command Class? Itching to get the GDC integrated into ST. I have a first cut of a device type, just need that pesky command class.