Discontinuation of MyQ Connect Community SmartApp

Just pure speculation here, but it might also be a problem where ST is ready and willing for an integration but Chamberlain isn’t.

From my experience based on a few products I am trying to get integrated with smartthings before release, a lot of manufacturer’s have this weird notion that everything should only be controllable by their own platform and software and hate the idea of it integrating with other things since they view it as providing an added benefit for someone else. It’s mainly an issue I am seeing with older manufacturers of systems that are recently getting smart additions. ITS A GENERAL PAIN IN THE PROVERBIAL ASS.

As an example, we currently have a Z-Wave enabled product that’s ready to ship at the end of the month, but the manufacturer doesn’t have proper device handlers for smartthings. I have requested some documentation to make it ourselves but so far I am jumping through loops… pretty massive ones. I might end up having to reverse engineer the commands. The additional problem is most of the people in charge of the department, or represent the departments that add these smart addtions themselves don’t understand a lot of how they work. So they stick to what they know or what their IT guys tell them. :sob:

2 Likes

The main reason I don’t see how this applies here is MyQ is already officially integrated with Wink.I don’t see why ST can’t get the same deal.

1 Like

This is very important to my setup, not good news! Two questions, and I am afraid to even ask the first one as I hope if it is an over thought someone doesn’t go back and fix it.

  1. For those of us who use this app for lets say, another brand (different IP), will that also be discontinued?

  2. What is the TENTATIVE date for the official SmartApp?

Ok, didn’t know that.

Can be any number of reasons at this point. Issues with the ST platform itself, or Chamberlain requires something in return from ST which ST cannot provide, or maybe even an internal exclusivity agreement (or as I call them the anti-innovation agreement), who knows but the way Chamberlain proceeded with the discontinuation was atrocious. Atleast a few days warning should have been given; waking up one morning to find my Garage doors not working is not something I would look forward to.

1 Like

No Tentative dates as of yet. In terms of the different IP’s I have no idea, hopefully someone else does.

It’s the battle of egos. The game of I-can-control-you-but-you cannot-control-me game. AKA I have bigger balls than you. If companies would lower their egos, we would have the interoperability that HA needs, until then we need to deal with fragmented platforms before one company grows its biggest balls and every other company would want to join the club.

1 Like

For the same reasons they ‘cannot’ get Nest integration, because they refuse to play their game… I rub your back if you rub mine.

2 Likes

Possibly… but this blew up previously quite some time ago. Perhaps Chamberlain is simply annoyed at this point. Clearly SmartThings is incapable of working with them for whatever reason.

So a bunch of folks are using SmartThings for unauthorized access to their system, in violation of their terms of service (yes, I read them). What would you do if it was your system being affected under these circumstances?

Well, from my point of view it looks like there is a fairly significant user base that is using it, so it’s always courteous to provide some warning or notice, primarily providing enough time for people actually to be aware of it and at least switch everything over.

1 Like

Agree with this point. Not sure why they couldn’t open up an IFTTT channel or something similar. Instead of running high pole rates they could just trigger on an event (open, close, light) and then they allow for the openness we are looking for but by their rules. This one seems to fall evenly on both companies, at least IMO.

This would cost Chamberlain money. It seems to me they are trying to Make money from their closed API’s. They don’t have interest in it because there isn’t direct income from it(even though they may make indirect money from increased sales, but this is hard to track)

Update - this doesn’t work :frowning:

Here’s a potential workaround - Smartthings -> IFTTT -> Wink (no hub needed) -> MyQ

  • Install Wink app and link it to MyQ (No Wink hub required and app is free!)
  • Create Wink Shortcuts to open and close MyQ garage door
  • Link Wink to IFTTT
  • Create Virtual Switch(es) in smartthings
  • Use Smartthings Virtual Switches to trigger Wink Shortcuts that open/close MyQ

Boom!! Done!!

I’ve had a tilt sensor on my garage door to get instant status in SmartThings. This is probably still going to be necessary in the near term, but I think this solution will work as long as all 4 clouds are working.

3 Likes

Have you tried this? MyQ shortcuts via Wink don’t show up in IFTTT

This sounds great, but I’m not finding a way to actually do it.

Yup, I’m seeing that as well :frowning: It was good idea I suppose…

Can you do a shortcut that would trigger another shortcut?

1 Like

Unfortunately no…

Good thinking, but it looks like you can only run robots from a shortcut, no other shortcut :frowning:

As of right now, ST/MyQ still functions for me. Has it actually quit working for anyone here?

Hey @SBDOBRESCU! Bobby just place the MyQ shortcut next to ST on your phone. Works like a charm! :wink:

1 Like