Wyze Doorbell v2 repeatedly disconnecting - possible solution?

Cameras
, ,
1

I’m at the end of my rope.

My Wyze Video Doorbell 2 constantly drops off the network. This happens roughly every 20-40 hours, but sometimes much more frequently. Today, for example, it happened at least twice. Sometimes I get a notice that the camera is offline. Sometimes I don’t and I only find out about it because it missed an important event or because I go to check in and get the “offline” error.

This appears to be a widespread issue with many forum reports, but I’m not seeing any fixes. Has anyone identified a cause yet? Some answers to common suggestions:

  • I’m on Verizon FIOS, not AT&T
  • I have a 300/300 connection – more than enough bandwidth
  • WiFi signal at the doorbell is decent
  • My access point is 2.4 GHz only. I have confirmed, re-confirmed, and triple-confirmed that the 5 GHz radio is turned off. There is no band steering.
  • The issue happens on access points from three different vendors: TP-Link, Zyxel, and Ubiquiti
  • Voltage at the doorbell is constantly between 18.4V - 19.0V from a 16V 40VA transformer
  • Firmware version is 4.51.3.6791
  • Only the Wyze Video Doorbell 2 is affected. None of my v4 cams have any problems.
  • I have had no problems with doorbells from Nest or Ring

Here’s the kicker: I have been battling this for over a year, and I eventually assumed my doorbell was just defective. I bought a replacement unit off Amazon about two weeks ago. The new unit has the exact same issues at roughly the exact same frequency. This tells me this isn’t a single defective unit, but an undocumented compatibility issue.

My access point logs are filled with errors like this for this device only when it drops:

2026-08-07 00:52:57 - 80:48:2c:ab:35:57 connected on Channel: 1, SSID: redacted_SSID, 2.4GHz, Security: WPA2_PSK, Signal: -61dBm, Interface: wlan-1-1
2026-08-07 00:51:29 - 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: redacted_SSID, 2.4GHz, Signal: -62dBm, Download/Upload: 0Bytes/0Bytes, reason 2, Interface: wlan-1-1
2026-08-07 00:50:28 - 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: redacted_SSID, 2.4GHz, Signal: -62dBm, Download/Upload: 0Bytes/0Bytes, reason 2, Interface: wlan-1-1
2026-08-07 00:49:57 - 80:48:2c:ab:35:57 disconnected by STA reconnect on Channel: 1, SSID: redacted_SSID, 2.4GHz, Security: WPA2_PSK, Signal: -62dBm, Download/Upload: 0Bytes/0Bytes, reason 8, Interface: wlan-1-1
2026-08-07 00:48:38 - 80:48:2c:ab:35:57 disconnected by STA reconnect on Channel: 1, SSID: redacted_SSID, 2.4GHz, Security: WPA2_PSK, Signal: -59dBm, Download/Upload: 0Bytes/0Bytes, reason 8, Interface: wlan-1-1
2026-08-07 00:48:14 - 80:48:2c:ab:35:57 disconnected by STA reconnect on Channel: 1, SSID: redacted_SSID, 2.4GHz, Security: WPA2_PSK, Signal: -62dBm, Download/Upload: 0Bytes/0Bytes, reason 8, Interface: wlan-1-1
2026-08-07 00:47:39 - 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: redacted_SSID, 2.4GHz, Signal: -62dBm, Download/Upload: 0Bytes/0Bytes, reason 2, Interface: wlan-1-1
2026-08-07 00:46:58 - 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: redacted_SSID, 2.4GHz, Signal: -62dBm, Download/Upload: 0Bytes/0Bytes, reason 2, Interface: wlan-1-1
2026-08-07 00:46:26 - 80:48:2c:ab:35:57 blocked by key handshake fail on Channel: 1, SSID: redacted_SSID, 2.4GHz, Security: WPA2_PSK, Signal: -62dBm, Download/Upload: 0Bytes/0Bytes, reason 15, Interface: wlan-1-1
2026-08-07 00:46:03 - 80:48:2c:ab:35:57 blocked by key handshake fail on Channel: 1, SSID: redacted_SSID, 2.4GHz, Security: WPA2_PSK, Signal: -62dBm, Download/Upload: 113Bytes/135Bytes, reason 15, Interface: wlan-1-1
2026-08-07 00:46:03 - 80:48:2c:ab:35:57 deauthenticated by key handshake fail
2026-08-07 00:45:55 - 80:48:2c:ab:35:57 disconnected by STA reconnect on Channel: 1, SSID: redacted_SSID, 2.4GHz, Security: WPA2_PSK, Signal: -60dBm, Download/Upload: 0Bytes/0Bytes, reason 8, Interface: wlan-1-1
2026-08-07 00:45:05 - 80:48:2c:ab:35:57 blocked by key handshake fail on Channel: 1, SSID: redacted_SSID, 2.4GHz, Security: WPA2_PSK, Signal: -59dBm, Download/Upload: 113Bytes/135Bytes, reason 15, Interface: wlan-1-1
2026-08-07 00:45:05 - 80:48:2c:ab:35:57 deauthenticated by key handshake fail
2026-08-07 00:41:34 - 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: redacted_SSID, 2.4GHz, Signal: -61dBm, Download/Upload: 0Bytes/0Bytes, reason 2, Interface: wlan-1-1

