Multiple Q Cams all trip to motion alerts when there's 'NO Motion' in the playback video

[gmd-024]

I have multiple Q cams along with a an Essential Indoor cam and 2 Essential Spotlight cams set up in the Arlo Secure Android App... for waaay to long I have been receiving waaay to many motion alerts, mostly from the Q cams, to where I have the motion sensitivity turned down on the Q cams to 25% - and I have the audio sensing alert(s) turned off, to no avail

   Just today, after looking at the time stamp on the recorded motion videos I realized that when there is a tripped motion alert/recorded video on any of the Q cams, that all of the Q cams are tripped also, and that ALL of the videos are time stamped at the same identical time of day - and when I play back the recorded video(s) there is NO MOTION taking place at all - and of course ALL Q Cams are aimed in completely different directions both inside and outside of the house

   I can now only assume the issue is on the ARLO server side and nothing I have done incorrectly in the set up process - plus all Q Cams show they are using the most current, up to date firmware

    Has any other users experienced this odd issue and possibly have any suggestions to resolve it

    Thanks

[jguerdat · Accepted solution]

Is it safe to assume that you turned off audio detection and adjusted motion detection in your modes and rules? Check your rules for each camera to ensure that cross-triggering (one camera detects and records and causes others to also record) isn't somehow enabled. Have you power-cycled each camera?

[gmd-024]

As stated in my opening paragraph... audio detection is turned off

  I have no clue where to look for "cross-triggering" - never heard of it (in relation to the Secure app), and no where in the Secure app's Modes is it listed as a feature/setting to be enabled/disabled - please elaborate further

   And yes, I have power cycled the Q cams (multiple times)

   Further details to this odd issue... Last evening I moved one of the Essential spotlight cams from it's original placement in the home and moved it within 6 inches to one of the Q cams and aimed it in the same direction of the Q cam - and over night the Q cam had triggered on a few motion alerts (which of course triggered the other Q cams to detect motion alerts also) - but when checking the 'Feed' section in the Secure app this morning I could clearly see where the Q cams had triggered a few motion alerts/events, but the Essential cam sitting 6 inches from one of the Q cams and aimed in the same direction had not triggered a single motion event !

   This test (setting the Ess. spotlight cam next to a Q cam) leads me to further believe that there is something going on with the Q cams or the Q Cams in the Secure app and/or it's a server side issue that ARLO possibly needs to investigate !

[StephenB]

---

@gmd-024 wrote:

  I have no clue where to look for "cross-triggering" - never heard of it (in relation to the Secure app), and no where in the Secure app's Modes is it listed as a feature/setting to be enabled/disabled - please elaborate further

---

@jguerdat explained what what cross-triggering is.  When you detect motion on camera X, you can tell the system to record on camera Y (or both X and Y).  You can see that by looking at the rules in the mode(s) you are using.

[gmd-024]

I'm sorry but I can't locate the cross triggering rule you're referencing - but unless this is something that's enabled by default (Which I doubt)... I think it's fair to say, since I haven't heard of it before, that I never enabled it

Also more info to add... I just realized that all the Q cams seem to be false triggering for motion at the same identical time of day, only at "night time" (even though there is NO Motion taking place when playing back the recorded video) -- the Q cams, whether indoors at night when there no light or only a small night light in the room - or outside at night when there is no sunlight, porch lights, patio lights, auto-motion triggered lights, etc.

    And as previously mentioned, I've played back 'Many' of the false tripped 'Motion' events/videos to inspect them for any signs of motion or some sort of a flicker of light and there is 'Nether' in any of the recorded videos

[StephenB]

---

@gmd-024 wrote:

I'm sorry but I can't locate the cross triggering rule you're referencing - but unless this is something that's enabled by default (Which I doubt)... I think it's fair to say, since I haven't heard of it before, that I never enabled it

---

It's not created by default, it's a rule you need to create.  If you didn't do that, then you aren't using cross-triggering.

• https://kb.arlo.com/42/What-are-modes-and-rules-and-how-does-Arlo-use-them

[gmd-024]

I just now realized that I actually had enabled 'cross-triggering' without realizing it - I'm fairly new to using the Secure app and how it functions, and apparently still learning

   I haven't given it enough time to thoroughly test this, but I'm 99.9 % certain that cross-triggering was the cause of my misunderstood issue

   I'll report back if the issue persists, but I doubt it will

   Thank you jguerdat (and StephenB)