I then discovered that none of my devices seemed to be responding, so I restarted the hub. That may be completely unrelated.
Today, the info for that rule is showing "Scheduled Jobs": None.
It wouldn't be the end of the world if I had to remove the rule and re-do it using a couple of Simple Lighting rules. (Or perhaps I'll go into the Restrictions and specify that it can run on each day of the week.) I guess I'm just trying to understand normal behavior, but on the other hand if something is broken, I wanted to let you know.
Is this not the big that was supposed to be resolved recently where http calls weren’t timing out and were killing the scheduler? I notice the next run time in the last screenshot is blank but the status is Pending. That’s what I experienced with my Smart Lighting not working on some rules that turned out to be a custom app making http calls, bogging down the system and killing the scheduler.
Can't tell from what's been posted. Not sure that has anything to do with this issue. As far as I know @kelpayne's issue is related to sunrise/sunset offsets in Rule Machine.
I was just trying to point a similarity to the issue I had with scheduling in that the schedule showed it was pending an action but the Next Run Time was blank. It would blank 2 minutes after missing execution of a schedule.
I had some other RM Rules that used Offsets with Sunset/Sunrise that I was able to move to Simple Lighting, but this one has to deal with some Color Bulbs, which the Simple Lighting App does not handle currently.
Is a fix still in the works for RM Sunset/Sunrise with Offsets? It looks like .118 was supposed to fix this... I am running the most current firmware (.119) as of yesterday, but I am not sure whether or not this Rule fired last night because my wife had already turned these lights on via Alexa or a Pico. Based on the Device Events shown below, I don't think the Rule fired last night as it should have shown an ON Event at ~7:05pm.
There were/are two separate issues. The first one, now fixed, is that offsets just weren't working at all. The second issue, fixed in the next release due out, is that a before-sunset or before-sunrise offset won't work on the first day, but will work on subsequent days.
I figured yesterdays update fixed the rules with offset not running, so after updating to .119 I deleted my rule, and recreated it. The rule is used to close my blinds 30 min after sunset. They didn't run last night, and don't look like they are going to run tonight because there is nothing in the scheduler. I figured maybe it would take a day for RM to lookup sunset, and figure the job run time, but today is a new day and still no scheduled job showing up. I went back into it and clicked done again, but still nothing in the scheduled jobs section.
Probably will need live logging to get a record of this; the Device Events page won't record an event that is not a state change, though live logging will (strange but true; you can verify this by comparing the 'Events' page record vs. live logging of an on/off event from the UI. If the device is already on, 'Events' won't record the redundant turn on command. Noted this back in March; apparently it is intended behavior).
The trigger is subscribed to the sunset event from the hub. It doesn't use a schedule until sunset, then it will set to run in 30 minutes. So check the app details after sunset but before 30 minutes after sunset, and you should see a scheduled job. I'd really like to know if that fails for some reason.
Thanks for your reply and explanation. I will check back after sunset. I believe this is where I should see something after sunset, but before 30 minutes correct?
I just found the bug! Argh... Next release, coming soon.
In the meantime you can work around this by using a rule instead of a trigger. Use time of day, with the first time being what will cause Actions for True, while the second time causes Actions for False.
I can confirm, 40 min offset from sunset is working again! Thanks for your work on this. Actually this was a great update. This offset issue being fixed, TTS voice global settings, and the surprise Ecobee integration. I have two ecobee 3's in my home so this update was very appreciated! I have a Brazilian live in nanny for my kids, so the surprise Brazilian Portuguese TTS was a lot of fun to play with tonight! I wish I could change the global voice setting to the Brazilian Portuguese voice when my wife and my Life 360 presence are both showing as not home, then switching to English when we are home, but that is for another day! Great progress on the platform.