Door Lock Automation: Understanding the 'Stopped' Timeline Issue

As someone who’s been diving into the world of smart home automation, I’ve been trying to perfect my door lock system. The goal is simple: when my family leaves the house, I want all doors (front, back, garage) and the garage door to lock automatically. If any door is left unlocked, I want a notification sent to my phone. It sounds straightforward, but I’ve hit a snag that’s been a bit puzzling.

Here’s what my automation setup looks like:

  • Trigger: When the ‘group.family’ state changes from ‘home’ to ‘not_home’ after a 5-minute delay.
  • Conditions: Checks if each door (front, back, garage entry) is unlocked or if the garage door is open.
  • Actions: Locks the doors, closes the garage door, and sends a notification with the specific door’s name.

The issue arises in the trace timeline, where it says, ‘stopped because only a single execution is allowed (runtime 0.00 seconds).’ I’ve tried tweaking the automation, especially the ‘choose’ function with trigger IDs, but the problem persists.

I’m curious if others have encountered similar issues and how they’ve resolved them. Is there a way to allow multiple executions or adjust the automation to handle all doors without stopping mid-process? Any insights or troubleshooting tips would be greatly appreciated!

Looking forward to hearing from the community and learning how to refine this automation for a seamless experience.