Discontinuation of MyQ Connect Community SmartApp

[Passive (David Jones)]

They are one and the same…

[ashutosh1982 (Ash / Ashutosh Jaiswal)]

@Passive

They are one and the same…

Thanks for the clarification. Thats what I thought .

[schapper05 (Jason)]

This is extremely unfortunate.

Short version: I’m upset.

Long version:

@jody.albritton

SmartThings is working directly with Chamberlain to officially bring MyQ garage door openers

By working with I think you mean negotiating. Partnership team = sales team.

You’ve been ‘working on this’ since the beginning of time. What possibly reason is there to believe a statement that it’s officially coming?

Do I need to change out 4 garage door openers and buy a relay kit if i want them integrated into ST

IMO shit, or get off the pot. Stop with the false hope it will only make others purchase into something you aren’t seriously planning on.

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@schapper05

Stop with the false hope it will only make others purchase into something you aren’t seriously planning on.

Isn’t that SmartThings business as usual?

Seriously… I think SmartThings sincerely “plans” a lot of stuff / features and even puts a lot of effort into it. But intention != result.

[schapper05 (Jason)]

@jody.albritton

No question. The unofficial integration is currently generating upwards of 1 million errors every day so it is not only a source of frustration for customers who use MyQ, but it’s a source of frustration for us as well.

Conspiracy anyone?

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@schapper05

Conspiracy anyone?

Besides the wild speculation I posted? … What do you imply is the “conspiracy” and what evidence?

Oh… This has some history: (March 10th…?)

[WITHDRAWN] MyQ LiftMaster/Chamberlain

We know that 2100 customers have the code that is generating the errors. We are making a plan for how to message those customers and alert them that there is an updated version. I am completely sympathetic to your situation and the situations others are experiencing, but this is not a technical hurdle for us. It’s a business agreement that has to be put in place. If the Chamberlain API were open we would have had official integration long ago.

So I responded in that thread…

[WITHDRAWN] MyQ LiftMaster/Chamberlain

I guess it would have been courteous of all involved parties to try to give some advance notice before pulling the plug. The ideal situation would have been to have a replacement official handler in place before pulling this Community one, donchathink. This didn’t become a problem overnight! This Topic (and DTH) was launched in January 2015, right? That’s nearly 1.5 years for this to have been detected and resolved more cleanly. Technical issues will exist and old code will be discovered to be inefficient / resource intensive / platform impacting; but if SmartThings and Chamberlain wish to have “world class” and “consumer friendly” products, then partnership protocols have to be thought out in advance to deal with these issues on a business-to-business level. Regardless of who initiate…

[scottinpollock (Scott)]

We were told we would get an official integration “soon” almost a YEAR ago!!!

The fact that the most purchased garage door brand is still not supported, and that the most connected light on the planet is still in labs after more than two years, says a lot about this company’s ability to ‘get things done’.

It is simply mind numbing.

[Mbhforum (Marc)]

Wow. This is disappointing. I recommend we all also put pressure on MyQ to get an official integration done as well. Both parties should want this equally. This isn’t Smartthings fault but it is. MyQ is pretty much the only commercial game in town for garage automation and folks like Nest and Wink have this working officially, but yet ST hasn’t gotten it done. The bad thing is IFTTT, Yonomi or Stringify doesn’t integrate with MyQ either so we literally have no work around. Can someone please correct me here if I am wrong?

Wink just looked a lot better today

[Derrek113116 (Derrek Krasnicki)]

Well it’s 5/6 here 6am and mine still works:grinning:

[LadySapphy (Megan)]

yea this Times 365. MyQ + ST was one of the major needs that got me sucked into the HA rabbit hole. I am getting tired of all the hollow promises about stuff from ST.

So we lost RM, Now we loose MyQ, what next? Are they going to kill the nest manager? Maybe kill of SmartTiles?

[pstuart (Patrick Stuart [@pstuart])]

Wow. Not being a user of this, but this sets a very disturbing policy. Instead of fixing the app, blocking it.

Sure it probably violated my q TOS. But if it’s open, then St should allow it. My q should shut it down not St.

