Wyze Cams and Asus Routers - connectivity issues resolved

FWIW I have an RT-AC68U as well and haven’t had any major issues with my Wyze Cams. I’m running the Asuswrt-Merlin firmware though, which in my experience has been more stable than the stock Asus firmware (and comes with some nice extra features).

I have an Asus RT-N66 router and have been having occasional connection issues over the last several months. After trying many many different (changing microsd cards, changing resolutions, power cycling cameras/router/iPhone, updating firmware,…) the thing that I think made it all finally work was that I noticed one day my asus router seemed hot, so I found an old internal computer desktop fan and mounted it to blow on the router and keep it cool (had to use a 5v wall brick to power it). Now everything is much more stable and connections speeds are much faster and not choppy.

1 Like

ASUS RT-AC68U user here…thank you SO much for this. The connection issues were becoming a constant source of daily frustration.

I had the same problem with the ASUS Black Knight router RT-N66U

I had changed both 2.4 & 5 power settings to “balanced”

Changing it to “Good” or “Performance” fixed the issue for me (using Good)

Airtime Fairness is not an option listed for this older router

1 Like

Here’s a new one with ASUS Routers (maybe others). Don’t turn on secure DNS settings. When I turned this feature on (a must have in my opinion) Wyze Door Gateway, Wyze Color Light, and Amazon Plugs stopped connecting to WiFi. Very frustrating that I can’t use this secure DNS feature with security devices.

2 Likes

This finally solved my problem, I tried everything else. I had to turn off DNS-over-TLS under DNS privacy protocol in order for it to connect.

3 Likes

There is also a feature in Asus software called DNS Privacy Protocol under Advanced -->WAN. I turned this on (off by default) and it caused intermittent issues with all my Wyze devices. They were showing up offline in the app and some would work occasionally and then stop. Finally tracked it down to the DNS Privacy protocol after going nuts downgrading firmware, changing dns servers and going through settings in the Asus software. The intermittency threw me for a loop, but as soon as I turned off the DNS Privacy Protocol, all the devices came back and showed up as ON in the app.

3 Likes

Please remember, all this stuff is “designed” by programers and their brains are not wired the way our brains are :slight_smile: FAirness to a programmer can mean lots of things :rofl: :rofl:

Not an expert, but that to me sounds like a hardware issue. If I were you, I would replace that piece of hardware. We should not be cooling or heating externally our equipment unless we leave in a middle of Sahara or Antarctica.

1 Like

I know you posted this a long time ago… but wow, I was fighting this and finally saw your post and it saved me. anyway thanks! yes I wish this was somewhere, anywhere as an FAQ .

I’m a little embarassed that such an old thread had the answer and I didnt find it until today. I upgraded to a new top of the line Asus router a few years ago and experienced this same problem. I couldn’t figure it out so I ended up turning off the 2.4 Ghz radio on the new router and just running my old asus router as an AP with it’s 2.4 Ghz radio. It was so baffling because nothing else seemed to be affected but then again I try to stay away from 2.4Ghz devices and opt for zigbee/zwave smart home devices.

So glad I finally found this post. What got me looking is the old router is starting to require reboots and needing a replacement and I was worried that the replacement router would have the same issue (and now I know it would have). Fortunately now I’ll be able to use my more current router and not have the need for a second router.

2 Likes

Fantastic. Welcome to the Forum.

Often times old threads can be useful.

Thank you for not archiving this thread Wyze.

I have found with my dozen clients using Wyze devices, that I had to create 2GHz & 5GHz guest networks (non-expiring), in order to have their own dedicated bandwidth (shared with Eufy), and leave the smart connect WiFi network congested with all other network peripherals…

All my clients use RT-AC86u, RT-AC88u, RT-AX82U and RT-AX86u routers after numerous issues over the years with Netgear, D-Link etc…

My thinking, is do at need to ask Merlin and Gnuton to weigh in on this issue??? They will know exactly what and how this code works, plus any discrepancies in language and interpretation…

Surely devices should be able to be ‘excluded’ from Airtime Fairness, just as they are excluded and prioritised with QOS? (rather than turning the feature off) But are there any QoS alternatives for handling INTERNAL traffic? Both LAN and WiFi?

I am not convinced Airtime Fairness should be disabled, and I certainly don’t want to negatively impact my clients by switching this off and “experimenting” with their networks…

Thank you! :smiling_face_with_sunglasses::+1:t3:

I disable airtime fairness as one of the first steps in installing a router or AP. It attempts to let you jam more clients than the band can handle by trying to randomly throttle them. On a network with dozens of clients and basically 0 remaining capacity, it can improve the experience (but it will still be problematic, just less than before). On a network with available capacity, all it does is reduce the available capacity and throttle clients unnecessarily.

I’ve yet to see it perform well in any scenario. Maybe in a stadium situation where you have tens of thousands of people and you just want them to be able to send a tweet or something basic. Other than that, my experience is it adds more problems than it solves. Universal beamforming is another one that should be shut off, and in some cases even MU-MIMO.

1 Like