email@example.com - the CEO who was kind enough to give me his email address on Twitter when I hijacked their marketing… He hasn’t acknowledged my email, so may appreciate a few more users dropping him a line
Hi there, I’m also trying to connect and not getting anywhere. Are there any updates on this that anyone knows of?
Guys. Can we keep this thread clean, or ST may think we forgot about the problem. BTW how’s fixin’ going?
Guess you just joined… the latest info , such that it is, is all on this forum if you have a look around. I don’t think SmartThings will think we forgot !!
I regard this thread as pretty much the OAuth topic - and therefore any temporary workarounds seem pretty much on topic. The fact that it’s titled IFTTT was just the first of many things that are broken without OAuth. SmartTiles, LIFX etc. I hope people find the content useful in that context. However separate threads on workarounds could be created and linked from here if the moderators prefer, which might be tidier ?
Discussion of individual device types or other workarounds should be given their own thread with a post placed here linking over to it. Code discussions and troubleshooting can then be referred to that thread.
One of the best things about SmartThings is that it is not limited to a kit of fixed devices. With the exception of the hub, everyone has different set ups. So to keep the forums easy to use for everyone and interesting, anything on a detailed level which is device or model specific needs to go into its own thread. Not only does it keep this thread cleaner, it makes it much easier for people coming in new to the category to find those specific device types and workarounds.
The people working on a workaround for Netatmo for the UK have been doing this very successfully, for example:
Thank you for your help in this regard.
We are close. I am sorry that we have been quiet on this but I am going to provide you guys with insight as soon as I have something more to share. It shouldn’t be to much longer.
I am writing the documentation as we speak
Thanks for the update @slagle - sure would be nice to actually get this working soon!
Thanks Tim, it’s appreciated. When we say close, are we talking “oh, I can see the port over there” close, or are we talking “Yep, we’ve just got to get past Greenland on our rowing boat, at least we’re nearer the UK than America now”
Alex was expecting it next week… That was a week and a half ago… I hope Alex isn’t getting too stroppy with the development team…
Nice - hurry up
So, it looks like this might be working now, been able to authorise properly but yet to try a routine out! Other apps now have my hub showing correctly where they didn’t before and I no longer have to log in twice…
I just authorised it using a web browser through the IFTTT website, IFTTT now shows as a smartapp within SmartThings and I could select all the devices I wanted to allow it access to. I’m on iOS9. When you sign into the SmartThings site now (graph.api.smartthings) you no longer have to click on locations and sign in a second time it automatically logs you into the eu site
Trying to get SmartRules to work but I’m now stuck at the next hurdle, it says “Client is not associated with a SmartApp in location XXX” which is an improvement over having no locations but still doesn’t help much.
IFTTT still can’t access my devices!
Just tested this! It WORKS!
Have you actually got something working, any recipes I try can’t actually access the required devices so close!
Never mind… Jumped the gun! Hit the same snag you did!
EDIT: I have also noticed that it is now actually authentication against the US server, which must have some kind of federated authentication over to the EU servers.
Getting there ST, I have to give you that!
Once you guys have authorized the SmartApp, what happens if you open up the SmartThings mobile app and attempt to edit the list of authorized devices for the SmartApp from there?
I still get the Problem accessing your xxx sensor message
This doesn’t look good. I’ve Just tested with:
LIFX - Fail, doesn’t even start the smartapp
SmartRules - Fail, comes up with error "client is not associated with a SmartApp in location"
Amazon Echo - Fail, comes up with error "client is not associated with a SmartApp in location"
IFTTT - Fail, connects but cannot access sensors / actuators / devices
Lets all be honest though, we have all jumped on the band waggon of “It’s working!” Even before anything has been announced -
Either that or we’ve just beta tested the fix and found a law already.