Because this issue usually seems to involve WPA2 authentication, I’m starting to suspect that may be where the compatibility issue lies. I’m going to experiment with different key lengths and characters to see if maybe something in the password and/or SSID is the issue. I won’t post my SSID or password for obvious reasons, but there’s a single underscore in my SSID and a single period in my key. Neither of these should cause any issues, but absent any fixes from Wyze, I’m not sure what else to try.

I’m also disabling DCS and locking my AP to channel 1. That’s far from ideal but if it behaves locked, at least that’s another clue.

Has anyone found a fix for this yet?

2

I just changed out my Mesh Wifi to Ubiquiti S7 Pro’s. After the changeover, I cannot add the Doorbell chime back. No other device (Wyze or otherwise) had an issue with the new AP’s.

I want to blame the new AP’s but I doubt it. Seems like something else would have had an issue other than this chime.

Luckily, you can have the doorbell use camera’s as chimes so I’m covered but would still like to know the root issue.

I need to get into the AP access logs to see if mine match OP’s.

3

I want to blame the new AP’s but I doubt it.

Given the years of unresolved complaints on this exact issue, I’m convinced that the issue is localized to the doorbell’s wifi implementation. All of my AP logs tell the exact same story:

  1. Doorbell is working fine
  2. AP drops the doorbell due to WPA2 authentication failure
  3. Doorbell makes multiple attempts to reconnect. AP repeatedly rejects the connection because either the authentication is wrong or the doorbell reaches the idle timeout.
  4. Doorbell spends several minutes to several days struggling to reconnect
  5. Given infinite time, doorbell ultimately reconnects (though I usually just do a 5-minute power cycle after a few hours)

My IDS is disabled for testing and my firewall and DHCP server are logging no issues. The issue is between the AP and the doorbell. And again, for anyone else reading this, I am observing this behavior across three different brands of APs, so the AP is unlikely to be the cause.

The repeated deauth / key failure paints a picture of the doorbell failing to send the full key, or sending a corrupt key. I have devices all over the house using this IoT network so I set up a new SSID with a unique alpha-only name, set up a shorter alphanumeric-only key (no symbols), and moved the doorbell (and only the doorbell) over to that SSID.

I’ll report back if this works. In the meantime, if anyone else has logs, please post them.

4

I don’t have great logs right yet. I need to dig deeper in the Ubiquiti software. I only see the Chime joining and disconnecting. Nothing else more descriptive unfortunately.

image
image1416×154 30.2 KB

5

Well, I tried the simpler SSID (“wyzetest”) and a borderline insecure simple password (two words + four digits), and the camera failed again.

My AP timeout was set to 300 seconds, and I noticed the cam is failing every 4:55 - 4:59 minutes. I’ve temporarily set the timeout to 30000 seconds (about 500 minutes). That’s an absurd setting but if it behaves, that’s another clue.

6

While I haven’t personally experienced this problem with my Video Doorbell v2, I appreciate the effort and detail presented here, and I dropped a link to this topic in Wyze Video Doorbell v2 Issue Collection since that’s a topic Wyze created at one time seeking input on issues with that product. I don’t know if they’re actively tracking that one, but this seems like information they should know.

