<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Minimum time between triggers in Arlo Pro</title>
    <link>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238189#M8256</link>
    <description>You got it. Li e view would be a definite reason.</description>
    <pubDate>Tue, 28 Feb 2017 16:55:11 GMT</pubDate>
    <dc:creator>jguerdat</dc:creator>
    <dc:date>2017-02-28T16:55:11Z</dc:date>
    <item>
      <title>Minimum time between triggers</title>
      <link>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238032#M8238</link>
      <description>&lt;P&gt;I have started to notice that once an event is triggered and a recording is made - if something else happens within a short period of time - it doesn't trigger.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example - if I leave the house at 7:40 - motion triggers, recording is made. &amp;nbsp; If my wife leaves at 7:52, nothing happens. &amp;nbsp;If Amazon arrives at the house at 8:11 - motion triggers, recording is made. (This is exactly what happened today). &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a minimum time between triggering that needs adjustment somewhere?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This seems to be a recent change - before I would always get the 7:40 event and the 7:50 event - which is what I want to happen so I can make sure everything is locked up properly and the kids are off to school on time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This could also be a risk if someone comes up - sees the camera, retreats - then comes back forces the door, covers camera etc to penetrate. &amp;nbsp;I would never know the second thing happened.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2017 13:21:57 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238032#M8238</guid>
      <dc:creator>ThermoDyn</dc:creator>
      <dc:date>2017-02-28T13:21:57Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum time between triggers</title>
      <link>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238050#M8240</link>
      <description>&lt;P&gt;That shouldn't be happening. &amp;nbsp;There is a reset period but it's on the order of 15-30 seconds at most. My guess would be that your wife isn't presenting the same target that you or Amazon is - size, path, speed, something that isn't catching her. &amp;nbsp;You likely should spend some time testing to see if increasing sensitivity or camera position or something else would help.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2017 13:38:54 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238050#M8240</guid>
      <dc:creator>jguerdat</dc:creator>
      <dc:date>2017-02-28T13:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum time between triggers</title>
      <link>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238133#M8245</link>
      <description>&lt;P&gt;Interesting - ok - I will test this some more. I have the sensitivity up around 80% and it gets her when she comes home in the afternoon so I don't think that is the issue. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think it might have happened becuase I was live viewing at the time. &amp;nbsp;Not actually watching but listening.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So basically - if you are live viewing through the app - the motion doesn't trigger a recording.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have I got that right?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2017 15:52:17 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238133#M8245</guid>
      <dc:creator>ThermoDyn</dc:creator>
      <dc:date>2017-02-28T15:52:17Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum time between triggers</title>
      <link>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238189#M8256</link>
      <description>You got it. Li e view would be a definite reason.</description>
      <pubDate>Tue, 28 Feb 2017 16:55:11 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238189#M8256</guid>
      <dc:creator>jguerdat</dc:creator>
      <dc:date>2017-02-28T16:55:11Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum time between triggers</title>
      <link>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238200#M8258</link>
      <description>&lt;P&gt;&lt;STRONG&gt;So basically - if you are live viewing through the app - the motion doesn't trigger a recording.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As mentioned ,Yes.&lt;/P&gt;
&lt;P&gt;Live view over rides the ARMED record mode...tho you can manually start a record session any time you are live viewing by clicking on the "target" icon&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2017 17:11:33 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238200#M8258</guid>
      <dc:creator>TomMac</dc:creator>
      <dc:date>2017-02-28T17:11:33Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum time between triggers</title>
      <link>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238775#M8329</link>
      <description>&lt;P&gt;Perfect - thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 01 Mar 2017 12:06:28 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo-Pro/Minimum-time-between-triggers/m-p/1238775#M8329</guid>
      <dc:creator>ThermoDyn</dc:creator>
      <dc:date>2017-03-01T12:06:28Z</dc:date>
    </item>
  </channel>
</rss>

