Time based events failing?

Just make sure you don’t use ST timer for those!

1 Like

My timed events have been running super smooth ever since tomorrow.


But seriously folks… I’m collecting stuck apps. I’ve got a “vintage” one that’s been stuck since November!

On a more positive note, I just noticed an “Update” button in the installed smart apps list in the web interface, to help you free those stuck apps daily. Now I just need to make a program to go press all of those update buttons every day on some kind of schedule. Anyone know of a company that can write code that could do that?

1 Like

Have you seen what @ahawkinson retweeted:
Benedict Evans ‏@BenedictEvans Feb 19


1 Like

I feel like Alex and I have very different definitions of the word “exciting”.


Rule Machine can do this for its own Rules. It has an action to Update a rule.


I set up a rule to do this with all of my rules. It seemed that it was triggering rules to occur.

Should it be doing this? Or could it just be with the way I have some rules programmed?

Whenever you update a rule, the rule is evaluated. This is true whether updated by Rule Machine, in the IDE, or by hitting Done in the rule.

This does not happen with triggers, conditional triggers, or actions.

Ok, do I should only use this for everything except rules, unless I’m ok with the house doing things…
Oh wait, this is ST… It adjust does that!

There’s a good reason why the rule is evaluated upon update: Suppose you edit a rule, and change it somehow. When you hit Done, it’s effectively got new conditions and rule, so it evaluates the rule to establish the initial rule truth state. That is the same code called no matter how the rule is updated, and there is no discernment available as to why it was updated.

Think of Update Rules, and the Update link in the IDE as being the exact same thing as hitting Done in a rule.


Which explains why when I had the update rule set to do its thing at 3 am strange things were happening. Lol


I’m just about convinced the hub is still a prototype by design. How can a company put a product on the market that is claiming to perform home automation when you end up waking up to cold house during the winter. I love the concept, but it’s beyond frustrating to try and understand why this happens. I see everybody else is having similar issues with minimal support though so I’m glad I’m not alone. But somebody answer me this, is there any hope for this project?


Hi, Time based event its a common problem, SmartThings its a beta system, no for production, that is crystal clear, but we have it right now, I think the way to still use ST is not depend on it, To the smartapps that uses a timer I have added a Timer Check (Watchdog timer) and make the things to work with the problem, of course take more resources from ST platform, but its necessary to maintain my system working until ST have a real fix to the problem. If we going to still work with ST must to live with failing timers. I use a power meter who reports every minute the power, this event works to check the timers in the smartapp, in this way I have a 1 minute error system,

My time based routines haven’t worked in 2 days…

1 Like

My time based (clock time AND sunset based) routines have been consistently failing for weeks. Lights don’t turn on at sunset, lights don’t turn off at clock time. Sweeper backups don’t turn off the lights in the house mid morning, etc.

Seriously – basically I have a remote control where I turn lights on at night using my cell phone, and off in the morning. There are no reliable time based events working and have not worked for several weeks.

My wife goes around in the morning and turns off the lights manually by pressing the button on the modules/ switches… She’s not amused they burn all night when they are supposed to go off. And if she didn’t turn it off manually, they burn all day…

Face it, Smartthings is losing the competition with electromechanical “clock” timers in her eyes.


There’s always, hope, my friend, … there’s always hope.

In my personal opinion, SmartThings has a much greater chance of stabilizing the product / platform than they do of sustaining the business. There’s no ongoing revenue and tremendous marketing and consumer education challenges. The “smart home / consumer IoT” market will either fizzle (enter a long trough), or become highly competitive (SmartThings has yet to face Nest, Apple, etc., head-on).

1 Like

Which would be fine, except that it doesn’t advertise itself that way.

1 Like

It is pretty outrageous.

I am sure they convince themselves these are “minor problems” that they will iron out “soon”.

Business Intelligence believes (and I agree with their conclusion) that the smart home market is stuck in the ‘chasm’ of the technology adoption curve, in which it is struggling to surpass the early-adopter phase and move to the mass-market phase of adoption.

The key point is this:

The largest barrier is technological fragmentation within the connected home ecosystem. Currently, there are many networks, standards, and devices being used to connect the smart home, creating interoperability problems and making it confusing for the consumer to set up and control multiple devices. Until interoperability is solved, consumers will have difficulty choosing smart home devices and systems.

SmartThings (and others) try to solve this problem by claiming to support all protocols - Zigbee, Z-Wave, BLE, TCP/IP and what not. This is clearly not working. It just creates more confusion for a non-technical customer, which leads to frustration and dissatisfaction.

There’s like 90% overlap in functionality between Zigbee and Z-Wave. Why would an average Joe Consumer care for one over the other is beyond me. The sad thing is, in their quest to support all protocols, SmartThings (and others) have to settle for a bare minimum feature set, effectively offering customers castrated versions of all “supported” protocols.

1 Like

We’re drifting off of the “Time Based Events” Topic, but I think that multi-protocol support is a valuable feature – except that it really has to be “all or one”. The lack of BLE (and Homekit, for that matter) is making a larger and larger subset of devices incompatible with SmartThings.

A key advantage of SmartThings (now copied by some other vendors) is compatibility with lots of third-party hardware and services; some more successfully integrated than others. Because the market is still small, this isn’t like iPhone vs. Android which both have large app stores with, dunno, probably 90% overlap in the most demanded Apps? Heck, some folks are still willing to use Windows Mobile with its tiny store.

As I see new connected / smart devices hit the market (Kickstarter, etc.), I’m always pleased to see Z-Wave or ZigBee, and not happy with those that are BLE, 6wLoPAN, Thread … or even WiFi. The two Z’s integrate well, especially if the Community pitches in for a custom DTH and if protocol specific functions aren’t required (direct association?). Bluetooth BLE will be a quite a feature jump.

In summary; I have far fewer concerns about SmartThings’s compatibility than stability / reliability. Their model for extensibility may not be optimal, but it seems to be pretty resilient except for some notable edge cases (Lutron? Nest? proprietary ZigBee?).