Thank you for taking the time to share this! :+1:

7

Next day report: None of the changes I made to my infrastructure addressed the issue, unfortunately. So far I’ve tried all of the following without success:

  • Switched AP to 802.11n-only mode. This seemed to slightly reduce the frequency of errors, but they continue.
  • Switched AP to 802.11b/g-only mode. This had no meaningful difference over n-only.
  • Verified 802.11k/v is disabled. No impact as expected, but this simplifies things.
  • Verified DCS is disabled and AP is locked to channel 1. Possible a slight improvement in event frequency, but no meaningful help.
  • QoS locked to WMM. No impact.
  • Hard power cycle: cut power to doorbell for a full five minutes, rebooted AP, powered up doorbell after AP returned to service. No impact.

To reiterate from my earlier post, I have verified voltage at the doorbell is at a steady 18.4V - 19.0V range. The transformer is 40VA. Connections to the chime controller are solid. There are no environmental factors (time of day, weather, usage, etc) that correlate with the doorbell dropping off the network. I see this behavior with three different access points (TP-Link, Ubiquiti, and Zyxel). No other devices on this network are having issues, including a large number of v4 cameras.

One thing I’ve noticed is that Wyze only sends a “your device is offline” notification once a device is off the network for a fixed period of time, like 10 minutes (just a guess; possibly shorter). The doorbell is disconnecting for a much shorter period, so it doesn’t always trigger the Wyze alert. When this happens, it can’t stream and it won’t record events, and the app displays the “your camera is offline” error. In these cases it fixes itself within a few minutes to a few hours. I suspect it always fixes itself within a few minutes, and outages that appear to be several hours long are just the camera in a re-failed state every time I check.

Based on this continued behavior from two different Wyze Doorbell v2 units purchased new from an authorized retailer roughly 18 months apart, the intermittent and semi-invisible nature of the failure (you’re not going to notice unless you’re watching at the exact moment it drops, or you start missing recordings), and given the widespread nature of this issue, I suspect that the Wyze Doorbell v2 has flaky WiFi hardware. Most consumers won’t have access to their wireless AP logs, so this is exactly the kind of behavior that can go undetected by many. Unfortunately, it explains why both of my doorbells miss a lot of events – because they repeatedly silently fail.

I’m about out of options here. As one last ditch effort I’m going to try unboxing my emergency backup AP (another TP-Link, brand new), running a cable to the other side of the wall, and setting the thing up three feet from the doorbell. If that fails, my next step will be to break out Wireshark and see if I can see exactly where the handshake is failing. I suspect the doorbell is either sending corrupted data or failing to respond.

The logs continue to show rapid, repeated failures even after all my troubleshooting steps:

2026-08-08 13:11:33
Station: 80:48:2c:ab:35:57 connected on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA2_PSK, Signal: -64dBm, Interface: wlan-1-2

2026-08-08 13:10:48
Station: 80:48:2c:ab:35:57 blocked by key handshake fail on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA2_PSK, Signal: -65dBm, Download/Upload: 113Bytes/135Bytes, reason 15, Interface: wlan-1-2
 
2026-08-08 13:10:48
Station: 80:48:2c:ab:35:57 deauthenticated by key handshake fail
 
2026-08-08 13:10:31
Station: 80:48:2c:ab:35:57 blocked by key handshake fail on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA2_PSK, Signal: -65dBm, Download/Upload: 113Bytes/270Bytes, reason 15, Interface: wlan-1-2
 
2026-08-08 13:10:31
Station: 80:48:2c:ab:35:57 deauthenticated by key handshake fail
 
2026-08-08 13:10:13
Station: 80:48:2c:ab:35:57 disconnected by STA timeout on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA2_PSK, Signal: -65dBm, Download/Upload: 569KB/8.26MB, reason 34, Interface: wlan-1-2

2026-08-08 13:05:07
Station: 80:48:2c:ab:35:57 connected on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA2_PSK, Signal: -65dBm, Interface: wlan-1-2
 
2026-08-08 13:04:38
Station: 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: wyzetest, 2.4GHz, Signal: -64dBm, Download/Upload: 670KB/11.34MB, reason 2, Interface: wlan-1-2
 
