I’m not going to put in a support request because support will just tell me to use something other than Rule Machine. But after a week of solid performance, I know have a rule that isn’t completing because it takes 151 seconds to execute I assume. On 4/23 in took 103 seconds and didn’t run. On 4/24 it took 36 seconds and ran. On 4/25 it didn’t execute and took 151 seconds. The rule is supposed to fire at 2200. @slagle
Anybody else seeing this?
Several threads and posts starting this morning related to execution timeouts/stuff not firing…
I have several loss of scheduled actions in the morning… Right now they are all ok.
Just curious, what’s your rule?
As developer, I understand there is no perfect code, and Rule Machine might not be bug free (also depend on which version you are using), so it may well because of the scenario/code/setup issue, it can run one day doesn’t means it run it efficiently.
Perhaps its good for ST to review the Rule Machine code, to see if they can further improve it.
I had a couple of triggers based on time that didn’t fire last night and early this morning. I too am hesitant to submit a support ticket, but I’ll probably still do it to make sure the data point is entered.
I had 3 separate instances of items not happening. They should have all been triggered by routines. It started yesterday at 8:27pm. I did notice some lights not shut off from a motion rule in rule machine earlier in the day but didn’t think too much of it. I had one routine fire correctly this morning. These are all time based except the rule machine unless you count the time delay before the lights turn off. SHM went completely bonkers and re-armed itself in away mode even though I was home sleep because my alarm didn’t go off. It’s happening all over so something has definitely changed on their end.
It’s a trigger. At 10:00 p.m. do these actions: Turn off Living Room Fan, Change Mode to Night. Pretty easy stuff compared to my others that are working.
Hey Guiz…
Don’t worry too much. I am sure there are plenty of ST community members that will chime in soon with their reports stating that they are still 99/100% stable.
As long as a few have that perception, we’re good to go. And we don’t want to bring those lucky/oblivious folks down with any negativity. Facts are not always appreciated.
Had to click Update on a Rm rule so that it turned on a virtual switch when I opened a door. Wasn’t working. Also my morning rule for 6:24am didn’t fire… I’ll click Update on that and see in the morning tomorrow.
Mine actually was working very well up until last night. All of my triggers were executing, lights behaving, SHM even acting liked it should. I was enjoying my HA up until about 14 hours ago.
The rule to turn off the virtual switch 5 minutes after was scheduled… but never happened… still hasn’t appeared in the execution history yet… some prior ones took as long as 100 seconds.
Last night and this AM I’ve had issues with a couple of dim-up or dim-down over time rules stalling as well. Given that these seem to be timing related events, maybe the cron fix faulted?
hi, will you be able to share your exact setup, can they be setup using routine? Most of my setup are routine based and so far ok, except for the few days that when things really bad.
I wawant to be the first to chime in. My system is 100% stable and reliable.
All of my lights and devices are turning on exactly as they are programmed to. No problems there.
I can rely on ST whole heartedly not to leave me in the dark.
But I do have this one little complaint. It’s small cause I can see just fine.
Everything turns on, but nothing turns off…
So yes, 100% on turning things on.
Not do much for turning them off.
I love it. Move the goal posts!
I have some very simple time-based triggers using Rule Machine that have been solid for about a week. Looking at the job histories in the IDE, I see records where something tried to execute, but the execution times for failed events are a lot higher (close to 10x) than normal.
I have also submitted a support ticket.
I’m down to only THREE zigbee devices and TWO Smart Lighting rules–no Rule Machine. All they do is turn on at Sunset, off a couple hours before dawn, and make sure they are set to the right color. I no longer have a single 3rd party SmartApp installed.
Seriously, the whole system is issuing three commands a day. That’s it. ST misses turning off one of the lights about 20% of the time in the mornings.
Anyone want to trade for a Sylvania IQ dimmer light? I’ll take an old X10 CM11A or better, as long as it plugs into USB.
I’m seeing this to on rules that have a scheduled time that the past few days the execution time has greatly increased. I had one rule this morning that didn’t fire at all and no logs in the IDE of it trying.
Just an fyi folks, this isn’t restricted to any single app.
It seems to be a cloud issue.
I’m having failures related to of command and pending of commands. These are occurring in tile machine rules, smart lighting rules, and other apps I have that issue cloud based commands.
There is no telling how long this will occur until ST first acknowledges it, and then fixes it.
In the mean time, try to program local control.
I ran a test this morning. I set up two smart lighting rules, one local, one cloud. Both with the same trigger.
They both executed. There local performed every time. The cloud got progressively slower to execute until it also failed.
Not to say this will fix it. I was just trying to replicate the symptoms for troubleshooting.
Everything fired 100% for me, SHM worked is still on point too. Keeping my fingers crossed.
I did have a hub reboot in the middle of the night, not sure what that was about. I’ve never had that happen before.But it came back online no problems.