Activation times

[Edinburgh_lad1]

Hi @BrookeN 

I was wondering if you would help identify the cause of the system arming later than it's scheduled to. There are days when it's on time, but the night time can be activated as late as 8 minutes after the scheduled time, which is on the hour. Is it Arlo's servers in the UK/Ireland that the SmartHub has a problem communicating with? 

My set up: fibre to the premises (150Mbps), SmartHub connected directly to a gigaport in Fritz!box 7530ax (German product, but used by one ISP in the UK, too). Time and date are automatically obtained via Fritz!box using an EU tine server. DNS queries are encrypted and go through Cloud flare DNS servers, though I understand that Arlo's system uses its own hard-wired DNS server. 

Thank you.

 

[BrookeN]

@Edinburgh_lad1 let me see what I can find out and I will reach back out to you. 

[jguerdat]

@BrookeN frankly, it's been like that for, well, ever since release. This has been reported by myself and many others over time.

[Edinburgh_lad1]

@jguerdat thank you.

@BrookeN this needs addressed then, as when automations/schedules are set up for a specific time, it's not appropriate that they start at different times. Obviously I lost faith in Arlo as a CCTV system a long time ago, but at least when a crime is committed at 9:02pm, I'd like to be able to provide the police with evidence, and not look like a lemon. 

And, by the love of God, please tell your Dev Team not to introduce any new features or interfere with existing ones until they address the issues raised by the community! 

[Edinburgh_lad1]

@BrookeN got an automated email asking if the problem has been solved. I don't think so, so can we have an update please?

[BrookeN]

It is still being investigated, was this from an open ticket you had or through the community?

[Edinburgh_lad1]

I think both. Certainly I'd talked about it before, and so had the others.  

[BrookeN]

I am referring to the email asking if it was resolved. Do you have an open ticket through support open as well? If so were you regularly communicating with them? If not that may have been why they asked if it had been resolved. Regardless, we were able to reproduce it on our side. So development team is working on a fix. I will update again as soon as I receive any more updates. 

[Edinburgh_lad1]

I don't have an open ticket. This issue isn't resolved. And certainly it affects others, too. 

Gosh, lots of fixes on the go. I'm psyching up for new issues, though!