I have only performed bench testing on tagging within the Detection Zone on the V3, which does respect the DZ when tagging… provided an object isn’t slightly overlapping into the included\unblocked DZ. If any part of the object is in the included\unblocked DZ, the entire object is considered by the AI tagging engine even if the vast majority of the object is blocked.
As I understood it, this was a feature change to the firmware so each cam would have to be updated to firmware including the logic. I have not read any definitive info as to which cams have this logic so there is no way for me to confirm with certainty if it has been rolled out on all cams without bench testing each model I have.
I recently had a situation where my online OG cams stopped uploading events. A power cycle was required to remedy the issue.
I just did a walk around on all my cams. All are subscribed to CP Unlimited, upload all motion events, notify only on Person Detection & other select AI, all running latest available Beta or Production Firmware, latest Android Public Release App.
All cams returned Person Event uploads. All but 1 V3 cam pushed a Person Detected Notification:
V3 - 9 Cams
PanV3 - 4 cams
V3 Pro - 1 Cam
Floodlight Pro - 1 Cam
OG Cams - 1 S, 1 T
So, the cameras I’m testing this on to help out @wam is a v3 and a v2. They use a v3 from what i understand.
The issue I have is that these 2 cameras of mine are used on my bird feeders and I primarily use it to watch the hummingbirds, so I have the detection zone very very small so it doesn’t pick up passing cars or my driveway.
It does catch me when I go fill them and it shows up in events (I have all motion detection on), BUT in the events list they aren’t tagged as people.
I did restart the cameras yesterday and no change. So, perhaps I do need to fiddle with the detection zone temporarily to see if I can recreate what Wam is experiencing.
I do use detection zones on many of the cams I listed, however I can’t be sure how much of me was within each included\unblocked DZ without getting really deep into the events recorded and overlaying them with the current DZ on each individual cam using one.
Those are super tight. I can’t comment on the V2 since I don’t have one to test. It has been a long time since the DZ overlap logic was added to the V3 and I tested it, but I can’t imagine it has changed in the V3 without an announcement somewhere.
Assuming the logic is still there, if you are creating motion anywhere in the unblocked areas, it is supposed to consider you and tag you even though you overlap the DZ separation. If it is no longer there, it should absolutely be tagging you. Previously, the DZ was completely ignored by the AI Tagging Engine and any object within the entire FOV was considered if there was motion in the unblocked DZ.
Not sure if this is what is happening, but it looks like you don’t have Person selected as an Event filter. If all filters have been cleared, the Person events should still show, but I have found that the cam specific filters have been acting flakey lately.
Check your filter management UI and specifically select the two cams, Person, and Motion at the bottom and see if it changes anything.
Regardless, if you aren’t getting notifications w\ Person notifications selected in the Device Notifications UI, there probably aren’t any tags there to see.
they update the software very frequently, so if you’re waiting months to update, it won’t make much of a difference as it will update you to the most recent. I’m on the beta app and beta firmware, to test stuff out before it goes live for everyone.
Nope… The last firmware has been released months ago.
With the app updated it’s still happening. Looking for configuration issues is a waste of time. Wyze is the problem, or most likely their buggy firmware as stated by a member earlier.
It’s happening on one on my cam, or both, or the other one, it starts malfunctioning, then start working again 2 days latter without doing anything, it’s not related to dz, filters or whatsoever !
Events are just not uploaded to the wyze cloud, or the cloud is discarding them, don’t know which one…
Thanks wyze for brushing it off, and to left us with a useless monitoring for the holidays !
Will stop recommending wyze from now on, and even discourage people to buy, too many problems the staff is absolutely not interested in fixing, don’t want to antagonize friends with this crap…
If it was subscription free, I could still understand this “bad” choice, but now, ring or other companies are making much more reliable products…
Ok it’s the firmware, 100% sure, downgraded one cam, no more problem, the other keeps bugging. Again thank you wyze for
Keep pushing a defective firmware months after its release
Playing it silent with absolutely no communication on this issue and even trying to mislead users
I can’t even downgrade the other cam since it’s on a very hard to reach location, I have to wait for an unknown amount of time for wyze to fix its stupid firmware and release an update.
You implied that you are not located in North America. Where are you located and what Internet service provider are you using? Are you running a router-based VPN or using a proxy service, or the same on your phone/tablet? If so, try disabling it to see if your issues resolve.
You mentioned that you are certain it is now Firmware related and that you downgraded. But, I’m not seeing in any of your posts which version of the firmware you had\have the cams running. Also not clear which version you used to Flash back.
4.36.11.4679 is the latest V3 Production Release firmware available.
If the cam is inaccessible for a Flash reversion, have you considered entering the Beta pool and installing the 4.36.11.4847 Beta Firmware currently in testing, which I have been successfully running on all my V3 cams since it was released? This will allow you to update thru the standard OTA cam firmware update channels. You can then turn off future Beta update opportunities or leave the Beta pool. It is worth a shot so that you may not have to flash that cam.
