Delay times of more than 60 minutes for automations in new V3 app?

[Vinlo (Gavin Lock)]

I recently migrated to the new app and have a problem with one of my automations. Before I have it set that if it was in away mode for more than 12 hours it would switch to vacation mode (lights would randomize, thermostat would turn down, etc). With the new app the highest delay I can seem to specify is 60 minutes. Am I missing something on how to do this? I currently have is set to be;

If away, home, night and specific person is gone for more than 60 minutes then run scene i’m on vacation.

It used to be if mode was away for more than 12 hours run i’m on vacation, but I can’t figure out how to do that now.

I am sure it’s far more simple than i’m making out to be but I just can’t figure it out. Any help is greatly appreciated.

[GSzabados (Gabor Szabados)]

It is a know issue.

Unable to extend time away longer than 60 minutes

In the old app I had a routine that changed my mode to traveling if I was away longer than x hours, the advanced option in the member location in automatons has a max of 60 minutes

Sunrise/sunset setting now only has max 60 minutes, used to let you choose HOURS

I understand you had numerous Routines with offsets greater than 60 minutes. The new app only supports offsets up to 60 minutes by design. I passed along your feedback and frustration but don’t have any insight into that decision. I assume you’re referring to this device: momentary-button-tile.groovy. If so, the metadata needs to be updated. This might serve your needs:

[GSzabados (Gabor Szabados)]

@nayelyz, @erickv

Does the Rules API support hours to do automations like the OP asks?

[Abhijeet_Ghosh (Anonymous)]

@Vinlo I know it is a clunky workaround but have a virtual switch be delayed 60 minutes, which triggers an automations that turns on another virtual switch after 60 minutes, and so on. After the needed time is reached, just have the last virtual switch trigger the final action

Or just use webcore

[jkp]

You can use webCoRE as a temporary means until the current max of 1 hour delay is resolved in automations

[GSzabados (Gabor Szabados)]

@jkp

You can use webCoRE has a temporary means until the current max of 1 hour delay is resolved in automations

Will that be ever resolved? Now the most important is to add the Samsung Find feature, what has nobody asked for…

If WebCore, then Sharptools.io 's Rule Engine should do the job as well.

[Vinlo (Gavin Lock)]

I’ll have to stumble through Webcore… seems simple enough, I hope (I’m not that skilled).

[orangebucket (Graham)]

@GSzabados

Will that be ever resolved?

I guess it depends on why the restriction is there.

Possibilities include:

• Someone has decided that no one can possibly need a time delay or offset of over sixty minutes.
• Someone thinks it looks prettier only going to sixty minutes.
• Long delays and offsets in some way contribute to something that is bad happening, such as the frequent timer issues we see.

[rontalley]

@Vinlo

I’ll have to stumble through Webcore… seems simple enough, I hope (I’m not that skilled).

There’s a Wiki and a booming community. IMHO, webCoRE is the answer for most of what I see posted here. It’s just a freaking awesome Rule Engine. Very easy to used once you understand the basic concept.

[nayelyz (SmartThings Developer Support)]

Hello @Vinlo,
The Rules API is another option, in the time properties such as sleep you can use bigger units like Hour or Day.
The example below describes this workflow:

1. IF the location mode changes to Away
2. THEN wait for 1 hour and check IF the location mode is still Away.
3. IF so, THEN change the location mode to Vacation.

{
   "name":"Change Location mode after x hours",
   "actions":[
      {
         "if":{
            "equals":{
               "left":{
                  "location":{
                     "attribute":"mode"
                  }
               },
               "right":{
                  "string":"away-mode-ID"
               }
            },
            "then":[
               {
                  "sleep":{
                     "duration":{
                        "value":{
                           "integer":1
                        },
                        "unit":"Hour"
                     }
                  }
               },
               {
                  "if":{
                     "equals":{
                        "left":{
                           "location":{
                              "attribute":"mode"
                           }
                        },
                        "right":{
                           "string":"away-mode-ID"
                        }
                     },
                     "then":[
                        {
                           "location":{
                              "mode":"vacation-mode-ID"
                           }
                        }
                     ]
                  }
               }
            ]
         }
      }
   ]
}

This rule needs the location mode IDs, to get those values, take a look at this post.

SmartThings API: Listing location mode

Have you tried this? https://api.smartthings.com/v1/locations/{locationId}/modes You also need the proper scopes on your token (modes)

In the API documentation, you can find more information about the Rules’ syntax. Refer to this post for the instructions to install a rule.

Run pump x min on, x min off on continuous loop?

Hi, @mpnret You can create your Rule Automation using either Postman or Insomnia. Personally, I’d suggest you to use Insomnia, as it has a simplier and intuitive UI to perform your API calls. Please, follow the steps below: First, you must create a Personal Access Token that you’ll be using at your Requests Headers to the SmartThings API. Then, you must get the list of your devices making a GET HTTP Request at the SmartThings Devies API and track your GE SmartSwitch’s Id. Finally, update the JSON file from above with your GE SmartSwitch Id and make a POST Http Request to the Rules API. I hope this information results useful to you. Best regards, Erick.

If one of the previous posts answered your question, would you please mark it as solved? If you still have doubts or issues, let me know what’s going on and I can dig in further.

[jlv]

@nayelyz

If you still have doubts or issues, let me know what’s going on and I can dig in further.

Can we get a statement on why automations are limited to offsets of +/-60 minutes?

[Vinlo (Gavin Lock)]

I was able to get it working through webcore, although in doing that I somehow screwed something up and am now no longer to see the dashboard “there was a problem loading the dashboard data…” error. I just can’t win today. lol.

I’ve been trying to fix that problem now for a while, to no avail.

edit: I get the error in live logging
“physicalgraph.api.StatusCodeException: Invalid http status code returned: 401 @line 950 (api_get_base_result)”

Maybe I need help from @webCoRE_Minions ?

[Monique]

I have not used Webcore, I’ll take a look at it

[GSzabados (Gabor Szabados)]

@Monique, look at this as well:

Delay times for automations

Whatever is easier for you. But really adding a rule with more than an hour option shouldn’t be that complicated.

[Monique]

Thanks forthe reply and feedback, for now I am approaching the logic in a different way, however it would be great to have this functionality restored.