# Changes to device delay settings in Routines

**URL:** <https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451>\
**Category:** Features & Feedback\
**Created:** [July 1, 2025, 12:29am UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451 "2025-07-01T00:29:41Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![rbendell](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@rbendell](https://community.smartthings.com/u/rbendell)\
**Post date:** [July 1, 2025, 12:29am UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/1 "2025-07-01T00:29:41Z")

</div>

I’m trying to understand why Smartthings made the changes to device delays in Routines. If there is a ‘real’ reason for this change, WHERE was the notification posted? Thank you.

---

<div class="post-metadata">

**Author:** ![jkp](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/jkp/32/117130_2.png) [@jkp](https://community.smartthings.com/u/jkp)\
**Post date:** [July 1, 2025, 12:57am UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/2 "2025-07-01T00:57:50Z")

</div>

The App Store would have shown a description of changes.

---

<div class="post-metadata">

**Author:** ![mocelet](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/mocelet/32/195631_2.png) [@mocelet](https://community.smartthings.com/u/mocelet)\
**Post date:** [July 1, 2025, 5:06am UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/3 "2025-07-01T05:06:43Z")

</div>

> [@rbendell](#):
>
> I’m trying to understand why

The “why” is usually not explained, but in the SmartThings app Menu tab there’s a section called Notices where it communicates important changes like new features, end of support for Android versions, etc.

The delay feature is good to have but think twice before using it, most of the time you don’t want a delay but a “keep this state for a certain time”, especially for auto-offs, motion sensor routines or even a sequence of actions spanning a long time. A routine with a delay cannot be canceled and may have side effects. “If plug is on, wait 5 minutes and turn plug off” is not the same than “if plug is on for 5 minutes, turn plug off” which is usually the intended behaviour.

---

<div class="post-metadata">

**Author:** ![rbendell](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@rbendell](https://community.smartthings.com/u/rbendell)\
**Post date:** [July 1, 2025, 3:41pm UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/4 "2025-07-01T15:41:13Z")

</div>

I frequently use delays within a routine. I live in Florida and have a cabin in Michigan. I find it very useful to have lights go on and off in areas of my house to help it look like someone is home. The first night after the change, even though the notification said that the change would not affect my setup, it did. I’m just trying to understand the purpose of the change…

---

<div class="post-metadata">

**Author:** ![wags1](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/wags1/32/151348_2.png) [@wags1](https://community.smartthings.com/u/wags1)\
**Post date:** [July 1, 2025, 6:41pm UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/5 "2025-07-01T18:41:24Z")

</div>

Do you have to change current routines that use a delay? I currently have 2 routines for bathroom fans. When you turn the fan on the routine turns the fan off 7 minutes later. Both routines currently work perfectly for thier intended purpose.

---

<div class="post-metadata">

**Author:** ![orangebucket](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/orangebucket/32/81590_2.png) [@orangebucket](https://community.smartthings.com/u/orangebucket)\
**Post date:** [July 1, 2025, 6:54pm UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/6 "2025-07-01T18:54:48Z")

</div>

> [@rbendell](#):
>
> I’m trying to understand why Smartthings made the changes to device delays in Routines.

What changes are you seeing? I am aware that they have _added_ the ability to add explicit delays between actions in Routines, but I am not aware of any changes to the functionality that already existed. I am not clear how that would even be possible without changing the functionality of the rules engine which would be unforgivable.

---

<div class="post-metadata">

**Author:** ![wags1](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/wags1/32/151348_2.png) [@wags1](https://community.smartthings.com/u/wags1)\
**Post date:** [July 1, 2025, 6:59pm UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/7 "2025-07-01T18:59:21Z")

</div>

NM. Not really sure what was changed or why but I just edited the two routines I had, deleted and then re-added the delay. Now they look the same, work the same, but I no longer get a warning message when I open the routine…🤷🏻‍♂️

---

<div class="post-metadata">

**Author:** ![Andreas\_Roedl](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andreas_roedl/32/209616_2.png) [@Andreas\_Roedl](https://community.smartthings.com/u/Andreas_Roedl)\
**Post date:** [July 1, 2025, 7:20pm UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/8 "2025-07-01T19:20:41Z")

</div>

> [@rbendell](#):
>
> I’m trying to understand why Smartthings made the changes to device delays in Routines.

You can control the _same_ device multiple times in a routine now.

---

<div class="post-metadata">

**Author:** ![MarkTr](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/marktr/32/76583_2.png) [@MarkTr](https://community.smartthings.com/u/MarkTr)\
**Post date:** [July 2, 2025, 3:50pm UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/9 "2025-07-02T15:50:19Z")

</div>

> [@orangebucket](#):
>
> What changes are you seeing? I am aware that they have _added_ the ability to add explicit delays between actions in Routines, but I am not aware of any changes to the functionality that already existed. I am not clear how that would even be possible without changing the functionality of the rules engine which would be unforgivable.

When I look at routines that had a delay incorporated, I get a warning that the automation has changed. Previously the routine would have “turn off (delay 6 hours)” and now it has “delay 6 hours” as an independent step, followed by “turn off”. This looks like it will allow for a lot more flexibility in creating routines but I haven’t had time to actually play with it yet.

---

<div class="post-metadata">

**Author:** ![orangebucket](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/orangebucket/32/81590_2.png) [@orangebucket](https://community.smartthings.com/u/orangebucket)\
**Post date:** [July 2, 2025, 4:00pm UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/10 "2025-07-02T16:00:44Z")

</div>

Ah I see.

The Routines you see in the editor are recreated from lower level Rules on the fly so it sounds like the Rules that implemented ‘turn off (delay)’ have the same structure as those that implement ‘delay’ followed by ‘turn off’. So its probably a new interpretation of the same code in order to support new functionality in the Routines editor.

---

<div class="post-metadata">

**Author:** ![orangebucket](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/orangebucket/32/81590_2.png) [@orangebucket](https://community.smartthings.com/u/orangebucket)\
**Post date:** [July 2, 2025, 6:47pm UTC](https://community.smartthings.com/t/changes-to-device-delay-settings-in-routines/302451/11 "2025-07-02T18:47:18Z")

</div>

> [@orangebucket](#):
>
> So its probably a new interpretation of the same code in order to support new functionality in the Routines editor.

Having said that, I see that both the delayed action and the auto-off are explicitly no longer supported, and the auto-off in particular was certainly implemented using a command/sleep/command ‘group’.

If we assume that ‘group’ does what it looks like it does (it not being documented) it isn’t at all obvious why the old and new functionality couldn’t coexist.

It may be that is an incorrect assumption and the `group` was just a helper to reconstruct the Routine.
