Please stop making up “theories” to fit the limited observations you’ve had. They just don’t fit the facts. Please spend some time perusing this forum and/or the official documentation. SD cards aren’t used to buffer cloud recordings. There is no 4 second recording before a motion event. I’m not going to address each point further because frankly you’re kind of just making them up.
Perhaps some of the other regulars will have more patience to explain.
Unfortunately this tangent is detracting from the valid concerns raided about the excessive DNS queries.
Edit: here are a couple of old threads that may help; the information is still mostly valid
Well if that is the case, then that is a really bad method of handling cloud recordings, and it would explain why I often get “could not upload” errors when I try to view cloud recordings - not buffering the recording means you only have one shot to get the video sent to the cloud or else the video is lost if there was any error. But if you used the memory card first, then you could try multiple times to upload the video to the cloud because you will not “loose” the original recording thats stored on the sd card.
Fair enough, it might be nice to reserve such space on an available card but I’m nearly certain Wyze does not. You can understand why, since SD use is optional.
As it stands I think the camera stores to its local memory and then uploads in 1 or 2 minute chunks; I am NOT sure how exactly that works.
Edit: it’s 1 minute chunks when recording to SD card but it would have to be much smaller chunks for 12 second non-CamPlus recording; I don’t think I’ve seen a precise breakdown of the timetable / workflow
I don’t understand why you think this - You can play ANY video or sound event recording and the green motion box or the detected sound do NOT start immediately at the 0:00 mark- they always start a few seconds in. So if there was no CONTINUOUS loop recording, it would be IMPOSSIBLE to have a few seconds of silence before you heard the sound event or a few seconds of video before the green motion detect box is displayed.
When I diagnose a problem, I come up with a theory, then see if my observations fit that theory and if not, I come up with a new theory.
But the bottom line is that if you do not have a memory card in a v3 camera, it seems to screw up wifi for other devices. And the only thing I can think of is that the camera is somehow overloading the wifi network almost like a DoS attack - which is why I thought this might be related to this thread’s massive DNS traffic issue.
I see a huge number of comments on this thread but what I cannot determine if it was ever resolved.
My case: WyzeCam v3, FW 4.36.8.15 (reported as current): More than 1000 DNS queries in a single hour, as reported by my PiHole.
@WyzeBaohua : Can you (or anyone else) provide a status update on this issue? Any alternative other than removing this defective product from the network?
I just saw this. It was so bad that my pihole became overloaded just trying to look at all the DNS queries by clicking on this client on the dashboard, and would crash it for a while.
I upgraded the firmware on it, and it seems to have fixed it:
I see this with my WyzeBot Vacuum. multiple (5) DNS requests every 1-2 mins to time servers. Previous WyzeBot (replaced) would do the same and also disconnect from network periodically.
Same experience here with my pihole. Currently 2.5 million requests over 9 hours. My log over 24 hours is usually around 10-15mb, currently after 9 hours its 234mb. Trying to grep out and wc to verify down to the exact number but I think its (pihole) locked it up again since there’s so many entries. I’ve invested about $2k in Eufy cameras\bulbs\switches\etc. and was testing this camera (Wyze v3 Inside\Outside, firmware 4.36.9.139, SD card installed) since I’m not impressed with Eufy’s AI. But at least with Eufy I don’t have to deal with this. Kicking all Wyze off my network and on ebay it goes. As do the Wyze bulbs and switches I bought thinking of replacing my Eufy’s with those as well. Arrggh just remembered I bought the lock also which luckily I haven’t installed yet so I can get my money back there.
FYI: I had to physically unplug the thing to get the requests to stop. Merely disabling it in the app didn’t stop the dns queries.
Should also mention for those who have theories, I did notice that several of my SD card video’s didn’t upload fully to the cloud. Only about the first frame. My pihole puts you on the no no list after making too many queries so I’m guessing that is what’s happening. But I’m going to go enjoy the free market and stop complaining now.
Yup. this continues. Here’s a screen grab of my PiHole’s activity this morning…
That grey bar represents 1000 DNS inquiries in a period of ten minutes from a single WyzeCam. That’s 16.7 per second – before the PiHole said “enough” and halted the activity! (For comparison, the other colors shown on the same bar represent the DNS inquiries of the other 37 devices on the network.)
It’s interesting that Wyze is totally silent on this issue. Help tickets have not brought resolution and Wyze cannot say “we did not know.” One can only conclude the activity is intended and for nefarious purposes. Has Wyze built DDoS bots here?
I can’t help but wonder if one day we’ll be reading about Wyze alongside HikVision, Dahua, Huawei and other agents of Poo Bear and his PLA.
It’s ridiculous. It’s still unplugged and if I get some time I’m going to solder on some header pins and try to download the firmware. Then just grep for Google.com and see what classes and functions are doing with it. Needless to say I’m no longer a Wyze customer.
Taking a look a one of the routers’ outbound connection s this morning we see the massive number of DNS inquiries continues, Below follows an image of one of the WyzeCams making repeated contacts with Google DNS at 8.8.8.8. How can Wyze fins this to be acceptable? This is just one of many similar pages. Hundreds of queries from this rogue device!
