Hey all - First time posting, long time Wyze cam owner! So I purchased the duo doorbell camera a few months ago, I live in a rental so it’s battery operated without another choice. My problem is the event capturing is recording after the person is no longer in the frame, unless someone stops and is at my door (such as me coming home) for a few seconds, I’m now lucky to get the back of their heel as they have finished passing thru. Usually it’s nothing now.
I’ve had the camera three months, out of the box it initially was capturing people walking by. I’ve adjusted all the settings but doesn’t change anything. Detection sensitivity is at high. SD card barely has anything on it. Nothing changed to my knowledge with my internet speed. Any ideas? It’s really frustrating I was going to move it to record constantly but that’s not an option on battery power. I have a neighbor who was harassing me and the camera is meant to capture when she’s wandering around my door but it no longer does that.
If I was on the board of directors for this company, there would be some heads rolling.
This thing is USELESS as a security camera for notifications.
Someone could bust down my door and be all the way across my house before I would ever get a notification!
I had a 200meg down/20 meg up internet connection and THIS is pitiful.
Total waste of money for what it is intended to do.
I had a contractor come to my door, push the doorbell and by the time I got to the door, he was already out to the sidewalk by the street!
I should have spent the extra and went to RING instead…
I unloaded groceries from my car parked 12 feet from the doorbell and was already in the kitchen sitting them on the counter before any announcement came over my speakers and doorbell chime alert…
I will never recommend this product until they FIX this crap.
Thanks for the reply. In my case it was working fine and notifying promptly… so it is capable of doing so and I replaced a Ring with this because while Ring was better image quality, the dual camera and ability to use with out a subscription was more compelling for me.
Though I’m starting to wonder if Wyze is making it work poorly trying to get you to buy a subscription :/. Since I haven’t had any feedback here I’ll paste the advice Wyze bot sent for others to read. I’ve tried most of these with no luck besides the battery removal and hard reset options towards the bottom, it’s such a pain to take apart I haven’t wanted to deal with trying those but I also shouldn’t have to, this is really disappointing.
Update the Wyze App: Ensure that your Wyze app is up to date. Go to the Account tab in the app, tap About, and check your app version against the latest version on our Release Notes & Firmware page.
Check Firmware: Verify that your Wyze Duo Cam Doorbell’s firmware is current. You can check this in the Account tab under Firmware Update.
Event Recording Settings: In the Wyze app, navigate to the doorbell’s settings, then Event Recording. Make sure Motion is enabled and select All Events. Under Customize Detections, ensure that the boxes for both the Tag and Notify columns are checked.
Detection Settings: Go to the Detection Settings in the doorbell’s settings. Adjust the Motion Detection Sensitivity to High and toggle off the Detection Zone while testing.
Power Cycle the Doorbell: If your doorbell is battery-powered, remove the battery pack for 10 seconds and then reinsert it. If it’s hardwired, flip the breaker that powers the doorbell off for 10 seconds and then back on.
Factory Reset: If the issue persists, consider performing a factory reset. Remove any microSD card, press and hold the RESET button on the back of the doorbell for 5 seconds until you hear a voice prompt, and then set it up again as a new device.
Check for Interference: Ensure there are no Automations set up that could be causing interference. You can delete any existing Automations and add them back one by one while testing.
Thanks for that wealth of info you provided.
I’ve actually done everything there before I came on the forum and nothing helped.
YET…
I have been a wyze user for 2 or 3 years.
Having owned the previous Wyze doorbell PRO, the heat from the concrete the mount was on made the mounting tabs on the backing plate weak and broke off, They don’t sell that part, of course, being the weakest link, forces you to purchase a new one.
The old one was a “little” better in notifications but this one really stinks..
I’ve even gone as far as setting a Manual IP assignment in my ASUS router.
Waiting to see if that helps at all.
It is on my 5g wifi.
My last resort will be to move it to 2.4G… Which my 2.4 is more crowded.
This doorbell supporting 5g was one of the selling points for me…
I have a variety of their cameras. About 5 or 6 of them .
I also find it funny that Although I have their cam+ subscription, when I go to their WEB app, some of their cameras don’t even connect to the WEB app but they DO show up working on the Android phone app…
I’m also on their BETA program…
I’m just not a very happy customer of theirs right now even though I WAS in the past…
Basically, the only Automation I have enabled is the one for their connection to my Amazon Alexa devices for announcements… (well, and their own chime)…
I also find it interesting that their own support people don’t comment much on here…
Customer support leaves a lot to be desired when your only option is on here and to LIVE chat…
I am not patient enough to do their live drawn out chat where you try to explain to them you’ve tried everything within your 28 years of Computer and networking experience dating back to the old Commodore 64/IBM PC XT DOS-Basic-Windows 2.0 days and probably have more experience than their whole team put together.
I am currently a network support specialist contractor for State government…
Thank you once again for that info. Maybe with some new firmware updates, they will fix the latency issue…
FYI… As I was typing this, I was running a “ping” on the IP address assigned to it,
It dropped over 30 packets and picked back up…started replying again…
Here is just a short clip of the results…
Reply from 192.168.0.169: bytes=32 time=45ms TTL=64
Reply from 192.168.0.169: bytes=32 time=48ms TTL=64
Reply from 192.168.0.169: bytes=32 time=57ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.169: bytes=32 time=44ms TTL=64
Reply from 192.168.0.169: bytes=32 time=39ms TTL=64
Reply from 192.168.0.169: bytes=32 time=46ms TTL=64
Reply from 192.168.0.169: bytes=32 time=32ms TTL=64
Reply from 192.168.0.169: bytes=32 time=46ms TTL=64
Reply from 192.168.0.169: bytes=32 time=62ms TTL=64
Reply from 192.168.0.169: bytes=32 time=72ms TTL=64
Reply from 192.168.0.169: bytes=32 time=74ms TTL=64
Reply from 192.168.0.169: bytes=32 time=75ms TTL=64
Reply from 192.168.0.169: bytes=32 time=80ms TTL=64
Reply from 192.168.0.169: bytes=32 time=101ms TTL=64
Reply from 192.168.0.169: bytes=32 time=14ms TTL=64
Reply from 192.168.0.169: bytes=32 time=105ms TTL=64
Reply from 192.168.0.169: bytes=32 time=16ms TTL=64
Reply from 192.168.0.169: bytes=32 time=22ms TTL=64
Reply from 192.168.0.169: bytes=32 time=26ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.169: bytes=32 time=4ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=9ms TTL=64
Reply from 192.168.0.169: bytes=32 time=4ms TTL=64
Reply from 192.168.0.169: bytes=32 time=4ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=3ms TTL=64
Reply from 192.168.0.169: bytes=32 time=3ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=43ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=10ms TTL=64
Reply from 192.168.0.169: bytes=32 time=7ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=3ms TTL=64
Reply from 192.168.0.169: bytes=32 time=1ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=3ms TTL=64
Reply from 192.168.0.169: bytes=32 time=2ms TTL=64
Reply from 192.168.0.169: bytes=32 time=5ms TTL=64
Ping statistics for 192.168.0.169:
Packets: Sent = 97, Received = 66, Lost = 31 (31% loss),
I just noticed something else interesting.
Packet flow (Pings) stop whenever the App quits and you stop live viewing…
TCP/IP flow dies…
THAT does not support a good reliable WIFI connection in my opinion…
All of those “time out” errors above, occur every time I close the app. I was running Ping command from my PC and opening and closing the app on the phone…
Be careful of your final conclusion. I do not have a duo but do have 3 battery cam pros. To conserve power they do not respond to pings as they are in an extreme low power state. If they are responding to an event (motion trigger) or being accessed by the app (viewing) they will respond to a ping. I’ve noticed they continue to respond for a few seconds after you close the app.
I’ll dwell on your bigger issue time permitting.
p. s. a more valid test would be leave the app open and viewing while running your ping from a pc. You are sniffing around the problem. Keep sniffing.
That technique of theirs may explain the latency. If the device has to reconnect to the WIFI router each time, It may take a few seconds to validate the connection. Especially if using DHCP and something else grabbed the previous IP address… Just guessing…
I went out to my car 12 feet away, came back in the house and was sat down when the alert finally came in. The old PRO doorbell worked better. This one certainly needs tweaking more.
Thanks for your response.
