When accessing through Lights & Switches, there is only turn of and on using a schedule…and that only has a switch for sunset or sunrise.
Where in the app are you getting the above settings?
Setting up or modifying a Hello Home Action. I have one that runs automatically around sunrise and another for sunset.
See where it says “perform the action”? That’s the HHA I’m currently setting the triggers for. Off the “perform automatically” screen.
Ah, that’s the difference. This is not under a hello home action, this is under the standard actions for things themselves.
Home Health Action triggered by sunset failed again tonight. 
I set up a new HHA to turn on a light at half an hour before sunset, and it worked fine. Still working with support.
I started having this issue randomly a couple weeks ago and I don’t have the option to offset the time to turn on lights - does smart things have any idea when they’re gonna resolve this issue of sunset turning our lights on?
Yesterday I removed the lights from the sunset HHA and then readded them. It didn’t trigger last night, but it did today. Could just be coincidence, but if you don’t have too many devices it might be worth trying. However, it may need a full 24 hour cycle before it works. I did not reboot the hub.
FWIW…
No custom smartapps involved. Plain vanilla Hello Home Action that turned on one light at sunset. Support had been working with me on it for 4 days.
My sunrise / sunset switches and groupings all worked reliably until a few nights ago, and now none of them work.
More interestingly, there’s a thread on these forums from folks who have rolled their own scripts to do work with API level sunrise and sunset triggers, and those have suddenly stopped working as well. That implies it’s a systemic problem.
Did someone file a ticket? I don’t want to duplicate
Rob
Please file a ticket. It’s the only way for them to get a sense for how many people are affected, and so justify spending more resources on the problem. So it’s not duplication, it’s raising the urgency level. 
1 Like
I came into say that it is intermittent for me as well.
Thanks - I will file that today.
I have a few custom apps subscribing to location sunrise and sunset. One turns lights on/off and the others just set a state variable. The app that turns lights on runs pretty reliably at sunset, except for the day it is installed. The others have never run from the sunset or sunrise location trigger. The code used in each is exactly the same expect for what happens within the subscription handler.
I started a chat with support a few days ago about the issue, no progress as of yet.
I noticed that mode changing actions triggered by sunset/rise have stopped working past a few days as well. I contacted the support and they acknowledged that there is problem and they are fixing it now. It is quite frustrating to see features I rely on suddenly breaking like this.
We are rapidly approaching 3 months since the issue was officially listed on the SmartThings status page.
http://status.smartthings.com
That’s a bit concerning for something as core and “simple” as a sunset/sunrise trigger. I’m sure I’m insulting the engineers by saying it is “simple,” but to an end user it is just a timed action. If the issue is load on the servers, why not make sunset/sunrise a window starting 5 minutes prior where accounts are randomly set to on a daily basis within that window?
Does anyone out there really care that it happens exactly at sunset? If you do, please elaborate because I would love to understand this more. The ONLY thing I can think of is that you want your lights turn on at sunset and you house is on a shoreline/mountain that faces west and you can actually see the sun set over the horizon in front of your eyes! 
Even then, does it matter that your lights might come on a few minutes early?
3 Likes
Perhaps make this an option within the configuration of the iOS or Android app itself, at the account level. By default, all users are set to the 5 minute window. You have to opt out of it if you want to have exact sunset/sunrise times.
Then, the offset times can still work off this. For example, if you live in a valley, your sunset is earlier because you are in the shadow, so I can see you wanting your lights to come on earlier - aka the offset. That can still happen in the scenario I am proposing.
I definitely agree that this “known issue” has been unresolved for too long, particularly since it affects a very common and expected use case (i.e., turning on/off lights at sunset/sunrise!).
I fear that the issue is that even 5 minutes may not resolve the problem (and I think – just guessing) that this is tied into the long execution times of “unschedule()”:
The behavior of runIn() and all (?) related scheduling is defined with rules that seem too tight for the abilities of the execution environment. Jobs are not allowed to execute if their scheduled time has past. Maybe this is resolved with a queuing mechanism that takes a “tolerance” argument (i.e., a sunset job can live in the queue as long as 30 minutes, rather than being dropped altogether).
1 Like
Agreed. Shouldn’t matter. I did add a hard-coded 1 minute offset to sunrise and sunset times in my dusk-to-dawn app. Maybe some improvement . . .hard to say. I have had 2 failures in the last 3 weeks or so of rise or set actions.
1 Like
I got the impression from support that they’re just waiting for the new hub to come out to relieve the stress on the backend rather than put forth the effort to fix it.
I have a HHA set to trigger 30 minutes before sunset. Recently it’s been triggering TWO WHOLE HOURS (and that’s approximate, which is even more frustrating) before sunset.
I’ve been supportive of ST and the challenges they’ve been facing, but I’m starting to think it’s time to search for a new alternative. It’s getting ridiculous.
I got fed up with the sunrise/sunset and replaced it with an outdoor luminescence sensor. It is sort of my personal sunrise/sunset as it is actually measuring the amount of sunlight outside my house. It has been pretty close to 100% paired with the smartapp “Light Up the Night”.