Timers are very inconsistent

When I go out of town, I set a bunch of SmartThings plugs up to turn on and off lights at fixed times. Sunset triggers work like a charm (though last winter they didn’t work for about 4 months). Setting a light to turn on and then off at fixed times is very flakey- lights frequently don’t turn on or turn on, but don’t turn off. I’ll get up in the morning in some other city and look at the statuses and see some lights orphaned on. Also, if I check mid-evening, I’ll see lights that never turned on.

This is the case with SmartThing’s own smart plugs as well as other devices like Link bulbs. It seems like other triggers such as motion, sunset, etc… work, but fixed times are 30-50% unreliable. I also have landscape lights on a SmartThings smart plug, and frequently they never shut off at midnight.

Lest 00:00 hour be a problem, I use 00:01 for midnight shutoffs, but when out of town, different lights go on and off at different times, so it’s not just all lights off at midnight.

Anyone else seeing this? It’s always been this way- it’s never worked right. I have v1 hub.


Same problem I’m having. I’m trying to move some of my time to less peak times to see if it helps. I even got to the point where I created backup timers to double check if the lights turned on but last night even my backup failed. And then there’s the app that executes the command but the device never receives the on/off command. It’s just a mess.

Check your app schedule and see if the next execution date maybe have lapsed already, in that case it will never fire until you edit and save it again.

There are more discussions here:

Thanks for the link. It didn’t find it as it auto-suggested while I was starting to type it.

Interesting that some folks think it’s an app problem on the phone (I see iOS and Android comments)- I highly doubt that. The apps serve only to configure the hub and cloud settings- they don’t control it. As long as the app properly configures your settings, the app is out of the loop control-wise. This is all cloud-based problems, given that hubv1 is also having the issue.

What was happening last winter with the sluggishness was the servers getting behind and issuing commands late, or that “peak time” issue.

I can tell it’s a big problem when that thread informed me it would take 1 hour 22 min to read it :smile: