topic Re: Base Station Restart in Arlo

Base Station Restart

rmahon — Wed, 28 Sep 2016 21:33:00 GMT

About

Version 2.0.2.732_11731

Released 02/11/16

Arlo Base

FW Version: 1.7.1_4638

HW Version: VMB3010r2

Hello Community,

I added a new camera to my setup over the weekend. I now have a total of 4 on the Basic plan. Since the 4th camera installation, the system has been running flakey. I had no activity at all throughout the day, which is very strange.

Tonight, I restarted my Base station to try and resolve any issues. I had "custom" modes setup with serveral "rules" in each. For instance, start a certain camera when another detects motion. I had several of these.

Well now I have this:

Armed Motion detection on

Disarmed Motion detection off

Schedule Manage based on schedule

All DisArmed Custom mode

None of these are the names of my custom modes. Is this the experience everyone else has had? I am sure I am not the only person to restart their Base Station.

Not happy...serveral hours setting these custom modes up.

Any advice is welcomed. Thanks, Rob

Re: Base Station Restart

Schorschi — Tue, 16 Feb 2016 04:01:50 GMT

rmahon wrote:

(..)
Well now I have this:

Armed Motion detection on
Disarmed Motion detection off
Schedule Manage based on schedule
All DisArmed Custom mode

None of these are the names of my custom modes. Is this the experience everyone else has had? I am sure I am not the only person to restart their Base Station.

Not happy...serveral hours setting these custom modes up.

Difficult to diagnose. It could be that you didn't hit the Save button enough times, and lost rules and/or modes you set up.

For instance, once you create a rule in a mode, you must save it as the last step (there is a Cancel and Save button at the bottom of the final page of the rule set up process).

Also, if you created your modes and rules in an app, try doing it using a web browser.

Btw, the modes Armed, Disarmed and Schedule are default names that you cannot change, they came with your system. Schedule isn't actually a mode, just a time table where you can program when a certain mode is to be active.

Re: Base Station Restart

rmahon — Wed, 17 Feb 2016 00:01:44 GMT

I understand you on the "default" modes. I did not attempt to change these.

As for the "Custom Modes", these were setup and working perfectly until I added a 4th camera. After adding the camera, the entire system would not record or detect any motion or send notifications. At this point, I did a Restart on the Base Station and ALL "Custom Modes" (that were working prior to the 4th camera installation) were missing. Nother but the defaults were present. I had to rebuild all of them.

Now, today and tonight....

I am receiving activity...they are showling up in my Library BUT I am receiveing my email alerts a lot later. For instance, I had an email alert come through at 6:43 pm and the timestamp in the Library is 4:34 pm. Proof...

alerts@arlo.com
6:43 PM (16 minutes ago)

to me
Hi Rob,

Arlo has detected motion on one of your cameras. Here are the details:

Front Door at 4:34:27 PM EST on Feb 16 2016

Re: Base Station Restart

JamesC — Mon, 22 Feb 2016 19:11:15 GMT

rmahon,

Are you still seeing this behavior?

A fix for this issue has been released and has significantly improved Arlo performance. However, a side effect you may currently experience is the alert counter on the camera screen disabled and set to 0. Resolving this counter issue and further optimizing Arlo performance is our number one priority at this time and Arlo engineers are working non-stop to resolve this.

Please refer any additional comments on this issue to the following thread: https://community.netgear.com/t5/Motion-Detection/Email-Alerts-Video-Recordings-Not-Getting-or-Getti...

Thank you,

JamesC

Re: Base Station Restart

rmahon — Mon, 04 Apr 2016 21:01:02 GMT

AGAIN. I had a custom mode setup to do recording on multiple cameras. I also have rules to movement detection on one and record on another. For instance about 7-8 rules under 1 mode in this case.

AGAIN, today, I made a small change to the amount of time to record and BAM....the little Arolo birdie is stuck on my screen. Sotware is locked up, need to restart the software and now the damn mode is gone.

Arlo, what the heck is going on. This is the second time this has happened to me. I'm sure others have experienced the same. I need answers. These are time consuming to setup. Also, how about creating a "duplicate mode" button so you can start with something simaliar so you don't have to "Add" each device/rule.

Re: Base Station Restart

JamesC — Tue, 05 Apr 2016 20:44:57 GMT

rmahon,

Were you editing an existing custom mode or was this a mode you had created but did not save (due to the lock up)? Are you noticing this occurring on a specific device (browser or app) or does it occur regardless of the device used?

A feature to duplicate an existing mode is a great idea. I encourage you to visit the Arlo Idea Exchange and post this there (if you haven't already)

Thanks for sharing,

JamesC

Re: Base Station Restart

rmahon — Wed, 06 Apr 2016 12:18:14 GMT

Good Morning James,

Yes, it was an existing custom mode that had been configured for almost 2 months. I decided I was not getting enough time on the video so I did an edit, increased the "time" slider, and attempted to save. That is when to lock up occured and re-opened that app and the entire mode had disappeared.

I usually do all my edits via the web application for readablity. I only use the app on my phone for an occasional arm and disarm function.

Re: Base Station Restart

JamesC — Wed, 06 Apr 2016 21:12:00 GMT

rmahon,

I have not been able to replicate the issue you describe. You should be able to to edit existing modes and rules from either the web client or the app without issue.

You might consider a factory reset of the base station to see if you get the same behavior after the reset.

JamesC

Re: Base Station Restart

jguerdat — Thu, 07 Apr 2016 12:59:40 GMT

Alternatively, try a new mode with the exact same settings as the problem one. It may be the one mode has a problem. If this works, just delete the old one.