If your use case only involves different locations for the trigger side, you should be able to use any alternative presence locator that has an IFTTT channel and use that one to trigger off your office presence. It doesn’t have to be one that integrates directly with ST. You can even just use the IFTTT android location or IOS location app as the trigger.
You can’t control devices at multiple ST locations through IFTTT, but you can definitely have different IFTTT channels trigger devices at one ST location. So if all you need is geopresence somewhere else, you should have several options.
As @Kermee points out above, a work around is to operate two ITFFF accounts and two ST accounts with a hub on each account, however that defeats the purpose since we cannot be logged into ST on a mobile device with two different sets of accounts.
Does anyone have or know of any updates to this issue? Got the same problem here…
Sadly, when this thread started back in 2014, there was a workaround : it was possible to attach multiple hubs to the SAME location (using the IDE). It was not officially supported, but it did work.
Unfortunately, with v2 Hub introduction, ST decided to outlaw this option, which for me created a huge regression since I was only using multiple hubs because of too long distances between hubs and devices within the same location.
I fought madly with ST Support to restore this multiple hubs/single location option and got nowhere, although it had been working perfectly.
Unfortunately, and it is a pity for such a promising kickstarter project, ST does not seem very interested in feedback from early adopters; when ST Support answers “forwarded to the development team”, it could as well write “pushed into the nearest black hole”… .
And to tell the whole truth, many early adapters, including myself, are not very interested in ST anymore, considering the huge stability issues, and the tons of unresolved bugs…
And multiplying the constraints of one cloud (ST) with the constraints of an other (IFTTT) can only make it worse.
Excellent question… We must be several hundreds (thousands) of SmartThings early adopters looking for such an alternative.
The problem is that “the devil is in the details”, and that to reach the 99.999% reliability level needed for trouble free Home Automation, you need to take care almost of ALL the details, WHEREVER they are in the chain.
And then there is the price vs functionality issue…
The bottom line is that you will NOT know a home automation will work adequately for your specific needs until you have “played” with it multiple months, AND on a large enough scale : the error rate which is acceptable when you have only a few Devices could very well be UNacceptable when you move to several dozens of them !.. as I did learned painfully .
The tentative and partial conclusion I have reached at this time is that a 99.999% reliable system is likely INcompatible with a too open, too young, cloud based, system… unless the same company controls all the components along the way, either Hubs, Devices or cloud. And even in that case, you will have all the vagaries of Internet TC/IP connections, a technology designed more than 30 years ago by the Pentagon in a “fire and forget”, “let’s survive the next nuclear war” spirit…
At that point, for local operations, I would likely recommend FIBARO, which has strongly impressed me with the great engineering quality of its products.
And for a cloud based solution, I would look into Apple’s HomeKit, although they are currently very limited in number and type of devices supported; but that will improve in the next 12 months.
In the meantime, as long as you do not require high reliability, SmartThings has a reasonable price to “play” with Home Automation… and learn yourself, the hard way, all its present limitations.
But do not build anything “mission critical” on top of that, that would be like building a skyscraper on top of a quagmire…
Currently, IFTTT and other integrations like Google Home and Alexa can only be installed on one account. This is a limitation of both SmartThings and also IFTTT/Google Home/Alexa. At the moment, the only way to authorize IFTTT is to set up each Hub on a separate email account for both SmartThings and also IFTTT. While IFTTT may be able to see each location since they are tied into the same email IFFF lacks the logic necessary to differentiate between locations. So if you triggered the applet in IFTTT it would randomly select one of those locations as it is not capable of being able to select a specific location, even though you selected a specific location. This is why you would need to have the separate accounts.
If you wanted to do this you would need to Factory Reset one of your Hubs and set it up in a separate SmartThings account as well as a separate IFTTT account. I apologize for this inconvinence. We would love to be able to offer multiple location access to these services and I have added this as a feature request on out internal page on your behalf.
Well, I recently switched to a Samsung account for SmartThings. When I went to authorize my 2 St Hubs in Ifttt, it shows both locations and I was able to give authorizations for all devices on both hubs.
However, the problem now is that when I go to create a trigger using a switch at one location and have it activate something else, my first location’s (hub) that I had with Ifttt before I got the second one, is the only device list that shows. The other devices don’t show up in the list. I’ve already made sure devices from both locations were added using graph.
I was hoping I could use a siren as a trigger to activate a siren on a different hub using IFTTT. Apparently that’s not gonna happen unless I can get IFTTT to list the other hubs devices. I figured once I was able to list both, that would be an option. Guess not…
First, IFTTT will need a different SmartThings username/password for each location. To create a unique username/password for any given location, setup a dummy SmartThings account and then share the location with it.
Next, each IFTTT account can only handle one SmartThings username/password. So you link locations by linking multiple IFTTT accounts.
To link IFTTT accounts, use webhooks. In the “then that…” account, initiate the recipe with “Webhooks”. And in the “if this…” acount, the recipe should call that webhook.
Awkward, maybe. But it works. Using these two tricks, a condition at one location can trigger an action at another.
I have a second location with two Blink camera systems: one for indoor, one for outdoor. I want them both to turn off when I arrive and on when I leave, and additionally I want the outdoor cameras on when that location switches to Night mode when I’m there.
It turns out that TP-Link / Kasa devices show up on both locations when added to one. I have a Kasa 3-outlet power strip. This has three individually controllable outlets. I named one Indoor and one Outdoor (I’m currently not using the third). These devices show up on both my Smartthings locations: the location where the strip is plugged in, and my other (regular home) location, which is the one that’s linked to IFTTT. I then added triggers through IFTTT to switch on or off the Blink systems from my home location, which reports the same status as the location where the power strip actually is.
I’m assuming at some point either TP-Link / Kasa or Smartthings will realize this anomaly and ‘fix’ it, but until then, there’s your solution. The powerstrip was on sale for about $20, and just for good measure I plugged non-sensor LED nightlights into the two ‘security’ outlets as control lights. Those were $4 for two.
.
.