TP-Link Omada Outdoor Access Point | WiFi Extender Outdoor Universal Compatible | N300Mbps | IP65 Weatherproof | Seamless Roaming | Omada Remote Managed(EAP110-Outdoor)

Bought it so I could extend my WIFI to my Detached outdoor Garage and to my Pool ...... works Fine

My ultimate goal is to put this outside near the edge of our property to get a signal where it is now very weak. Currently the mesh network inside our house barely reaches the device I have out there and so it drops off regularly.Since it's quite cold out, for the time being I've done some other testing. Set up is quick and straightforward. I had it configured and working in under 15 minutes. I hooked it up indoors, in my computer room a couple feet away from my primary mesh node. I plugged it directly in to my switch, just like the mesh node. I then ran speedtest from my phone, once with the mesh network and once with the EAP110. The results were shocking! The EAP was getting 50 Mbs while the mesh network was getting 40 Mbps.I then went to different locations inside the house, in different rooms. We have two other mesh nodes in the house providing full coverage. To my phone, the signal from the EAP was as strong or stronger than the mesh signals in most locations.Being extremely happy with these results, I moved the EAP into my garage, and pointed one of the antennas in the direction of the device with the weak signal I was ultimately trying to reach. Again, the signal strength was stronger than what it had been receiving from the closest indoor mesh node. This should be good enough until the weather gets warmer and I can move it outdoors closer to the device and set it up as I intended.Also note, I'm using some bigger high gain antennas that I had.Update 6/2/2025So, after a year and a half, I finally moved it out of the garage to the outdoor location I had originally intended. I am even more impressed with it now, as the signal range I am getting across my ~4 acre property is astounding. If you have line of sight, you can go very far from it and still have a good signal and decent bandwidth. As you can see in my photos, the final location is atop my very old C-Band dish that I've repurposed as a huge monopod which has 2 Tapo cameras, an air quality monitor, and now the Omada Access Point. All of my cables, power, and network devices are in a weatherproof box buried at the base of the dish.Since these are so inexpensive, I just purchased another to install on the other side of our property so we can be bathed with a strong wifi signal no matter where we are outdoors.I couldn't be more happy with this device. The bang for the buck is off the charts. I may need to buy a third one, just to keep as a spare.

works as intended. set it up in the back yard and forget about it. stretches the entire yard which is nice.

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.

I ordered this as an outside AP dedicated for my Christmas lights. They don't use a ton of data, so i figured the older 300Mbps spec would be fine.....IF....it ran at least @ 150 Mbps it would be fine. Wow was I disappointed.Let me start by saying this is a nice looking, decent to mount and compact AP. But it stops there. They include a POE injector, +1. but not any Ether net cables to connect between it and the switch/router. EVERYONE who sell a POE includes at least 1 short cable for this.Next up you have to download the Omada app to manage the AP. It has you create an account with TP-link, pretty common now adays. It then has you setup a Controller, "in the Cloud" Which I am not a fan of, but hey go with the flow. Get it setup only to find this device is not controllable /compatible with their cloud controller. So you then have to setup a Standalone controller locally on the app. This BTW has a LOT less features than the cloud management does.Lastly, It is up and running once You setup the normal AP stuff. I have about 32 clients connect to it right off. I had 51 in the end too and all worked on the AP no problem with one caveat. The only download at about 15Mbps. Doesn't matter if it has 1 device connect or all 50+ I had later it is exactly the same. I tried every setting adjustment I could and NOTHING changes it.I worked in IT as a Network administer for 20+ years, so i know my networking stuff. This thing is a piece of crap.Avoid like the plague.

Excellent!!!