My 4 OGs (but not my OG Telephoto) updated to 1.0.82 from 1.0.80 last night. There are no release notes that I can find for 1.0.82 (just the beta that isn’t specific)? It also broke detection zone, all 3 cameras that have it enabled (one doesn’t) started detecting stuff anywhere in the field of view. Luckily toggling detection zone off then back on for each camera seems to fix it.
I’m not signed up for beta firmware so I shouldn’t be getting pre-release, but the release notes still say 1.0.80 is the latest.
1.0.82 was undergoing beta testing for Cam OG last month. It’s probably in the process of being pushed out to production and the release notes haven’t been updated yet. “Improved connectivity with Wyze Web Portal” aside, I’m not sure what “bug fixes” were included in 1.0.82, but my OGs running this version have been stable over the past month.
Yes, I use detection zone on all of my cams. My OGs didn’t have your issue during beta testing though. Thank your reporting. I’ll keep an eye out for others reporting the same.
Also… assuming Wyze will be announcing this as a production firmware update soon, do you mind if I merge this topic with the announcement for posterity? Your findings and solution may prove useful to others who may encounter the same.
I do think that the time to load the camera in the app is significantly improved. Because my cameras are on an isolated wifi network and can’t talk to my phone directly, my stream is going via Wyze’s servers, so maybe the improved connectivity to the web portal has something to do with that also.
Well it would appear the “fix” of toggling detection zone off then back on worked for exactly 1 day, just had to do it again… Need a fix or a roll back.
Now I’ve attempted toggling off and on and then restarting each cam. Maybe that will make it stick. Odd that the bug seemed to recur exactly 1 day later.
@dave27 Since your are toggling things on and off you may want to toggle off the automatic firmware updates so you don’t have any future surprises. I have it turned off on all of my cameras because I want to see what is in the update prior to venturing into the unknown.
I would tend to agree, though I don’t see that as an option in the settings for my Cam OG (nor for my Cam Pan v3s); however, I do have it turned off for my Cam v4s and Video Doorbell v2. Based on that, I’d be inclined to think that camera models that apparently don’t have an Automatic Update setting will prompt the user prior to installing firmware updates, but that might not account for what @dave27 described in the original post, so I’m a little confused (which isn’t entirely unusual for me).
I don’t have an OG, just V3 cams, a V3 PRO , V4 and WCO v1 and they all have the option to turn off auto updates. I thought all cams were like that. Makes no sense to me why some cams do not?
I actually don’t have any automatic update, never had an issue before so I just tapped to update when it prompted me. Guess I should wait a couple days and check here first.
I agree. I think I’ve said elsewhere on the Forum that I’d like to see more consistency across the camera interfaces (but I’m also aware that some users have strong preferences for the “old” vs. “new” camera control UI).
Thanks for clearing that up. I wondered if that was the case but wasn’t sure from the initial post.
Toggle the zone off and back on, it should fix it for a while. I’m not sure if this is actually firmware related or if that is just a coincidence, there is another thread with someone’s v4s not following detection rules and it started around the same time (possibly related to the global IT outage thing, who knows). When did you update your firmware?
Edit:
Well around 5pm(here) I did try the detection off/on toggle you suggested. It temp worked for about 2 hours 20 min before randomly detecting in the gray zones again.
Same here, and that seems to be when the person with the v4 starting having smart detection issues (and also the day of the big outage). So it is unclear at this point if it is firmware related or not. Though it did seem to start happening immediately after applying the firmware update, it could just be because that’s the first time the cams rebooted after whatever server issue they may be having started…
