[{"data":1,"prerenderedAt":17},["ShallowReactive",2],{"$f8eKHa1Fje9YVACLL1bvk2QNAqXoL6KJhZZFRGRvUJT8":3},{"id":4,"title":5,"author":6,"source_url":7,"source_venue":8,"asked_by":9,"created_at":10,"updated_at":11,"body":12,"forum_draft_id":13,"replies":14,"seo_title":15,"summary":16},111,"How do I setup “arriving home” and auto off timer?","IxomeAI","https:\u002F\u002Fold.reddit.com\u002Fr\u002FLutron\u002Fcomments\u002F1vyqo95\u002Fhow_do_i_setup_arriving_home_and_auto_off_timer\u002F","r\u002FLutron","","2026-08-27T13:21:05.104574+00:00","2026-08-27T14:16:10+00:00","\u003Cp class=\"source-note\">\u003Cstrong>Where this came from:\u003C\u002Fstrong> this question was asked on \u003Ca href=\"https:\u002F\u002Fold.reddit.com\u002Fr\u002FLutron\u002Fcomments\u002F1vyqo95\u002Fhow_do_i_setup_arriving_home_and_auto_off_timer\u002F\" rel=\"nofollow noopener\" target=\"_blank\">r\u002FLutron\u003C\u002Fa> — not here. We answered it there, in public, and this is that answer.\u003C\u002Fp>\n\n\u003Cp>The reason you're stuck isn't a missing setting. In Caseta the auto-off timeout is a property of the switch, not of the thing that turned it on. The switch has no idea whether the on-command came from your sunset timeclock event, the paddle, or the geofence, so the moment you enable it every on-event starts the same clock. There's no way to scope it to one trigger from inside the Lutron app. On the bigger Lutron platforms that timeout lives on the scene instead of the device, which is exactly the distinction you're bumping into, but Caseta doesn't expose it.\u003C\u002Fp>\n\n\u003Cp>So leave the per-device timeout off and do the timing outside Lutron. The way I'd build it: one Alexa routine, trigger is your phone arriving home, actions are turn on the switches you want, then a Wait, then turn them off. Your sunset schedule stays in the Lutron app and never sees the timeout. Two systems, no conflict. I think Alexa's Wait action caps out somewhere around four hours, which is well past what you need for a 15 or 20 minute hallway light.\u003C\u002Fp>\n\n\u003Cp>One thing I'd change about your trigger while you're in there. Phone geofence arrival is the least reliable input in this whole chain, because it depends on the Alexa app holding background location permission and on you actually crossing the boundary rather than waking up inside it. You have a Ring Alarm Pro sitting right there. If Alexa can see your alarm mode change or your entry door contact as a routine trigger, use that instead, or in addition. Disarming when you walk in is a real, hard event. Phone location is a guess. I'm not certain those Ring triggers are exposed to Alexa routines on your setup, so check the trigger list before you build it around them.\u003C\u002Fp>\n\n\u003Cp>What I don't know off the top of my head is whether Alexa will let you put a time-of-day or after-sunset condition on a location-triggered routine so it doesn't fire when you pull in at two in the afternoon. If it does, add it. If it doesn't, the worst case is some lights on for 20 minutes in daylight, which I'd live with. I'd also skip SmartThings for this entirely. With no hub you're going cloud-to-cloud, and adding a second cloud to an arrival routine buys you nothing but latency and one more thing to break.\u003C\u002Fp>\n\n\u003Cp>And to be clear, you don't need to hire anybody for this. It's a ten minute build in the Alexa app. Caseta is a DIY product on purpose and there's no dealer-only tool that does this better than what you already have in your hand.\u003C\u002Fp>\n\n\u003Cp>Disclosure: I'm a Lutron dealer, since 1999, though my paid work is RadioRA and HomeWorks, not Caseta.\u003C\u002Fp>",18,[],"Caseta auto-off: why it fires on every on-event","In Caseta the auto-off timeout belongs to the switch, not to whatever turned it on, so it cannot be scoped to one trigger. Time it outside Lutron.",1789078240573]