📶 TP-Link EAP235-Wall: Powerful In-Wall Wireless Gigabit Access Point with MU-MIMO & Beamforming Review

Earlier I asked here whether the TP-Link EAP235-Wall Access Point can cover a two-storey house more than 1800 square meters. Feet, every structure is different, but proper placement can be very helpful. I placed mine on the ground floor indoors in the middle of the outside wall where there was a phone jack 4 feet off the floor. The WiFi signal with 2.4 and 5 GHz is very good or excellent everywhere in the house, even in the basement. The signal is good to use in the backyard. Modem, router…

I have gigabit fios. Got a direct gigabit line from a router with kat6. I've seen downloads at 400Mbps. shakes no faster than 350MB/s while standing nearby. I only use it for 5GHz mode. 2.4GHz mode never exceeded 100Mbps. That's not bad performance, but I'm a bit disappointed that I didn't get the full advertised speed of 860 Mbps.

Slow connection. Wi-Fi extender works better than this. Received two wall units and sent them back. I'm using a $30 Tp Link Re 220 range extender and I can see all four of my Amcrest IP cameras. To make them work, I ran Category 7 wiring around my house and hooked them up. high. When I saw that my Amcrest IP camera was connected to the devices, I couldn't see the live video. Maybe I should try a ceiling mount hotspot because it has more power. very slow, and one of them doesn't show live…

Very easy setup and good speed over hotspot. The device gets a little warm, although only 1 or 2 clients with low usage. I also want it to support fast roaming for a smoother handover. I understand it's intended for hotels or conference rooms that don't need roaming, but it's still a standard feature that all access points should support.

Listed as "an access port that supports POE passthrough to power wired devices". It doesn't clearly state that it requires 802.3at POE+ input and has a maximum output power of 13W. Also, the POE output was OFF by default on the device I received. You need to enable it through the Omada controller. After using my POE+ switch and turning it on, I was able to connect the security camera without any problems. The EAP235-Wall is a good product, so don't get me wrong. It was easy to add to the…

The device works as expected. A word of caution for now. When I do the Sid setup for the VLAN, the Ethernet ports cannot be set for the VLAN ID. May or may not change on firmware update. I was hoping to be able to make Sid to VLAN and VLAN on each port, specifically route POE through the port. and make the POE output port work with the established VLAN while wireless communication works with another VLAN.

The Ubiquiti device had a constant problem with dropping DHCP packets and the devices often failed to connect to the network. Omada devices do not have this problem. I noticed that the configuration UI is almost identical to Ubiquiti's UI. It is clear that someone copied someone.

Listed as "a POE passthrough capable access port to power a wired device". The maximum output power is 13W. Also, the POE output was off by default on the device I received. You need to enable it through the Omada controller. After using my POE+ switch and turning it on, I was able to connect the security camera without any problems. The EAP235-Wall is a good product, so don't get me wrong. It was easy to add to the controller and once I ticked the right boxes it works flawlessly. I'm very…

Used to solve poor 5G coverage in my home office (3 walls including mirrors and tiles on the way to the main hotspot). Yes, I had to make an awful trip to the attic to run the cable from my PoE switch there, but now that that little expedition is a thing of the past, it's been pure joy. The device is cheaper than Ubiquiti and I am currently getting 400Mbps+ in my office (400Mbps throughput from my ISP). If you're installing it very high or low (mine is installed upside down, right under my…

There is currently a known issue with using VLANs. SSIDs with VLANs enabled will not work at the same time as assigning VLANs to 3 Ethernet ports. I had this issue during the initial setup where the wireless clients weren't assigned IP addresses and the wired clients weren't visible in the Omada controller. It took me a few days to figure this out after a thorough search of the TP-Link support forums. As far as I can tell this issue should be fixed in the next firmware update but it has been…