Wyze would sell more V3 cameras if they didn't need to have power recycled periodically

Yea, I think we all find what works for us. Your approach of putting the Wyze products on its own router is a positive one and something I am planning on doing in the near future.

1 Like

I believe we may have ABASHED carver. :astonished: Let me withdraw to my dressing room like Laurence Olivier after a gobsmack performance and review… how did we do it?? :laughing:

@ssummerlin say something nice to him. He won’t expect that. :grin:

Oh, I see what he’s doing… withdrawn to a text editor or a DM-to-himself compose window :slight_smile:

Vamp until ready then…

James Michener in one of his enormous novels had a seafaring character relay: Never let a fallen adversary up from the deck. Finish the job.

Have you seen a picture of James Michener?? That guy can write. :slight_smile:

Eric Schmidt may agree to be my transhuman daddy. If so, will he manipulate me humanely? He says he will.

And I trust him. With my life. :face_with_diagonal_mouth:

  • Carver is abashed.
  • Carver is licking his wounds.
  • Carver is DM’ing himself.
  • Carver is the least of our problems. Keep your eye on Eric Schmidt!!

0 voters

3 Likes

Huh. I have 9 cams (one V3) on my ordinary at&t router. I routinely restart them after checking to make sure the microSD card is wyrking.

Infrequently, I’ll need to “kick the plug” on a cam… it seems like the age of the camera is correlated to the issue. The V1 in my super hot attic has been turned off until cooler temps cuz that one was needing to be unplugged/replugged.

I have never associated any problem relating to my router… and I routinely look at 3 cams in a group.

2 Likes

This is the system I am running. Not top of the line but far better than low class.

One of the reasons I went with this system is it being tri-band and that having a dedicated backhaul channel I thought would be very good for our cameras having the system and the satellites talk to themselves on their own dedicated channel versus taking up yet another channel. The other reason I went with this system was it’s capacity. Although I had a Wi-Fi 6 router before I didn’t realize that even for the money I spent it was limited at around 30 devices. I was rather shocked by that. This one States it’s good up to about $150 devices which if we give Wyze 24 to 48 hours I’ll probably be over that after they release more things LOL. (strictly a joke I know of no releases coming out in the next 24 to 48 hours)

Since I’ve had this system I have not had any of the issues I previously did such as my plugs disconnecting, I have Wi-Fi all the way down the block. This thing reaches out to a huge distance I was rather shocked. The one thing I wish it did have was certain settings that seem common on a lot of lower routers such as the ability to set a schedule to Auto restart it. Luckily I rarely have to restart it. It would just be a nice option to have. A router is definitely worth the money spent if you spend good money on it though.

For anyone trying to stay on top of the game though I would highly recommend researching the difference between Wi-Fi 6 and Wi-Fi 6E as the Wi-Fi 6E systems are being pushed and becoming more and more common even though devices to use them that have the 6 megahertz radio included are not very common yet. But considering all the things that will change once MATTER is included in iot devices I have no doubt there will be an insane amount of recommendations to update and upgrade routers on this forum considering all the device connections possible then.

7 Likes

I thought I’d write a more comprehensive answer I can refer to later since I see so many users believe their connectivity issues are solely Wyze’s fault. Some will cite their signal strength or Bandwidth as evidence it’s definitely Wyze’s fault, though the issue is way more complicated than just signal strength or even bandwidth alone.

I used to experience a lot of these issues (devices losing connection and having to reboot often, etc) in the past myself. It was VERY frustrating having to reboot my Wyze Cams, Routers, and other devices so often. So I can totally relate. I tried so many things and did so much research and testing. I learned a lot about this. I finally got my connectivity resolved and I rarely have to reboot anything anymore even though I now have over 200 Wyze devices on my network including more than 2 dozen cameras using Cam Plus and uploading video constantly, etc. So after my experience I am now pretty confident that most of the time the issue is NOT Wyze since it is possible to have everything working reliably with few to no problems. My connectivity issues and my issues of needing to reboot basically all disappeared after I worked through some of the following.

