If you want reliable Wifi at home, get yourself Ubiquity access points and throw away TP-Link. The issue is not the protocol. After many years of unplugging and plugging back in my TP-link router I know that they are cursed.
I have "enterprise" TP-Link equipment for my house which I bought 3 years ago now and am very happy with it, in particular I'm using:
- 4x EAP245 Access Points
- 1x SG3428 Switch (the APs came with PoE injectors and I wanted a fan-less switch, hence why the switch is not PoE enabled)
I rent out a room on my property and have my tenant on a separate VLAN to the main house. I also have my IoT devices on a separate VLAN.
I use a generic PC with pfSense as my "router".
My only complaint is that their Omada Controller software doesn't want to run as a Windows Service (I'm not interested in trying to manage a Linux box). Fortunately, it's not required at all, but is useful for centralized configuration management and facilitation of handover of WiFi clients between APs.
Before I moved into my current large-ish place, I used "cheap" ISP supplied TP-Link routers with WiFi, and aside from limited speed capabilities, were 100% reliable for me, in particular I used the following two models:
- TL-WR840N
- Archer C20.
I also use a few cheap (but again fully reliable) 5 port and 8 port TP-Link 1GB/s switches, for example under my desk in my office to allow both my laptop and desktop to share the single CAT6 cable to the room.
Before buying the "enterprise" TP-Link equipment I considered Ubiquiti, but the TP-Link stuff was less expensive, I liked the controller being optional and considering all my past TP-Link equipment's reliability was a non-issue, I was happy "to take a risk".
Haven't had any wifi problems since. To the point I don't remember what wifi standard my home is on :)
Too bad they may or may not have given up on the cloud connectivity requirement. I've been told (even on here) they have, but I've also been told that you can disable it after setup instead of setting up without any stinking cloud.
Say, did Ubiquity stuff work during the AWS outage?
It doesn't really matter which part in the chain requires the stinking cloud as long as they sneak it in somewhere.
Speaking of which, I just bought a Razer mouse again because I've read they gave up on the login requirement for configuring your blinkenlights. But they didn't. They invented a 'guest login' instead.
Burned twice so far.
AFAICT, the controller is needed for fast roaming of clients.
So can I just ignore that option or do they make me register to the stinking cloud just in case?
IIRC the controller is needed to configure your AP anyway when you first set it up.
Indeed. You need the controller running first before you can configure AP, Switches, and gateways.
None of my ubiquity stuff uses their cloud stuff at all.
Ubiquity stuff was giving me constant buffer bloat issues and it was a pain to do basic configuration for. Just too many options.
TP-LInk generally works just fine as long as the WiFi channel is clear.
For wifi I have been using ASUS's AI Mesh. Not that impressed tbh so looking to change to something else in the next upgrade cycle.
Although I have previously encountered significant issues with WiFi, I now do not see a need to replace these devices despite the availability of WiFi 7.
I haven’t thought about it since I set it up, three years ago. 100% reliability, seamless handoff between APs.