2026-08-08 13:03:49
Station: 80:48:2c:ab:35:57 disconnected by STA timeout on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA2_PSK, Signal: -64dBm, Download/Upload: 670KB/11.34MB, reason 34, Interface: wlan-1-2

2026-08-08 13:00:28
Station: 80:48:2c:ab:35:57 connected on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA2_PSK, Signal: -65dBm, Interface: wlan-1-2
 
2026-08-08 12:59:24
Station: 80:48:2c:ab:35:57 left on Channel: 1, SSID: wyzetest, 2.4GHz, Signal: -63dBm, Download/Upload: 290Bytes/248Bytes, reason 3, Interface: wlan-1-2
 
2026-08-08 12:59:23
Station: 80:48:2c:ab:35:57 connected on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA2_PSK, Signal: -63dBm, Interface: wlan-1-2
 
2026-08-08 12:59:11
Station: 80:48:2c:ab:35:57 blocked by key handshake fail on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA2_PSK, Signal: -64dBm, Download/Upload: 113Bytes/405Bytes, reason 15, Interface: wlan-1-2
 
2026-08-08 12:59:11
Station: 80:48:2c:ab:35:57 deauthenticated by key handshake fail
 
2026-08-08 12:57:59
Station: 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: wyzetest, 2.4GHz, Signal: 0dBm, Download/Upload: 0Bytes/0Bytes, reason 2, Interface: wlan-1-2
 
2026-08-08 12:57:05
Station: 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: wyzetest, 2.4GHz, Signal: 0dBm, Download/Upload: 0Bytes/0Bytes, reason 2, Interface: wlan-1-2
 
2026-08-08 12:52:52
Station: 80:48:2c:ab:35:57 left on Channel: 1, SSID: wyzetest, 2.4GHz, Signal: -63dBm, Download/Upload: 0Bytes/0Bytes, reason 3, Interface: wlan-1-2
 
2026-08-08 12:51:58
Station: 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: wyzetest, 2.4GHz, Signal: -65dBm, Download/Upload: 0Bytes/0Bytes, reason 2, Interface: wlan-1-2
 
2026-08-08 12:49:03
Station: 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: wyzetest, 2.4GHz, Signal: -65dBm, Download/Upload: 0Bytes/0Bytes, reason 2, Interface: wlan-1-2
 
2026-08-08 12:48:30
Station: 80:48:2c:ab:35:57 left on Channel: 1, SSID: wyzetest, 2.4GHz, Signal: -65dBm, Download/Upload: 0Bytes/0Bytes, reason 3, Interface: wlan-1-2
 
2026-08-08 12:47:40
Station: 80:48:2c:ab:35:57 disconnected by STA timeout on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA3_PSK, Signal: -65dBm, Download/Upload: 376Bytes/1KB, reason 34, Interface: wlan-1-2
 
2026-08-08 12:46:54
Station: 80:48:2c:ab:35:57 connected on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA3_PSK, Signal: -64dBm, Interface: wlan-1-2
 
2026-08-08 12:46:52
Station: 80:48:2c:ab:35:57 blocked by key handshake fail on Channel: 1, SSID: wyzetest, 2.4GHz, Security: WPA3_PSK, Signal: -66dBm, Download/Upload: 135Bytes/423Bytes, reason 15, Interface: wlan-1-2
 
2026-08-08 12:46:52
Station: 80:48:2c:ab:35:57 deauthenticated by key handshake fail
 
2026-08-08 12:46:22
Station: 80:48:2c:ab:35:57 disconnected by Auth Timeout on Channel: 1, SSID: wyzetest, 2.4GHz, Signal: -64dBm, Download/Upload: 60KB/113KB, reason 2, Interface: wlan-1-2
8

I can confirm this issue. My VDB v2 keeps showing as offline. When the button gets pressed by my neighbor, the mechanical doorbell will still ring, but everything else is inconsistent. Sometimes my other automations will run delayed but sometimes not at all. One time my automations (flashing color bulbs, and Alexa announcements) happened MINUTES late.

I can’t stream it or anything though. The device says it’s offline, and then will randomly come back online then randomly go offline again for some time. It’s inconsistent. It self-heals and then repeats.

I posted this issue for the Fix-it-Friday event, but I probably posted too late. Hopefully it gets addressed anyway.