TP-LinkEAP245 V3 | Omada AC1750 Gigabit Wireless Access Point | Business WiFi Solution w/ Mesh Support, Seamless Roaming & MU-MIMO | PoE Powered | SDN Integrated | Cloud Access & Omada App | White

I bought this wifi TP-Link EAP110 Outdoor V3 Access Point to give my three outdoor Blink cameras a dedicated wifi signal. I had the three Blink cameras for several years without issue - however, I have added many smart home devices which all share the same 2.4 ghz wifi signal, and all three cameras have been getting slower and slower to load the live view - as long as 30 seconds at times - which renders security cameras almost useless. The motion detection video capture was choppy as well. To remedy the problem I thought a separate, dedicated wifi system would help. I installed the TP-Link EAP110 Outdoor V3 Access Point to the router and, after some location adjustments, I had a good signal to all three cameras and the blink sync module. All three cameras now load live view within 3 seconds with smooth motion detection video. The TP-Link EAP110 Outdoor V3 Access Point solved the problem and saved my Blink cameras! Highly recommend!

Ok, I was freaking out at first and was getting rather frustrated because the darn antenna would not power on. I checked other PoE devices and they all worked. I reached out to tech support and when I went back to check on things, the antenna had powered up and came online. I guess I simply wasn't waiting long enough. It was easily 5 minutes on my first attempts, but it was over 7 minutes when it finally worked.So at least on the first boot up, be patient. It will come online if you just leave it be.Router to the included PoE injector (because it has special power needs it can't be driven by a PoE switch). Then the PoE injector to the antenna. It is that simple.We are able to send text and pictures from well over 250 feet away. After that it gets to be hit or miss. But it will grab a connection here and there from almost 400 feet away and any pending WhatsApp or Messenger messages will go at that time.All in all, very happy.

I rate it high. its outside on a pole about 8 ft high. I built a wooden birdhouse looking cover over it to keep rain, snow, wasps etc away from it. Been using it 1 month. this TPlink AP is connected to 200 ft direct burial CAT6 from the switch, which is in the garage. Also have a couple of ethernet surge protectors in the mix , at each end. I get decent line of sight WIFI signal, until i cross a wire fence, then signal goes to nothing. speakeasy.net/speedtest says I get almost the same speed as indoor wifi next to router. Can't complain. I use Tplink switches, and am ordering a tp-link c402 solar outdoor camera. I named the SSID the same as the router's indoor SSID and same password.Update: The TP link C402 outdoor camera has good signal strength at 285 feet from the access point . -59 RSSI.

Really good low cost AP that supports VLANs.Haven't done extensive testing of signal strength or speed, but my IP cam on the porch connected with decent signal and speed.I am not using their controller or Omada software - web configuration only.Tried installing the software, and all I get were endless errors about ports being closed - on the same subnet, and temporarily turned off the firewall on my desktop, but didn't help. Still wouldn't connect, so one star off for that and the needless complexity of using a Management VLAN, and possible log in issues.One word of caution: If you enable Management VLAN (I use VLAN 10), then it will *only* connect on the same subnet (e.g. mine is 192.168.10.x), you cannot access from another subnet no matter what rules you have set up in your router, unless you also check "Layer-3 Accessibility" under Web Server, *plus* you also must check "Layer-3 Accessibility" under SSH Server (but not SSH Login, unless you want that), if you want to connect to the web configuration using HTTPS. All seems very obvious once I found those settings, but it took me way too much time to figure out, assumed it was a firewall setting in my router that was allowing me to ping the EAP245 from other subnets, but not allowing me to connect to it over either HTTP or HTTPS. None of my other equipment - Ubiquiti, Engenius, Netgear - had this issue when I moved them to my management VLAN, so one star off for this needless complexity, with settings scattered over three locations, and *zero* documentation either on the web configuration screens or the user guide for setting this up. A simple two sentence caution on the Management VLAN screen would have been sufficient - or, here's a crazy idea: Why not put the settings there? Last time I checked, there's no law that says you can't duplicate the same settings in several places, so you have all the settings that logically go together for the same function grouped together, so you don't have to hunt all over the UI for a setting on a different page that might be affecting what you're trying to enable.Also, when I log in with HTTPS using Firefox, it keeps wanting to know if I want to save my password (it's already saved), but it shows the password as a string of numbers, not the actual password, so I have to wonder if HTTPS is actually implemented correctly on the EAP245, because it sure seems like maybe it's taking my password and using it to generate a key that it then sends in plaintext across the network. Again, none of my other network equipment generate this weird behavior with HTTPS log ins.Overall, a great value home / SOHO AP that supports VLANs, but one star off. Management VLAN works great across subnets once you enable L3 access. HTTPS, I'm not so sure.