For me I cannot even open the unknown device type at all. The entry after front patio switch. Clicking on it does nothing. Of course looks like the garage door name is missing here…Aah!
On Android, it opens the device to a blank screen and says something like “could not get blah blah of device %s”; at least that is my recollection of yesterday’s fun with SmartThings.
Mine open’s fine, but I know I’m using a different device type. Just for data.
It’s still failing, and I’ll let you know when I see it working (when I can check, at least a few times a day).
Folks, what if MyQ changed their API/access method? This won’t fix itself if so. How could we tell? @copyninja, pulling you in, thoughts?
The failure is grabbing settings.property like “settings.door_name”. You cannot even install the device type anymore. Grabbing settings I would think is in ST land. Trying to update the device will throw the something went wrong happened error.
It’s probably because that is null, and I’d bet that’s because ST can’t talk to MyQ. It’s clearly ST, but where the issue is is another thing.
I’ve put in a ticket. I’m glad I have a backup tilt sensor to see the real state of the door, but this might be failure number three for me in the past two weeks pretty soon.
There is no official API. My recollection of how the original deviceType was penned was @essidle sniffing out what the official app or web interface was doing. I think if that changed it would break the official app (which hasn’t been updated in months). Plus experience has taught me that if something is broken, 99 out of a hundred times it’s SmartThings.
Just (re)installed the app - v4.06 - I already had the two device types installed from before and mine works fine (apart from the usual error @ line 261…which was discussed on My Q release thread)…
Actually even with the error, I think mine was working now that I dig in. I verified the open and close times. I wonder if the app is just retrying a lot and getting enough statuses to update.
MyQ has changed their API quite a bit. Original @essidle’s could break anytime, in fact I noticed that changed at least 2 times on some of the attributes in the JSON. The version I have uses latest iOS app’s API.
ST folks are looking into this. However, I can’t really confirm this but I’m suspecting MyQ had either blacklisted ST servers or they have deliberately put ST on a lower network quality of service because of the high volume of request sent to MyQ. If I redirect the traffic through a proxy, it works well without seeing errors.
1 Like
Or the Australian Government doesn’t like their server spammed as well anymore… 
This should have been removed, I guess. I am sure this is not the issue but well… this is not right as well.
def sleepForDuration(duration, callback = {})
{
// I'm sorry!
def dTotalSleep = 0
def dStart = new Date().getTime()
while (dTotalSleep <= duration)
{
try { httpGet("http://australia.gov.au/404") { } } catch (e) { }
dTotalSleep = (new Date().getTime() - dStart)
}
//log.debug "Slept ${dTotalSleep}ms"
callback(dTotalSleep)
}That hasn’t been in my deviceType for over a year. I stripped out all of the timing stuff and the incessant pings because it was janky, and no longer necessary given the operation of the door being monitored by the multi.
Your suspicions, if true, would really be a shame. @Ben What happened to the official MyQ integration that was supposedly coming soon (back around last Spring/Summer)? I have asked about this several times since then; why the silence? Please update us so we can decide to wait or move on to another solution.
I don’t know about others, but managing my garage door (in association with presence sensors) is one of the single most important reasons why I continue to use SmartThings
We do believe this is the case and are working with MyQ to resolve a short term fix prior to a full integration. There are few technical reasons the official integration has stalled. It is mostly about the partnership and business aspects at this point. And while I realize when pointing a finger at someone, three are pointed back at us, but in this case I’ll still do it.
The officially supported Linear device works great.
3 Likes
This kind of information is invaluable, thank you @Ben.
Thanks! What can we do to be sure we will be informed when this fix is in place.
Finger pointing is fine, I get it. They have set up some hurdles on your track. So you’re saying SmartThings can’t compete with “Wink” when it comes to establishing business relationships? That doesn’t exactly bode well for the future. Why can Wink get it done and not SmartThings? Really would like to know what the hangup for SmartThings is. This has been going on for an awfully long time, and your response still has me feeling that this may never be permanently fixed. Please give us a bit more to the contrary.
That, and $5 will get me a latte at Starbucks. (c;
Chamberlain has a few requirements that we are uncomfortable with. I am not going to get into them but Wink violated one of them and was sued. We are being cautious.
1 Like
Fair enough. I’ve modded things here to just get notifications, and will use the Liftmaster app to open and close, pending some announcement from you guys.
Mine is working and has for the past year.
When/where was this suit filed. I did a little research and only turned up a patent infringement suit against Linear. 0c: