# An update regarding Person Detection

**URL:** <https://forums.wyze.com/t/an-update-regarding-person-detection/73107>\
**Category:** Wyze News\
**Tags:** important, person-detection\
**Created:** [November 26, 2019, 8:23pm UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107 "2019-11-26T20:23:34Z")\
**Posts on this page:** 20\
**Page:** 11

<div class="post-metadata">

**Author:** ![R\_T](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@R\_T](https://forums.wyze.com/u/R_T)\
**Post date:** [December 10, 2019, 2:21am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/201 "2019-12-10T02:21:47Z")

</div>

> [@secondary\_2g](#):
>
> My understanding of person detection is that it’s a notification filtering layer for motion events.

That make no sense from a development perspective. If the only motion that’s of interest is ‘people’ why incur the overhead of managing (transmitting, storing, etc.) non-people motion only to suppress notifications.

If it is a notification filter as you suggest it should be clearly documented as such.

---

<div class="post-metadata">

**Author:** ![secondary\_2g](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/secondary_2g/32/14701_2.png) [@secondary\_2g](https://forums.wyze.com/u/secondary_2g)\
**Post date:** [December 10, 2019, 2:23am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/202 "2019-12-10T02:23:24Z")

</div>

Only echoing what I believe I came across in another thread. Will paste the link if I rediscover it.

---

<div class="post-metadata">

**Author:** ![qlang243](https://avatars.discourse-cdn.com/v4/letter/q/b19c9b/32.png) [@qlang243](https://forums.wyze.com/u/qlang243)\
**Post date:** [December 10, 2019, 2:23am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/203 "2019-12-10T02:23:52Z")

</div>

> [@R\_T](#):
>
> Exactly - it’s a refinement (or should be) of what constitutes ‘motion’.

Are you implying that for there to be “motion”, there should be a “person”? That’s what this statement seems to be saying.

---

<div class="post-metadata">

**Author:** ![R\_T](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@R\_T](https://forums.wyze.com/u/R_T)\
**Post date:** [December 10, 2019, 2:27am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/204 "2019-12-10T02:27:54Z")

</div>

> [@qlang243](#):
>
> Are you implying that for there to be “motion”, there should be a “person”? That’s what this statement seems to be saying.

Yes, if person detection is turned on it _refines_ the definition of motion as it must be identified as a ‘person’. If person detection is off than the ‘original’ definition of motion applies.

---

<div class="post-metadata">

**Author:** ![UserCustomerGwen](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/usercustomergwen/32/75644_2.png) [@UserCustomerGwen](https://forums.wyze.com/u/UserCustomerGwen)\
**Post date:** [December 10, 2019, 2:28am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/205 "2019-12-10T02:28:06Z")

</div>

I can confirm that the person detection was run on already existing videos and it only enabled tags for people being detected and limited notifications. It didn’t reduce the number of videos but we’re interested in that in the future (though can’t make promises that this will happen).

---

<div class="post-metadata">

**Author:** ![qlang243](https://avatars.discourse-cdn.com/v4/letter/q/b19c9b/32.png) [@qlang243](https://forums.wyze.com/u/qlang243)\
**Post date:** [December 10, 2019, 2:31am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/206 "2019-12-10T02:31:03Z")

</div>

> [@R\_T](#):
>
> If person detection is off than the ‘original’ definition of motion applies.

You’re redefining what the options mean. And that’s not the way it happens in practice. Cite a Wyze statement, publication or document that says that.

---

<div class="post-metadata">

**Author:** ![R\_T](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@R\_T](https://forums.wyze.com/u/R_T)\
**Post date:** [December 10, 2019, 2:32am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/207 "2019-12-10T02:32:54Z")

</div>

> [@UserCustomerGwen](#):
>
> I can confirm that the person detection was run on already existing videos and it only enabled tags for people being detected and limited notifications. It didn’t reduce the number of videos but we’re interested in that in the future (though can’t make promises that this will happen).

Good to know. How I thought it works is incorrect. It would be more efficient from a data utilization perspective if it were a refinement of the what constitutes motion rather that being a notification filter.

---

<div class="post-metadata">

**Author:** ![UserCustomerGwen](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/usercustomergwen/32/75644_2.png) [@UserCustomerGwen](https://forums.wyze.com/u/UserCustomerGwen)\
**Post date:** [December 10, 2019, 2:35am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/208 "2019-12-10T02:35:13Z")

</div>

It would! But it’s also harder and the risk of false positives or negatives carries greater weight. It is more tricky to do that with the hardware limitations of the device.

---

<div class="post-metadata">

**Author:** ![R\_T](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@R\_T](https://forums.wyze.com/u/R_T)\
**Post date:** [December 10, 2019, 2:36am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/209 "2019-12-10T02:36:18Z")

</div>

> [@qlang243](#):
>
> You’re redefining what the options mean. And that’s not the way it happens in practice. Cite a Wyze statement, publication or document that says that.

It’s a moot point now that @UserCustomerGwen has confirmed that ‘person detection’ is nothing more than a notification filter versus a refinement of what constitutes motion.

---

<div class="post-metadata">

**Author:** ![R\_T](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@R\_T](https://forums.wyze.com/u/R_T)\
**Post date:** [December 10, 2019, 2:41am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/210 "2019-12-10T02:41:22Z")

</div>

> [@UserCustomerGwen](#):
>
> It would! But it’s also harder and the risk of false positives or negatives carries greater weight. It is more tricky to do that with the hardware limitations of the device.

I guess that begs the question of why it was decided to put the function in the firmware versus a server side function. I realize that server load has to be considered but if it can be successfully implemented in the F/W of a limited capability device the increased server load couldn’t be all that great.

I really don’t expect an answer but it would be an interesting discussion in which to participate.

---

<div class="post-metadata">

**Author:** ![UserCustomerGwen](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/usercustomergwen/32/75644_2.png) [@UserCustomerGwen](https://forums.wyze.com/u/UserCustomerGwen)\
**Post date:** [December 10, 2019, 2:56am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/211 "2019-12-10T02:56:58Z")

</div>

If I recall correctly, it was faster to run in some ways (not all), security-conscious people appreciated the algorithm not happening on a cloud, and it didn’t require the cloud resources. I also know that we were hoping to be able to work it into a limiter someday. There are probably many other portions of this conversation but I wasn’t involved with them. These are just the things I heard about directly.

---

<div class="post-metadata">

**Author:** ![masterep](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@masterep](https://forums.wyze.com/u/masterep)\
**Post date:** [December 10, 2019, 4:30am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/212 "2019-12-10T04:30:04Z")

</div>

Gwendolyn,

Question. Given that the new online subscription transfers videos from the Wyzecams to the cloud after it has been triggered, my question is, are there guidelines to the number of Wyze devices that can be on the a single residential internet service for a certain upload speeds, given an assumed coincidence transfer load factor for the Wyzecams?

For example my service is 20 Mbps upload rate. Live streams of Wyzecam feeds using either an iOS application or a PC Android emulator, is three (3), anything more and my feeds becomes unstable and all the cameras disconnect, one by one, until there is just one streaming camera feed. I currently have 11 Wyzecams with more on the way and I’m concerned with the growing overhead on the upload stream.

Reflecting on the old Wyze Maxdrive/NAS development - there were far wider reaching and stronger benefits for the user’s holistic home experience with that solution as customers continue to grow its use of IOT products and other family needs without spending more dollars for faster internet upload service speeds.

---

<div class="post-metadata">

**Author:** ![nerdland](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/nerdland/32/11816_2.png) [@nerdland](https://forums.wyze.com/u/nerdland)\
**Post date:** [December 10, 2019, 6:02pm UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/213 "2019-12-10T18:02:04Z")

</div>

> [@UserCustomerGwen](#):
>
> I also know that we were hoping to be able to work it into a limiter someday.

What does that mean exactly? It sounds intriguing. I know it’s moot for now since the feature in its current form is going away, but I’m still curious what you’re talking about.

---

<div class="post-metadata">

**Author:** ![UserCustomerGwen](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/usercustomergwen/32/75644_2.png) [@UserCustomerGwen](https://forums.wyze.com/u/UserCustomerGwen)\
**Post date:** [December 10, 2019, 9:37pm UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/215 "2019-12-10T21:37:33Z")

</div>

We were hoping to develop person detection to eventually be able to reduce the number of Event videos in a way discussed previously in this thread. But that was a longer term project idea. 🙂

---

<div class="post-metadata">

**Author:** ![secondary\_2g](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/secondary_2g/32/14701_2.png) [@secondary\_2g](https://forums.wyze.com/u/secondary_2g)\
**Post date:** [December 10, 2019, 9:51pm UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/216 "2019-12-10T21:51:41Z")

</div>

I dig long-term projects 🕶

---

<div class="post-metadata">

**Author:** ![nerdland](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/nerdland/32/11816_2.png) [@nerdland](https://forums.wyze.com/u/nerdland)\
**Post date:** [December 10, 2019, 11:02pm UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/217 "2019-12-10T23:02:01Z")

</div>

Cool. Hopefully that will still come eventually. 🙂

---

<div class="post-metadata">

**Author:** ![lr00429](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/lr00429/32/14750_2.png) [@lr00429](https://forums.wyze.com/u/lr00429)\
**Post date:** [December 11, 2019, 6:00am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/218 "2019-12-11T06:00:52Z")

</div>

Any chance that the Wyze person dectect will be better. Maybe add pet detection?

---

<div class="post-metadata">

**Author:** ![Kaloy](https://avatars.discourse-cdn.com/v4/letter/k/71c47a/32.png) [@Kaloy](https://forums.wyze.com/u/Kaloy)\
**Post date:** [December 11, 2019, 7:21am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/219 "2019-12-11T07:21:20Z")

</div>

> [@masterep](#):
>
> Reflecting on the old Wyze Maxdrive/NAS development - there were far wider reaching and stronger benefits for the user’s holistic home experience with that solution as customers continue to grow its use of IOT products and other family needs without spending more dollars for faster internet upload service speeds.

I’m with you @masterep, exactly what I’ve been pointing out too. I’m not against their online/cloud services their offerings, but I hope they develop their products in a way that its still usable/functional offline on local Wifi/LAN. Internet had become widely available and getting cheaper, but as well as devices that consumes/using it, so on a regular household its easily getting congested. Your product price range targets common, middle, value and budget wise people, but its becoming a “catch” that it requires premium internet subscription, premium wifi router and maybe soon including cloud service will be required to for it to function properly. Same as @masterep; I think its better to have a hub / NAS / NVR for all the Wyze cams and smart things.

---

<div class="post-metadata">

**Author:** ![gemniii](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/gemniii/32/5776_2.png) [@gemniii](https://forums.wyze.com/u/gemniii)\
**Post date:** [December 11, 2019, 9:03am UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/220 "2019-12-11T09:03:58Z")

</div>

> [@Kaloy](#):
>
> Your product price range targets common, middle, value and budget wise people, but its becoming a “catch” that it requires premium internet subscription, premium wifi router and maybe soon including cloud service will be required to for it to function properly.

And also a newer device. My Samsung J3 is now showing significant video lag again. Made it difficult to position a V2 while hanging out a second story window and having to wait 20 seconds every time I moved the camera to a different FOV.  
A $200 device upgrade solved the problem, but that is the equivalent of 10 V2’s.  
It’s like buying an inexpensive item that requires an expensive infrastructure to be effective.

---

<div class="post-metadata">

**Author:** ![RickyS2552](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/rickys2552/32/9932_2.png) [@RickyS2552](https://forums.wyze.com/u/RickyS2552)\
**Post date:** [December 11, 2019, 12:42pm UTC](https://forums.wyze.com/t/an-update-regarding-person-detection/73107/221 "2019-12-11T12:42:31Z")

</div>

I second this.  
For some camera I do want to be notified for dog, for another not. The current implementation set only to detect a person, always triggers when my dog passes by.

[Previous page](https://forums.wyze.com/t/an-update-regarding-person-detection/73107.md?page=10)

[Next page](https://forums.wyze.com/t/an-update-regarding-person-detection/73107.md?page=12)
