Schedule error - 1 hour off

[Rusty-Alvin]

Hi there I have a weird glitch that seems to involve software, but it has resisted solution. Arlo support has no useful opinions about what might be happening.

One day each week, my schedule switches precisely 1 hour early to my nighttime lockdown mode. Instead of moving to Arm Away at 8:30pm, it switches at 7:30pm (sometimes 7:31pm).

I have suddenly realized it's always on Friday.

This is for my office so you can tell me it's cute, my office system is trying to tell me to go home at 7:30pm, but otherwise, there is no obvious reason this would happen.

I tried to upload a photo of my schedule but this system is screwed up and won't display images.

It's simple, though:

Morning soft opening - 6:00am Everyday (triggers ArmHome Mode)

Morning opening - 7:45am weekdays (triggers StandBy Mode)

Evening lockdown - 8:30pm Everyday (triggers ArmAway Mode)

That's it!!

Yet that "evening lockdown" mode triggers at 7:30pm instead of 8:30pm on Friday night.

I have actually wiped the schedule and rebuilt it, with the exact same effect.

Anyone else have quirky misfires of the schedule like this?

[BrookeN]

Are you still seeing this same behavior with the schedule being off by a hour. 

[Rusty-Alvin]

Hi there - YES.

I write to you on a Friday after posting that this happens every Friday, and only on Friday.

On this particular Friday, the system armed exactly one hour early, setting off the alarms while I was sitting at my desk, treating me like an intruder.

It's the only day of the week but it always happens. My schedule does not have anything different for Fridays.

[BrookeN]

Did you see this same behavior on your other location as well?

 I did send this information onto our development team who is investigating the behavior you are seeing.

[Rusty-Alvin]

This error only happens in one location. Every single Friday, the nighttime "arm away" schedule triggers one hour early. This happens even though the schedule is simply set to move to "arm away" at 8:30pm "Everyday."

In practice, this schedule functions properly on 6 out of 7 days, but not "Everyday." It is always messed up on Fridays. Still.

[BrookeN]

Thank you for providing this information. The development team is currently investigating this.

[BrookeN]

@Rusty-Alvin this behavior should now be resolved, can you please check and see if you are still seeing this same behavior?

[Rusty-Alvin]

Good day - this problem occurs exclusively on Fridays. Today is Tuesday.

I did note that LAST Friday, March 14, it did not occur, for the first time since I installed my system.

I noted that this was the very first Friday after the switch to Daylight Savings Time, "Spring Forward."

I had always speculated that the one-hour-early error in the system was related to Daylight Savings Time, but it was impossible to guess why the system was wrong about the time of day only one day per week.

So, what we know is that on one Friday the problem didn't happen. If this was AFTER the engineers addressed the problem, GREAT. Problem is likely solved!

If it happens again, I will report it. If it begins again after the time changes once again late this year, we'll have more evidence to suggest the source of the problem.

Thank you.

[BrookeN]

Are you still seeing this same behavior?

[Rusty-Alvin]

No it seems to be fixed!

I want to be sure we get through one more time change without the problem coming back!