Assigning rules to modes

[mfastag]

Hi, when I purchased the Arlo system the work flow for creating rules and modes was to, "Create a rule and then assign the rule to modes."  So, if I had a rule to "Record from Camera 1 for 10 seconds when motion is detected" I was able to assign this rule to multiple modes.

In the new work flow, when I "Create New Mode" and give the Mode a Name then next screen that appears notes, "Select the device that you want to use for this rule"...  I don't want to create a new rule, I want to use the rule that currently exists to, "Record from Camera 1 for 10 seconds when motion is detected".

How can I get back the simplicity of creating one rule that I can aply to multiple modes?

Thanks!

[JamesC]

mfastag,

With the UI update Rules were consolidated into the Modes tab. This was done to streamline the user experience when creating new modes and new rules. A separate library of premade rules that can be applied to new modes is a good idea. I encourage you to visit the Arlo Idea Exchange and post this idea there for future consideration!

JamesC

[Schorschi]

---

mfastag wrote:

In the new work flow, when I "Create New Mode" and give the Mode a Name then next screen that appears notes, "Select the device that you want to use for this rule"...  I don't want to create a new rule, I want to use the rule that currently exists to, "Record from Camera 1 for 10 seconds when motion is detected".

---

I feel the same way. So, with the new interface you are forced to create a new rule from scratch in a new mode, even if you have created one exactly like it before in another mode. You cannot reuse previously defined rules, like in the old interface.

I believe this came about, because users were whining, because they didn't get it - or didn't bother investing time to "get it". So, Netgear caved and redesigned the UI and each mode has to be created top-down, including rules, potentially creating multiple rule-redundancies.

The old interface (as far as mode- and rule-definition went) was so much better, logical and had no redundancies.