Alexa Sunset Routine Not Working

It is 7:42 p.m. in October, the sun went down twenty minutes ago, and your guest just texted: hey, none of the lights came on, is something broken? You set up that sunset routine months ago. It worked all summer. It worked last week. Now the porch lamp is dark, the living room is dark, the lockbox area is dark, and a family with two tired kids is fumbling for switches in a house they have never been in before.

This is the exact scenario your Alexa sunset routine not working was supposed to prevent — and the worst part is, the Alexa app probably still shows the routine as enabled, last run yesterday, no errors, no warnings, nothing. That silent failure is what makes sunset routines so frustrating to debug from a distance. Below is the order I work through every time, starting with the things that fix it in two minutes and ending with the deeper rebuild you do when nothing else works.

Why this matters more for short-term rentals

If you live in your house, a dead lights-on routine is a minor annoyance — you flip a switch and move on. If you host a vacation rental, a dead routine is a check-in that goes sideways. Guests arriving after sunset rely on the porch light to find the lockbox, the entry light to read the keypad, and the interior lights to feel like the place is welcoming and not abandoned. When sunset automations fail, you get late-night calls, one-star reviews about a creepy dark house, and refund requests that start with we couldn’t even find the front door.

Hosts who manage three or more properties remotely cannot babysit Echo devices in person, so the routine has to be bulletproof and the failure modes have to be familiar enough that you can fix them from your phone in the parking lot of a grocery store. That is the bar.

The fast checks that fix it 70 percent of the time

Before you rebuild anything, run through this short list. In my experience the answer is on this list more often than not, and you can do all of it from the Alexa app on your phone without ever opening a laptop or driving to the property.

Open the Alexa app, tap More, then Routines, and confirm the sunset routine is toggled on. Routines silently disable themselves after certain account events — an Echo factory reset, a household merge, a region change. The toggle being off is the single most common cause of an Alexa routine not triggering at all.
Tap into the routine and check the location set on the trigger. Sunset is calculated from a location, and that location lives on the routine itself, not on your account. If you copied the routine from another property or moved house, the location can be wrong by hundreds of miles, which means sunset fires hours late or hours early.
Check the device list inside the routine. If a Philips Hue bulb or TP-Link Kasa KP125 plug was removed, renamed, or replaced, the action attached to it can become an orphan and the entire routine quietly aborts on that step. Delete the dead step and re-add the current device by its current name.
Open the device page for each light or plug the routine controls and look for the word Offline. An echo device offline fix is a separate task — but a smart plug or bulb showing offline will absolutely make a routine look broken when it is really the device that died.
Run the routine manually using the Play button in the routine editor. If it runs perfectly when you press Play but never fires on its own, the trigger is the problem, not the actions. If it fails on Play too, the actions or devices are the problem.

The most likely real causes, ranked

If the fast checks did not solve it, here is the ranked list of what is actually wrong, based on hundreds of host reports and my own properties. Work down it in order — do not skip ahead, because the cheap fixes rule out the expensive ones.

1. The Echo lost Wi-Fi and rejoined a guest hotspot

This is the number one cause at rentals and almost nobody catches it. A guest tries to set up a Chromecast, the router resets, the Echo Dot 5 briefly shows offline, and when it comes back it sometimes latches onto a guest network with weaker DHCP and no LAN access to your TP-Link Kasa or Lutron Caseta hub. The routine itself runs in the cloud, but the device commands need to reach a hub on your main network. Reboot the Echo by unplugging it for thirty seconds, and verify in the Alexa app under Settings, Device, Wi-Fi Network that it is on your primary SSID, not the guest one.

2. The skill or hub linking expired

Philips Hue, Lutron, Kasa, Govee, and most other smart home skills use OAuth tokens that expire. They usually refresh silently, but a password change, a 2FA reset, or a manufacturer security migration can invalidate them. When that happens, the device still appears in the Alexa app, but commands sent to it fail in the cloud and the routine reports nothing. Disable and re-enable the skill from the Alexa app under More, Skills and Games, Your Skills, and you will be prompted to re-authorize. This is the same fix that revives a stuck smart plug routine that has silently failed.

3. The device itself is dead or stuck

Smart bulbs running 24/7 in lamps that get hot do not last forever. Cheap plugs in damp basements drop off Wi-Fi and never come back. If a single bulb is the problem, routine lights not turning on is the symptom hosts notice first. The routine runs, the cloud reports success on its end, but the bulb is a brick. Test the bulb in a different fixture, test the fixture with a different bulb, and replace whichever side is dead. Keep one spare bulb of every type in the property closet.

4. The trigger is set to sunset somewhere else

If you copied this routine from your home property to a rental in a different state, the sunset time is still being calculated from your home zip code. The routine will fire at the right time for your house, not for the rental. Hosts hit this constantly with multi-state portfolios. Always set the location explicitly per property, do not let it inherit. The same drift causes scheduled time-of-day routines to fail after a household account move.

