Arlo App. Scheduled Automation NOT working

Reply
Discussion stats
  • 5 Replies
  • 786 Views
  • 0 Likes
  • 3 In Conversation
4Ohr
Aspirant
Aspirant

I've read other similar posts, and they weren't helpful under my use case.

 

I created Arlo's Arm Away at a specific time, using the Routines feature with a separate Schedule Automations: one to set to Arm Away (11:59 PM) and another to switch back to Standby (5:00 AM). Both are enabled under the Automation tab and disabled, respectively, within the Modes, under “automations,” to prevent schedules from overriding each other. Screenshots below.
The Arm Away works fine, but the Standby automation has not worked. It doesn’t kick in. I hope this helps explain.
Could you provide some guidance? Thank you!Arlo Schedule 1 - Copy.jpgArlo Schedule 2 - Copy.jpgArlo Schedule 3 - Copy.jpg
1 ACCEPTED SOLUTION

Accepted Solutions
4Ohr
Aspirant
Aspirant

I tested the next mode concept. I enabled the Standby Automation Schedule under the Mode tab for the next desired mode alone, and I enabled the Arm Away Automation Schedule under the Mode tab for the next desired mode or action.

It seemed to work. So, this has been resolved for now. Thank you, StephenB!

View solution in original post

5 REPLIES 5
jguerdat
Guru Guru
Guru

Frankly, my suggestion is to leave the enable/disable alone (ie, leave it as Always Enabled). While I'm sure there are situations where using those is valuable, I don't use them and my schedules and GF work fine.

4Ohr
Aspirant
Aspirant

Thanks for your feedback. In the past, I tried your suggestion under the Modes tab, but it didn't work. You need to enable the schedule automations that will apply to that one mode, in my case, Standby. If I enable any other schedule available under Standby mode, then they'll cancel each other out, and nothing will be triggered. See Screenshot.

 

Arlo SB Mode - Copy.jpg

 

In my opinion, the Arlo App. modes and automations segments aren't well-written.

 

 

 

 

StephenB
Guru Guru
Guru

@4Ohr wrote:

You need to enable the schedule automations that will apply to that one mode, in my case, Standby. 


No, that isn't right.

 

If you are switching to a new mode in an automation, then the automation needs to be enabled in the modes you are switching away fromNot the mode you are switching into.  For example, if you are switching to standby in an automation, then that particular automation doesn't need to be enabled in Standby, but it needs to be enabled in either Arm Home or Arm Away (or both).  

 


@jguerdat wrote:

Frankly, my suggestion is to leave the enable/disable alone (ie, leave it as Always Enabled). While I'm sure there are situations where using those is valuable, I don't use them and my schedules and GF work fine.


If you want the schedule to be automatically suspended when you are in Arm Away, then you cannot just leave all modes enabled. 

 

You could choose to manually disable the automations in Arm Away until when you return, though that is a bit of a chore (and easily forgotten).

4Ohr
Aspirant
Aspirant

I'll test the away-from-mode into next mode concept tonight, and I'll let you know. 

4Ohr
Aspirant
Aspirant

I tested the next mode concept. I enabled the Standby Automation Schedule under the Mode tab for the next desired mode alone, and I enabled the Arm Away Automation Schedule under the Mode tab for the next desired mode or action.

It seemed to work. So, this has been resolved for now. Thank you, StephenB!