This is a very slippery slope. So much for an open platform. Guess this is the start of the guard rails?

[schapper05 (Jason)]

@Mbhforum

put pressure on MyQ to get an official integration done

I don’t think that MyQ/Chamberlain is where the issue lies. I believe that ST doesn’t want to pay for the API access.

[SBDOBRESCU (Bobby)]

I think you are right about the era of ‘guard rails’ is here!. They have been whining for a while that this integration is resource intensive.

BTW, thanks for asking Robert and Alex for the local processing and pressuring to get a concrete answer…

[schapper05 (Jason)]

@pstuart

St should allow it

I don’t think (at least I sure hope) that ST didn’t shut down the code on their side. To me it sounded like @copyninja withdrew the app so that new forum members weren’t confused when it didn’t work. He left it available on his GitHub.

[tonesto7 (Anthony S.)]

I know it’s all in humor but alexa works better than I imagined through the outside wall. So I can see how this could be an issue. They still should at least give us the option at least if we want to ignore the risk.

[schapper05 (Jason)]

@tonesto7

So I can see how this could be an issue.

Have you seen @N8XD’s project video where it adds the additional security layer? Pretty neat, Although I’m not sure how secure it is yelling your password either - I would probably use it for a garage door (Door to the house from garage kept locked)

AskHome - Alexa/SmartThings programmers kit. Alexa can do anything

Hi Guys, In real life you view your home as a structure filled with rooms, people, and objects. This kit helps you use Alexa to interact with your house by talking about those things - and not a list of devices. …which is great if you are helping someone non-technical make a smarthome. This is not a supported release, but a “share”. I’m sharing what I’ve done, and giving you the code so you can try it yourself if you want. Here is a short video with a few sample interactions from my home - and the kit code: documentation, smartApp, cut/pastes for alexa skills and lambda is here – https://github.com/n8xd/AskHome. The demo code is configured to work with some things at my house…to make it YOUR AskHome, you’ll have to program your house into it. The AskHome kit is for groovy pro…

[pstuart (Patrick Stuart [@pstuart])]

Where one door closes another opens. More reason everything should be local. Someone should just spin up a rPi and a node.js relay.

Send a command to the rPi and have the rPi open/close the door via their api.

If ST shuts down the connection outbound, you can always get around it locally. At least until Chamberlain starts blocking all ips.

If Chamberlain would have just implemented a proper API, this wouldn’t be an issue.

And if ST had proper error logging and the ability to stop an app after it gets x errors and warn the user.

Wonder what will be next?

[tonesto7 (Anthony S.)]

Well at least I can still use homebridge for this in a pinch

[copyninja (Jason Mok)]

@pstuart

Wow. Not being a user of this, but this sets a very disturbing policy. Instead of fixing the app, blocking it.

Sure it probably violated my q TOS. But if it’s open, then St should allow it. My q should shut it down not St.

This is a very slippery slope. So much for an open platform. Guess this is the start of the guard rails?

@jody.albritton

Chamberlain has informed SmartThings that they can no longer allow access by this SmartApp, and has closed the IP address it uses.

I know many are dissapointed. I am too. Please don’t add salt to the wound. MyQ is the one shutting it down, not SmartThings. This thread is just to announce that it doesnt work anymore.

@pstuart

Where one door closes another opens. More reason everything should be local.

Perhaps @brbeaird will take up this challenge like he did with RainMachine.

@pstuart

If Chamberlain would have just implemented a proper API, this wouldn’t be an issue.

This is the exact reason that everything isn’t efficient.

@schapper05

I don’t think (at least I sure hope) that ST didn’t shut down the code on their side. To me it sounded like @copyninja withdrew the app so that new forum members weren’t confused when it didn’t work. He left it available on his GitHub.

I withdrew it because of this thread.

[chevyman142000 (Jeff DeWolfe)]

Thanks for letting us know Jody. I appreciate that. I am, however, pretty frustrated by this. I don’t understand how getting a partnership for this has taken so long and is STILL not ready to go. People have been asking for this for quite a while and it has always been said that ST is working on it.