5. The Echo is flagged as a shared or household device

If you set up the property under an Amazon household and the secondary user removed themselves, some routines lose permission to run. The routine will appear in the app but will silently skip its trigger. Confirm the routine owner under the routine details, and if it shows the wrong account, recreate it under the primary host account.

A clean rebuild that holds up

If nothing on the diagnostic list worked, delete the routine entirely and rebuild it. A rebuilt routine takes about four minutes and removes years of accumulated cruft from renamed devices and changed accounts. Use this exact recipe.

In the Alexa app, More, Routines, find the broken routine, tap the three dots, Delete.
Tap the plus, New Routine. Name it something explicit like Property Sunset Lights On so future you knows what it does.
For When this happens, choose Schedule, then Sunset. Tap the location field and type the property address. Verify the city, do not trust autofill.
Optionally add an offset like 15 minutes before sunset so the lights are already on when twilight starts — this matters in summer when sunset is technically late but it gets dim earlier.
Add actions one device at a time. Smart Home, then the device, then On, set brightness to 80 percent if it is dimmable. Adding all devices in a single action group is tempting but routines fail more gracefully when each device is its own step.
Save, then immediately tap Play to test. Walk the property mentally and confirm each light should now be on.
Set a calendar reminder for two weeks out to verify the routine fired during a real sunset, not just on Play.

A diagnostic prompt you can paste into ChatGPT or Claude

When you are stuck and on the road, paste this into a chat with an AI assistant and fill in the brackets — it will give you a focused next step instead of generic advice.

My Alexa sunset routine is not firing at a short-term rental. Echo model: [Echo Dot 5]. Devices controlled: [TP-Link Kasa KP125 plug on porch lamp, two Philips Hue bulbs in living room]. Trigger: sunset, location set to [city, state]. Symptom: [routine shows enabled, last run yesterday, lights stayed off tonight, manual Play works]. What is the most likely cause and what is the single next test I should run?

The fallback for tonight

If you are reading this with a guest already in the property and lights still dark, skip the rebuild and do this. From the Alexa app, manually toggle each light on right now. Then create a one-off Schedule routine for tomorrow at the same sunset time as a temporary patch. Then send the guest a quick message:

Sorry about that — just turned the lights on remotely. There is a switch by the front door if you ever want to override the automatic schedule.

Hosts who name the failure and offer manual control come out of these incidents with the review intact almost every time. Hosts who go silent get burned.

Frequently asked questions

Why does my schedule failure only happen at sunset and not at fixed times?

Sunset is computed from a location at runtime, while a fixed time like 7:00 p.m. is just a clock check. If the location field on the routine is missing, blank, or wrong, the sunset trigger silently fails to compute a fire time, and the routine never runs. Fixed-time triggers do not depend on location, which is why they keep working when the sunset version dies. Always verify the address on every sunset routine, especially after copying routines between properties.

My Alexa smart home device unresponsive message keeps coming back. Is it the Echo or the device?

Almost always the device, not the Echo. Echos rarely lose individual device control while still responding to voice. Reboot the smart plug or bulb first by power-cycling it at the wall for thirty seconds. If it comes back, it was a Wi-Fi reconnect issue. If it does not, the device is failing — replace it with a known-good unit and re-add it to Alexa. Keep spares of plugs and bulbs in the property closet so cleaners can swap them between bookings without a service call. The full unresponsive device walkthrough covers the per-brand reset moves.

Will the routine fire if the Echo is unplugged?

Yes, surprisingly. Routines run in the Amazon cloud, not on the Echo. As long as the controlled devices have their own Wi-Fi connection — smart plugs, Hue bulbs through a hub, Kasa devices — the routine fires even if the Echo is dead or unplugged. The Echo is only required for voice triggers. This means a guest unplugging the Echo to charge their phone does not break your sunset automation, which is good news.

How do I know if the routine actually ran last night?

Open the Alexa app, More, Routines, tap the routine, and look at the Last Run timestamp. If it shows last night around sunset, the routine fired and the problem is downstream — a device did not receive or execute the command. If it shows two days ago or never, the trigger never fired and you have a routine-side problem. This is the single most useful diagnostic data point and most hosts forget it exists.

Should I just use a dumb timer instead?

For a single porch light at a single property, honestly, yes. A 12 dollar mechanical timer or a photocell-based dusk-to-dawn bulb is more reliable than any cloud routine and never needs an app update. Use Alexa sunset routines when you need coordinated multi-light scenes, occupancy logic, or remote override — not for a single bulb where a dumb solution would do the job. Knowing when to step down to simpler tech is a sign of a mature host setup, not a failure.

Next steps

Before your next booking, walk through the Alexa routine troubleshooting checklist while you are physically at the property — it catches device naming drift that you cannot see remotely. Then return to the broader Alexa troubleshooting hub and the parent Alexa routines pillar for the rest of the framework. Save the checklist before your next turnover — sunset failures are easier to prevent than to apologize for.