ISP -

  • I had Comcast/Xfinity and it was absolutely horrid. I swear half my problems were related to Comcast. When I switched ISP’s, I had a huge improvement. (At my previous house I had no choice but Comcast, then I moved and had to have Comcast here too. Then my city installed fiber and let us pick nearly any ISP we wanted. I switched and it was exponentially better.

DNS -

  • When I switched from my default DNS (Comcast/Xfinity) to either openDNS or Google I saw some stability improvement

Cable/Daisy-chaining issues -

  • Because cable shares bandwidth with the whole neighborhood (or city), devices often have issues during peak hours. We may have a good bandwidth in theory, but when the entire neighborhood is competing for limited resources, we all get screwed. You can sometimes even run a speed test and it might look okay since the cable company might temporarily prioritize you over others, especially to look like your connection is still okay. Our router then has to prioritize what it gives priority and IoT devices often don’t have priority. Rebooting my router or Wyze devices helped to reset things and re-establish the needed connection from scratch and it would then usually work for a while again. But if a cable company has a limit of X bandwidth for a neighborhood and the combined neighborhood is using more than that, they also have to decide what they’re going to prioritize… And net neutrality is currently in danger for telecom companies like this, so we can’t expect they’ll give Wyze equal priority as some company paying them for priority. Dropped packets, slowed packets, show connection etc… I’d look at the provider first.
  • There might not be much you can do about this if your cable company has a monopoly and your options are limited.

2.4ghz congestion/interference issues.

  • The more devices competing for the same channel and band, can cause a lot of dropped packets and basically jamming experiences. There are apps out there that will analyze all the congestion near you and tell you what would be the best channel to broadcast your 2.4ghz bandwidth SSID on. Some routers try to do this automatically, but many just default to a certain channel on their own…the problem is that the channels they usually default to are the same ones others default to, so they are also the ones with the most congestion and problems because everyone else does the same thing. Many people don’t even know you can change the channel, but sometimes it makes a big difference to switch to a non-overlapping channel. Some routers even offer more channels than others. This is one of the best solutions to the issue of average speed per device limitations (discussed more below in the Router performance limits).
  • 20 MHz setting vs 40 MHz setting for 2.4G Radio settings. Part of your problem could be based on whether you are using 20MHz or 40 MHz. 40 MHz has a higher throughput than 20 MHz because of what’s called “channel bonding.” The problem with channel bonding is that it reduces the number of non-overlapping channels, which increases the chances you are getting interference. For some people it’s better to use 40 MHz if you have a ton of use going on and it’s mostly just you near yourself. For others in crowded areas or apartments where lots of other people are also using lots of WiFi, it might be better to use 20 MHz so that you can more easily let your router switch to a channel that isn’t so congested. It’s a tough call to tell you which is best for you, but this could be a big problem for some people.

5GHz SSID and 2.4GHz SSID with Matching vs Diff names

  • Related to interference: For whatever reason, some routers (but not all) have issues with being able to properly route some devices when the 2.4GHz and 5GHz band SSID (network name) are the same name. Sometimes when a Wyze device (or those from other companies) can’t connect or continually disconnect or have connectivity issues, it turns out that there is a conflict related to the different bands having the same SSID name. When a person then creates a separate SSID (like a guest network) where the 2.4GHz band has it’s own unique name, suddenly the devices are able to connect and maintain a good connection. If you have consistent connectivity issues or can’t connect a new device to your router for some reason, this should be one of the first things you try to see if it makes a difference. It’s irrelevant whether “other devices” work fine with it, even other devices of the same model from the same company, or even whether this particular unit has worked fine with it in the past. For whatever reason, sometimes this problem creeps up and only resolves by making a unique name for a 2.4GHz band. This can mostly be considered a router issue because a person who has this issue can swap out for a different higher quality router and often not have this issue anymore. Thus, if the router’s connection and routing is programmed well, it can often avoid this issue. Though it is also true that device manufacturers can often mitigate this issue with using better chips and improved programming as well on their end.

Memory leak issues -

  • Many times when people have to reboot their routers (or their MODEM), or their devices, it is due to the router (or modem) or the device having a memory leak issue that just keeps building up and causing more issues over time until it gets rebooted and cleared. These are actually fairly common, especially with routers, modems, and computers. Rebooting either device fixes the problem [temporarily] and re-establishes the connection. This is why a lot of people schedule to reboot their router/modem every night in the middle of the night. It force clears the memory leak issues so everything is fresh and works cleanly the next day. Often, if your Wyze devices need to be rebooted every day, my first instinct is that the router/modem has a memory leak issue. This can often be mitigated by scheduling a smart plug to cycle every night while you sleep.

Router performance limits -

  • Routers have RAM limits and different processors that can handle different amounts of strain, power limitations, among other constraints. As others mentioned, different routers can handle a different number of devices and type of use. Most have a recommended limitation. Often people have a cheap router that can’t handle many devices, and have a bunch of IoT devices have problems because of this.
  • There’s also an issue about Maximum speed (which few to no devices will ever hit) vs the average speed per device. This can be an issue, particularly on lower end routers.
  • Related to this are router incompatibility issues. I won’t get into this too much, but some routers have struggles with IoT devices or their chips in some cases. For example, openWRT based routers have a known issue with certain IoT chips. They work totally fine with others, but they have issues with certain chips. Apparently, it is related to the WMM feature in some way since since people can get them to work better by disabling the WMM in the firmware. :man_shrugging: The Wyze V1 bulb happens to use one of the chips that openWRT has issues with sometimes. I believe the V1 Plug also does. It’s my understanding Wyze uses a different chip in later models, but the point is that sometimes a router, or more accurately the router firmware has a compatibility flaw in it that other routers have no problem with.
  • My suggestion?
    • Look for a router with WiFi 6 capabilities. I’ve read a ton of articles where people said that switching to a WiFi 6 router made a huge difference in their IoT stability. Some of it doesn’t make a lot of logical sense considering WiFi 6 shouldn’t actually affect most legacy IoT devices using 2.4ghz, but for some reason something about it seems to make an improvement with allowing lots of devices to connect simultaneously instead of waiting in line.
    • Good Mesh Routers are helpful. They reduce the processing strain off the primary node as well as giving increased signal strength to other areas. My Primary node signal is STRONG enough to get through the entire house, but having a second node that other devices can connect to can make a huge difference. You need to learn how to change when a device connects to which Mesh Node. On my Mesh system, almost every device will just connect to the main node by default if I leave everything at the default settings. So I changed the settings to force more of them to connect to the second node if they are within a certain RSSI (signal strength) of the second node. I just moved this number up or down until I felt there were enough devices using the second node instead of the primary. Mesh routers can also usually communicate with devices on one channel while communicating with the primary Mesh node on a separate dedicated channel (wired or wireless backhaul) so there is no conflict…extenders cannot do this, so they often cause interference problems and have to split what they’re trying to do. Extenders do not typically work anywhere near as well as a Mesh network that can use dedicated backhauls, but in many cases they can help with issues related to overload or signal strength if those are the primary issues at hand which need resolving.
    • When I was looking for a new router, @spamoni4 gave me some recommendations to look into, and ultimately he and I both concluded the ASUS ZenWiFi AX6600 was the best of all the options we were considering at the time. I have 2 nodes handling hundreds of Wyze devices, including more than a dozen with Cam Plus frequently uploading events, several of them nearly constantly. I have CLOSE to every device Wyze has made and I rarely to never have to reboot a device, with a few exceptions for things like all the beta testing I do on some of the devices, or testing things out to help forum members or trying to replicate issues they are experiencing. But compared to the aggravating connection and rebooting issues I used to have…those are far in the past for me despite having increasingly added more and more devices to my network. I am pretty confident that myself, @spamoni4 and @R.Good are EASILY in the top 1% of users with the most Wyze devices active at a time (partially because 2 years ago Wyze sent me an email saying I was in the top 2%, and my collection has grown exponentially since then and the 3 of us have a friendly contest about who has the Wyze-iest house). :slight_smile: And the thing is that despite our excessive addiction to a ridiculous number of Wyze devices, we rarely have the connection problems others report…so that’s worth considering what the difference is…The ASUS mesh router has treated me really well. It’s a big pricey, but it’s amazingly effective at handling tons of IoT devices in my experience so far. I am confident that this made one of the biggest differences because I made this change a month or 2 before I upgraded my bandwidth, and there was a marked improvement just from the router alone. I should mention that I went through trying at least 5 different routers in a 2.5 year period…7 if you count my attempts at replacing the stock firmware with Gargoyle Router firmware (an openWRT based firmware). I also tried using some WiFi extenders, and I tried changing a couple of routers into repeaters. Those both extenders and repeaters seemed to cause more congestion and conflict for me, sometimes bringing new issues (whereas Mesh nodes can often connect on either a wired or separate wireless backhaul channel without causing extra issues). All those solutions (extenders, etc) still had issues for me. It was really aggravating. Some of those things work well for others (ie: signal strength or mild load issues), but for me, switching to this ASUS Mesh router was the thing that primarily saved my sanity (Thank you @spamoni4 for recommending I check out reviews and videos and such on it…you saved my sanity more than I can say). I have had few issues with this router compared to all the others I tried.

Bandwidth Limitations [especially upload limits]

  • This was kind of addressed with the cable/Daisy-chaining, but we can point out the bandwidth limits in general can make a big difference, especially depending on how often they are using that bandwidth. If you have a low upload rate, but you’re trying to use Cam Plus on multiple cameras, you’re going to have problems, especially if you are also using the internet for other things that require upload access. I can’t say what the limit is or what you need since it will all depend on your individual use…what other devices you have, how much you use different services and when and so many things. I don’t know what’s enough for any particular person. I can only say the following:
  • Once I upgraded to 1gbps up and down, I’ve never had bandwidth problems even with my excessive amount of IoT and constant use of tons of cams and devices. I’m not saying whether a particular individual needs more or not, we can only guess…but bandwidth does play a HUGE part, especially Upload bandwidth, which is usually exponentially smaller for most people than their download bandwidth.

Router FEATURES causing issues

  • It has been demonstrated that things like QoS (particularly adaptive QoS) can cause IoT devices to have connection issues since it determines to give priority for other things like streaming or gaming over your IoT devices. Lots of people have had major issues with this, while others don’t. If you are having issues, consider disabling it and see if it helps at all. Or consider telling your QoS to give the Wyze devices priority (I know people who tried this it didn’t help as much as turning it off did, but you can try it)
  • WMM/WiFi Multimedia sometimes causes issues with some devices as I mentioned earlier. This option forces the router give priority to multimedia stuff over other IoT devices, and has been shown to cease connectivity for some chips in particular. If you are having problems and this is an option on your router, try disabling it. Some routers (some OpenWRT based routers for example) may force WMM to be on, and the only way to turn it off is through manually changing the firmware by logging into it using something like WinSCP or Putty. WAY too complex for most people…but I had to do this with one of my routers to get IoT devices to stop having problems. Usually just easier to buy a new router!
  • Auto-blocking (or manual blocking) features - Some routers have different blocking features, whether using an AI or various other things that may overzealously and inadvertently cause some blocking that you don’t want it to. Or some people might do something like try to block ALL Google IP addresses, only to find out that many IoT devices send a ping to Google IP addresses as a check to see if they are actually connected to the internet, so blocking Google (or whatever other IP the person blocked) makes some of their IoT devices think they are offline, when they aren’t actually offline. Some of them will even say they are offline in one place while showing online elsewhere or working with some stuff and not others. Sometimes this is caused from auto-blocking features sometimes blocking some things but not everything. PLEASE NOTE: I AM NOT SUGGESTING TURNING OFF YOUR FIREWALLS OR PROTECTION!!! I am just indicating sometimes Overzealous router protection features can be part of the problem for some people.

Wyze VP seemed to acknowledge they are working on some things to try to help improve the connection and stability issues as much as they can. When asked about it, he responded the following:

There are lots of other good responses in the AMA interview that could be related to this, including trying to make more things be locally based (which would reduce a TON of the strain), so I’d recommend reading the entire thing since Wyze might be coming out with some good solutions to connectivity frustrations in the near future.

I’m sure there are several others I am not thinking of off the top of my head, but I think I covered most of the major issues I personally experienced in the past. If I think of more I will try to add them in later.

The point is this. I too once had to reboot my devices all the time and I too once had connection issues, so I do totally empathize with how frustrating is. I also blamed Wyze initially. I totally get it. I really do. I’ve been there. But I found reliable people who I trusted who told me they never had any of these problems I was having, so they were confident it wasn’t Wyze that was my problem, so I spent all the time learning and testing and trying so many things with the above issues trying to figure out what the real issue was. Right now, I hardly ever have any of the issues I used to have after changing so many of the above things. Here’s what I have in rough order of what made a difference to me:

  • ASUS ZenWiFi AX6600 - 2 nodes with optimized load distribution (rarely to never needs a reboot, though I do it sometimes for testing purposes)
  • Bandwidth - 1gbps up and down Fiber (not a daisy chained cable connection anymore!)
  • ISP and DNS that is not Xfinity/Cable!
  • 2.4ghz Channel set to a different channel than the popular defaults near my house
  • QoS turned off

All I can really say is that having the above things has made it so I can have dozens of cams active with Cam Plus, 200+ total Wyze devices, plus multiple computers, TV’s, a Teenager, Toddler, and many other variables using our internet constantly now, and I don’t have the problems I used to think were Wyze’s fault. Therefore I’ve pretty well concluded that in my experience, the majority of the connection issues are resolved somehow else.

Having said that, it is possible there are things Wyze could do to make things more efficient or be prioritized higher by the routers or whatever by default since it seems like sometimes other devices are able to pull this off in some cases (though then we might have people complaining about their TV stream being affected :man_shrugging: ). The Wyze VP also acknowledged that while they are actually doing objectively better with connectivity than competitors, there are still things they can do to make improvements and they are going to do more. I don’t know enough about all that to be confident in elaborating on what Wyze could or should do differently, if anything. I can only say that it is definitely possible to resolve Wyze connection problems in other ways that seem to suggest a lot more of the responsibility lies in things Wyze has little control over and aren’t their fault, but with which we can often improve ourselves.

I hope the above is helpful to someone who is at their wits end like I once was. I spent countless hours trying to figure out what helps and maybe some of the above will spark some ideas to bring someone else some peace.

Keep in mind there are plenty of exceptions to the above…AWS issues, occasional Beta firmware/app issues, etc…but I am talking about ongoing long lasting pattern of connectivity issues being the problem, then the above is what helped me basically resolve all that.


UPDATE/EDIT: Also make sure you are using the correct power plug and cords for the devices having problems. There have also been cases where someone is using a different plug/adapter OR a really long 3rd party cord or something and thus the device in question is not the correct power (Volts, Amps, etc) that it needs to be reliable. Some Wyze devices have different power requirements than others. For example, using a V2/V3 plug for a V3Pro could cause the V3Pro to be less reliable, or using really long cables can degrade the power coming into the camera.

9 Likes

Yes, I started writing my reply in church. :angel: (Don’t tell Mrs. Carverofchoice),finished at home on my laptop though. This is part of the reason it took so long. It wasn’t non-stop typing for hours…I took some breaks. :wink:

Hey! Don’t make fun of my hyper-fixation (dis)ability/ADHD-super-power…sometimes I decide to go overboard in a reply for no good reason. :slight_smile:

I’ll take that as an apology…accepted! :grin:

4 Likes

You don’t disappoint. :slight_smile:

A lot of good stuff here

5 Likes

I’m going to keep banging my head against the wall until a decent sub $100 home router emerges. Such a thing used to exist.

All the current “good” ones seem to be hundreds of dollars.

Thanks for all the advice folks. There is good info here.

5 Likes

Picture? From behind is fine… :wink:

I expect there will be some huge improvements with upcoming Matter release. I was reading an article recently about the Thread 1.3.0 update which is supposed to be Matter compliant and allow any router with Thread 1.3 to be able to use any other Thread/Matter router as a mesh node. This kind of thing could change router options drastically. You wouldn’t even be stuck with a single brand of router. You could add any other “Border Router” as they call them to the network to work as another mesh node. I know Nest, Apple, Echo/Eero and Nanoleaf Shapes devices are all setup to support this as soon as they update to Thread 1.3. I imagine a bunch of others will too just so they can be Matter Compliant and have all that benefit. I may have some misunderstandings about the full capabilities of Thread 1.3, but the articles I read made it sound AWESOME how routers are going to change for the better in the near future. We’ll have to see how the implementation actually works. If I was thinking of getting a new router right now, I’d almost wait to see what happens when the first Matter devices start getting released the end of this year and check reviews online about how the implementation is working on those routers that claim they’ll be compliant as Matter/Thread border routers. Check out some of the articles about it online, I found them interesting and they made me excited about how cool things could be improved really soon. At least there is a lot of potential. It sounds like it will help a lot of IoT issues.

2 Likes

Ah, hell, you wrote the book anyway. :cloud_with_lightning: :kissing_cat:

Here’s where I would say it can be laid on Wyze (I know, I know, they compare at least to their industry peers, and maybe even favorably.)

Sales schpiels manage expectations UP.

Reality often slaps a customer DOWN.

Hello, forum, my old friend… :notes:

A good example would be the minimum quality SD card recommended and supported. Sure, kids, it’s a bargain brand, you can use that. Yet, to have a reasonably good experience, you should pony up and $nag a premium card. :face_with_raised_eyebrow:

Same with a router.

Improving from 63 to 67% might be described charitably as driving a metric toward 100%.

Why dangle 100% over users’ nose holes? They smell it!!   :dog: :dog2:


 
Nice reply! Obsess-on! :grin:

1 Like

Okay carver old pal, you finally got me to read a couple of Matter articles… Unfortunately this leaves me very disappointed. So far as I can see, there’s good reason cameras are not currently part of the plan - the technology is a “low-power, low-latency wireless protocol” and it’s aimed squarely at home automation, NOT communications or media consumption. You know, lights and switches and thermostats. Not cameras.

When a router is “border ready” for Threads and Matter, all that seems to mean is it will be able to act as a bridge to Matter home automation nodes. The Matter subnetwork remains separate and, so far as I’ve seen, this does nothing for bridging high speed WiFi networking and services across disparate routers.

So just another iteration of ZigBee or ZWave. This isn’t even as interesting as the original WDS bridging protocol, which at least WAS for WiFi and WAS vendor independent.

If there’s more to it please let me know. :slight_smile:

2 Likes

How many years would you say one could reasonably expect to stay with a router once you have it operating ‘invisibly’ (router? what router? oh yeah, that)?

Some folks (me) despise the adapt-adapt-adapt-a-dance. :slight_smile:

Also, I despise this coy b.s.:

If you have a router coming out, say so, not everyone enjoys fantasizing on your every future product.

All your fault, @bam, do better! :wink:

1 Like

I have not spent enough time on it to be confident.

Cameras are going to be part of the plan as far as I understand it. They’re just not part of the first iteration. Steve M just told us it should be coming:

1 Like

image

3 Likes

I want @spamoni4 to say something, he’s entirely too quiet lately. I mean he’s probably all gabby in the Maven Clubhouse, but out here with the proles he’s like :zipper_mouth_face:

Wassup with that? :wink:

He can take everything Carver just ‘said’ and squeeze it down into a tight (but relaxed) paragraph. Why does he deny us his talent??

And if @bryonhu wasn’t testing every damn thing under the sun six ways from sunday he’d probably chime in. But no. He must test. And so, miserly. :wink:

That goes for the rest o’ you libertarian mugs, too…

Speak out! :slight_smile:

1 Like

I responded to your other posts. Was actually on a little Vacation to Cape May NJ. and am now renovating my Garage where my Network will come into. Gutted the Garage and will have my painters come in and make is look good, then I will be putting in cabinets for my tools including a work bench for my Wyze testing and Car repair. Then I will do a new floor.

In the middle of all of this, I have been extremely busy at work with the end of FY coming. Then being part of the Wyze Discord and assisting in there as well.

Been Rather busy. Have you visited the Wyze Discord?

2 Likes

Well then I guess we’ll see. One thing is for sure - Thread has nothing to do with it. Thread uses ZigBee frequencies and handles the low power stuff. Anything video is going to have to go over Matter WiFi according to what I see.

Very little out there about cameras. This was updated this month:

1 Like

Blather withdrawn. Sounds like a good busy, anyway. :+1:

I despise other platforms. But I’ll defend ‘to the death’ others’ right to choose them.

Cheers, brother. May the wind be always at your back, may the sun shine warm upon your face, etc. :slight_smile:

2 Likes

My short response, bolded what I believe to be the biggest issue.

Nothing heavy duty for my IoT network. Do not have to constantly reboot devices since deploying this device in a 3 story large sq ft home plus outdoor living space, and I have Wyze devices in the triple digits.

All the network problems I had (which were pretty minimal, Robot vacuum loosing connection once a week and switches not wanting to connect) went away when I tossed the ISPs rented “junk” router and deployed this modest router

TP-Link WiFi 6 Router AX1800… https://www.amazon.com/dp/B08H8ZLKKK?ref=ppx_pop_mob_ap_share

I do have 2 routers (one modem) in my home though… One is dedicated purely for IoT home automation and security (Wyze) and the other router (less modest) for all else… gaming, streaming, and work.

3 Likes