Why isn't my automation triggering?Updated 2 hours ago
When you set up an automation using the standard method, the AC unit sometimes doesn't have enough time to fully initialize before the command is sent — especially for temperature or mode changes. This can cause the automation to:
- Run once and then stop triggering
- Turn the AC on but ignore your temperature or mode settings
- Turn the AC on and then immediately turn it off again
- Show as "running" in the app but do nothing to the unit
Use this setup to ensure a reliable automation:
- Delete your current automation (tap into it and scroll to "Delete automation" at the bottom)
- Go to Automations → Create new automation
- Select Scene →Do this: add action: → "Wait, then do something"
- Set the timer for when you want the action to happen (e.g., 10:00 PM)
- Add a wait time of 2–3 minutes — this gives the unit time to power up and initialize
- After the wait, add your desired action (e.g., Cool mode, 70°F, Low fan)
- Save your Scene
💡 Why the wait step matters: Your AC needs a moment to fully initialize after receiving the "turn on" signal before it can accept mode or temperature commands. The 2–3 minute wait bridges that gap.
If you want to set both temperature AND mode, use separate automations
The app works most reliably when each automation contains one command at a time. If you want to turn on, set a specific mode, and set a temperature, set them up as separate automations timed 1 minute apart:
- 10:00 PM → Turn on
- 10:01 PM → Set mode to Cool
- 10:02 PM → Set temperature to 70°F
💡 Why separate? Stacking multiple commands in one automation can cause only the first command to execute. Spacing them out ensures each one is processed fully.