Same here… they were fine until this morning… half fired, half did not. I have a specific time however not going off of sunrise/sunset times. I went into the IDE to refresh them and fingers are crossed for the rest of the day and tomorrow morning… thing is, I haven’t been having issues at all until we all started mentioning we have been working in this post (myself included), so yep… we Jinxed it.
I’ve had timed rules fail, gone into the ide and refreshed, only to watch it fail 3 minutes later.
I swear I think the scheduler had been uninstalled!
It was the most merciful thing to do 
2 Likes
You know… the odd thing is, when I was updating the timed events in the IDE, I noticed that there were a couple of successful event triggers that just simply didn’t show in the log which is odd because they HAVE been working just fine and haven’t missed a beat until this morning. The next time they were supposed to run was correct and in the future but the log of when they did fire was missing days worth of them for some reason.
Now, last night I had to remove/add a device and had to manually go through all of my routines and such to update them and this may have caused the hiccup this morning but I certainly hope not since everything is correct and half fired, half didn’t… and of course, as usual, I can trigger the events manually from the app and they fire correctly and quickly when manually executing them. The rest of my timed routines have worked perfectly fine today, so I hope it was just a hiccup and will go back to normal.
I’ve had rule after rule fail. And when I go check them out they aren’t rules anymore. All they are is actions. Which means I have to completely delete and rebuild them.
Same here. Since yesterday 50% of the scheduled events did not fire and did not reschedule. Even after an Update on the IDE it fails again after a couple of hours.
About 40% of my Rules in Rule Machine are only showing Actions (no Triggers, Conditions or Rules) and of course are NOT working and I had to rebuild them.
Hey @jody.albritton - If we open a support ticket for this issues and send you a PM what will you be able to do? Is there something that you can fix or restore on our accounts? Or this information is just to help you troubleshoot the issue?
Thanks
Since DST my sunrise event has not been working. This is with hub v1
Sunset DOES work.
I don’t know how to tell if it’s a rule or action. I’m looking in Routines in the app and use Smart Lighting. I don’t use Rule Machine or anything else. The first two routines missed completely but the next two so far have triggered just fine and the devices in these mentioned routines are all the same.
Looks like someone from ST is replying to this thread. State they know root cause now and are working on it.
Right now it would just be for troubleshooting purposes. I have seen reports of rules coming back after a disappearance so that might not be permanent. Once we stabilize the platform we can start looking into these rule machine issues.
Well, KNOCK ON WOOD… only those two first timed routines failed to fire after having to remove/re-add a device and go through all of that rebuilding… ever since those first two fails, everything else has fired on time as expected and is working again. Must have been a hiccup to get out of it’s system because I have gone full circle now and 1 full days worth of timed events have triggered as expected.
Yesterday, I just had a smartapp that’s been frozen in the past since November come back to life on it’s own. Maybe they are getting things fixed.
2 Likes
Did something change?? After months of my routines failing literally every single night, the last 4 nights/days all of my routines have worked. (knocking on wood)
1 Like
Yes things are finally working but unfortunately they plan to fix it on Monday. 
4 Likes
Mine have been working great the 3 weeks I’ve had ST but my outside lights didn’t come on last night. Only change was I added a wemo light switch I had laying around for a motion sensing light I installed yesterday ( all pro revolve 270). Since I plan on leaving it switched on and let the dusk to dawn motion sensor do it’s things I didn’t add the switch to any if my routines. I plan on replacing the wemo with a GE z wave switch even though the lights shut off on time this morning and I don’t think the wemo had anything to do with it.
I have had this issue off and on for about a month.
Same song: Smart Lighting ignoring time based on sunrise/sunset.
Support keeps running their Update Script to no avail. Insanity?
Below is my last email to support. Thoughts?
Please do not run the Update script again — it does not do the voodoo you think it do.
My lights are messed up again.
Having outside lights go on in the daytime costs me money.
Having outside lights NOT go on at night is a Security Risk for my family.
- I walked outside after Sunrise and the floods came on. The Live Log #failed to show this, but the device events list did.
- Then I updated the Smart Light app instance changing the time & changing it back & saving
- I walked back outside and the lights came back on.
- Other Apps depending on the time of day constraint in your smart app do work
- This one works sometimes
Pool Floods Device Events List First Failure
Pool Floods (Device) Events — displayed | all | from device
Date Source Type Name Value User Displayed Text
2016-04-26 7:58:45.988 AM EDT
moments ago DEVICE switch on Pool Floods switch is on
2016-04-26 7:58:45.969 AM EDT
moments ago APP_COMMAND setLevel Pool Lights motion Office-side Dark sent setLevel command to Pool Floods
Pool Floods Device Events List Second Failure
Date Source Type Name Value User Displayed Text
2016-04-26 8:03:49.231 AM EDT
moments ago APP_COMMAND setLevel Pool Lights motion Office-side Dark sent setLevel command to Pool Floods
2016-04-26 7:58:45.988 AM EDT
6 minutes ago DEVICE switch on Pool Floods switch is on
2016-04-26 7:58:45.969 AM EDT
6 minutes ago APP_COMMAND setLevel Pool Lights motion Office-side Dark sent setLevel command to Pool Floods
2016-04-26 7:51:18.695 AM EDT
13 minutes ago APP_COMMAND off Pool Lights Off when motions stops sent off command to
LIVE LOG OF “Pool lights motion office-side dark” Second failure
39b9df16-3441-4972-9c2f-25933d9065f9 8:02:59 AM: trace timeBasedTrigger: false
39b9df16-3441-4972-9c2f-25933d9065f9 8:02:58 AM: debug Updated with settings: [level:100, motionState:active, motionSensors:[Pool Motion Office], lights:[Pool Floods, Side Floods], motionStopsTime:9, startTimeType:sunset, endTimeType:sunrise, motionStops:true, trigger:Motion, action:level, overrideLabel:true]
39b9df16-3441-4972-9c2f-25933d9065f9 8:02:42 AM: trace timeBasedTrigger: false
39b9df16-3441-4972-9c2f-25933d9065f9 8:02:26 AM: trace timeBasedTrigger: false
My Sunrise/Sunset triggers have not been working over the last 3 days, either.
Same thing here. I have time based event that have been flawless for months. As of yesterday they keep breaking…
I ran a subsequent test in-between work calls a little bit ago.
I removed and recreated that particular Smart Lighting Automation. Works now.
THIS IS NOT A SOLUTION.
This is an indication that:
- We have a Configuration Data Consistency Integrity Problem
- The Update Script Does NOT do the same thing as Creating the App As it does not return the Configuration Integrity
- This can be an issue with the platform database, communication methods or logic.
- This is not a problem with our configuration of Smart Apps. So, cannot be fixed by Guardrails
- This will happen again until that underlying problem is fixed.
c’est la vie on new software that is fragile. But, it has taken one Helluva Lot of us to show the strain!
Spoke too soon. The workaround of recreating the Smart Lighting App did not last long.
I just walked out in bright sunshine, clearly broken.
Just broken.
I give up.
Fragile software…
I’m ready for some guardrails. That work.