Problems connecting from IFTTT (February 2017)

I recently bought my first SmartThings hub (v2) in a kit with two lightify a19 bulbs. So far everything is working great and i can control the lights from the app or my Google Home. However I also wanted to try integrating with IFTTT --but every time i try to connect from ifttt it fails.

I’m going to https://ifttt.com/smartthings where I click connect, enter my ST credentials and then get a screen where I select my location and get a list of devices. I check my bulbs under switches and click authorize. And I get message on the next screen that says “Could not connect SmartThings” and ifttt doesn’t let me use SmartThings in recipes – it acts as if I’ve never logged in. I can see IFTTT under Smartapps now in the app on my phone too, but again IFTTT acts as if it can’t see anything.

Any idea what is wrong or how to debug this?

Quick gif video of what happens when I try

4 Likes

Contact support at https://support.smartthings.com/hc/en-us

It’s an issue reported the day before yesterday.

3 Likes

Thanks, I contacted support. I didn’t realize this was a known issue.

1 Like

Well it’s pretty new (from what I know).

2 Likes

Having the same problem :dizzy_face: I’m really close to returning my brand new ST hub and pulling the good old perfectly working wink hub! :triumph:

This what everyone is experiencing?

2 Likes

Yes, that is exactly what is happening.

1 Like

Same problem here. Thought that IFTTT and Google Home might be fighting over “automation rights” because I can voice control the lights w/o IFTTT (which I didn’t expect to be able to do). But I would rather use IFTTT b/c it is much more flexible. I also have a harmony hub which has connected to IFTTT and Google Home without issue. Hope the context helps!

I’m having the same issue. Any updates on the progress of this?

1 Like

@slagle or @Tyler or @Aaron can you provide any feedback on this? It seems to be affecting a few users at this point.

1 Like

We are looking into this. Please contact support with your SmartThings and IFTTT email addresses (if different) so we can investigate. Thanks!

2 Likes

Hi, I’m having the same issue.

I’m also experiencing this issue. Your GIF matches my experience exactly. Good to know I’m not the only one!

1 Like

I’m having the exact same problem with my ST hub I just bought. I’ve submitted a help request with support, hopefully it’ll be resolved soon!

1 Like

I don’t get any notification. after I authorize it goes back to the recipe in the off position. i click it on and i go through the whole routine again. It does show up in the smartthings app (it is a door lock) though. I am trying to get the door to lock through alexa.

1 Like

Exact same problem here. Opened an incident with smartthings.

1 Like

Thanks for making the gif – it makes it easy to confirm that our experiences match exactly.

An additional data point… when I go back to my SmartThings iOS app, it clearly shows a connection to IFTTT, and I get the familiar, granular permissions page.

However, upon going back to IFTTT to use the SmartThings device, it says I am not connected, and we’re back to your gif.

I’ve submitted a case to add to the tally.

1 Like

Hello again, is there any expectation as to when this will be corrected?

Thanks

I have the same problem as well. New to ST and IFTTT connectivity was one of the main reasons to get ST. I also have (2) 8 series TV and they can’t connect to ST either. That’s (2) strikes against ST for me. Hoping it is an easy fix for ST dev. It seems like IFTTT is setup to use the OLD api endpoints for Hub v1?

Old:::
https://graph.api.smartthings.com

New:::
https://graph-na02-useast1.api.smartthings.com

I also see a lot of null pointer / number format exceptions in the API logs as well.

Rob

I sent in a request to support today, with plenty of screenshots as well. Hope it helps!

1 Like

© 2019 SmartThings, Inc. All Rights Reserved. Terms of Use | Privacy Policy

SmartThings; SmartApps®; Physical Graph; Hello, Home; and Hello, Smart Home are all trademarks of the SmartThings, Inc.