Best PoE Wi-Fi access point for a homelab: Omada vs UniFi

Run one Ethernet cable to a sensible AP position and you can put Wi-Fi where your devices need it, with power coming from the switch. Start with Omada EAP650 for a gigabit Wi-Fi 6 lab, EAP723 for dual-band Wi-Fi 7, or UniFi U6+ when you’re already building around UniFi. Want a 6 GHz radio? Look at U7 Pro.

This research-based guide uses maker specifications and official controller documentation.

For one AP on a non-PoE switch, choose a PoE injector by power class and Ethernet speed so the power supply fits the uplink.

Quick picks: choose the radio and the controller together

• Best Omada starter for IoT VLANs: EAP650. Wi-Fi 6, a gigabit uplink and Omada VLAN controls make it a sensible starting point for a separate IoT SSID.
• Best dual-band Wi-Fi 7: EAP723. Choose it for newer compatible clients and a 2.5GbE wired connection. It uses 2.4 and 5 GHz, with no 6 GHz radio.
• Best Wi-Fi 7 fit when you want 6 GHz: U7 Pro. Its third band is the important difference; use the maker’s U7 Pro page for this option.
• Best existing-UniFi Wi-Fi 6 fit: U6+. Keep AP management in UniFi when a gigabit uplink and dual-band Wi-Fi 6 cover the job.
• Omada 5 GHz step-up: EAP670 V2. Its 4×4 5 GHz radio and 2.5GbE uplink give you another option within the Wi-Fi 6 family.

Choose the controller family you want to manage before collecting ceiling discs from both brands. Our Wi-Fi 7 router guide covers the router decision; an AP adds wireless access to your existing routed network.

Compare the six access points

Access point	Wi-Fi and bands	Wired uplink	Negotiated PoE requirement	Published maximum draw
Omada EAP650	Wi-Fi 6; 2.4/5 GHz	1 GbE	802.3at PoE+	15.5 W, current V3 reference
Omada EAP670 V2	Wi-Fi 6; 2.4/5 GHz	2.5 GbE	802.3at PoE+	22.3 W
Omada EAP723	Wi-Fi 7; 2.4/5 GHz	2.5 GbE	802.3at PoE+	17.83 W on PoE, US V2.20 reference
UniFi U6+	Wi-Fi 6; 2.4/5 GHz	1 GbE	PoE / 802.3af	9 W
UniFi U7 Lite	Wi-Fi 7; 2.4/5 GHz	2.5 GbE	PoE / 802.3af	13 W
UniFi U7 Pro	Wi-Fi 7; 2.4/5/6 GHz	2.5 GbE	PoE+ / 802.3at	21 W

Power figures are the makers’ maximums—plan your switch around them.

Ubiquiti’s PoE reference distinguishes PoE, PoE+ and the higher-power 802.3bt modes. None of these six APs requires 802.3bt.

Omada: start with the wired uplink you need

EAP650 is the uncomplicated Wi-Fi 6 starting point. Its gigabit port fits a gigabit backbone, and it supports VLANs without requiring a Wi-Fi 7 client. Use an Omada controller when you want to manage several APs and their SSIDs together.

EAP670 V2 is the 5 GHz Wi-Fi 6 step-up. You get 4×4 MU-MIMO on 5 GHz and a 2.5GbE uplink. Pick it for a lab full of 5 GHz clients and a 2.5GbE backbone; its higher maximum power consumption belongs in the switch budget.

EAP723 is the dual-band Wi-Fi 7 choice. It adds features such as Multi-Link Operation for compatible clients, but it still uses 2.4 and 5 GHz. That makes it a different purchase from a tri-band AP with 6 GHz. Its current US specifications also say the DC adapter is not included; using a suitable PoE+ port keeps the installation to one cable.

UniFi: U6+, U7 Lite or U7 Pro?

U6+ fits a Wi-Fi 6 expansion of an existing UniFi network. Its gigabit uplink and 9 W maker maximum suit a modest AP role.

The U7 Lite brings a 2.5GbE uplink and Wi-Fi 7 while staying dual-band. U7 Pro adds 6 GHz and requires PoE+. Choose Pro when that extra radio is part of the plan, then pair it with clients that can use it.

A Wi-Fi 7 badge alone doesn’t tell you which bands an AP has. Compare the actual radios, your clients and the wired uplink. A 2.5GbE AP connected to a gigabit switch still has a gigabit wired link; see the switch and NIC guide when planning the backbone.

Where the controller runs—and which account you need

You can keep management local in either ecosystem. Cloud-hosted control is a separate choice.

Management route	Where it runs	Account requirement
Omada standalone AP	AP web interface	Local device credentials for local management
Omada Software Controller	Your own host	Local controller account; TP-Link ID for optional cloud access
Omada hardware controller	Dedicated controller	Local controller account; TP-Link ID for optional cloud access
Omada Cloud-Based Controller	Vendor-hosted service	TP-Link ID
UniFi OS Server or UniFi console	Your own server, CloudKey or suitable Cloud Gateway	Local credentials; UI Account optional for remote management
Official UniFi Hosting	Ubiquiti-hosted service	UI Account through Site Manager; hosted subscription

Omada’s software controller page describes on-premises software with optional cloud access. Its controller login guide distinguishes local accounts from TP-Link ID cloud login.

For UniFi, UniFi OS Server is now the standard self-hosting route, replacing the legacy Network Server. The current self-hosting guide makes remote management optional. Keep the server running to view and manage devices; if it goes offline, adopted devices continue with their last configuration.

A mini PC can host management software if it meets the current requirements; our mini-PC guide helps with the hardware choice. A dedicated controller keeps management independent of experiments on your main server. For a multi-AP lab, choose a controller rather than building the plan around basic standalone setup.

PoE: count standards, ports and watts

The PoE switch guide already makes the key distinction: per-port power and the shared budget are separate checks.

For example, NETGEAR GS305EP has four powered ports, up to 30 W per port and 63 W shared. The TL-SG1005P overview profile used in that guide specifies 802.3af and 15.4 W per port. Don’t choose that af-only profile for an AP requiring PoE+, even if you’ve seen a low idle reading elsewhere.

Here are mixed AP/camera examples using maker maxima. The cameras are the guide’s Color4K-T-S2, rated at 9.6 W maximum PoE input each. We apply the same assumed 25% planning allowance used in the camera guide, with decimal rounding half-up.

Example fleet	Powered ports	Combined maker inputs	With 25% allowance	GS305EP, 63 W
One EAP650 V3 reference + two cameras	3	34.70 W	43.38 W	Fits this planning example
One U7 Pro + two cameras	3	40.20 W	50.25 W	Fits this planning example
Two U7 Pro + two cameras	4	61.20 W	76.50 W	Choose a larger shared budget

The calculation is sum the device maxima, then multiply by 1.25. It also checks the example’s powered-port count and per-port allowance against GS305EP’s limits.

The larger switch options and their revision-specific budgets are in the PoE buying guide.

Give IoT its own SSID—and finish the VLAN job

Plan a VLAN-capable router/firewall and a managed switch alongside the AP. Both ecosystems can map an SSID to a VLAN. The AP tags the wireless traffic; the router/firewall decides what that network can reach. Start with one trusted SSID and one IoT SSID, then add complexity when you need it.

1. Create the VLAN, addressing/DHCP service and intended firewall rules on your router. With a third-party gateway, do this before adding the matching network to UniFi or Omada.
2. Carry the required tagged VLANs through the switch to the AP. Preserve the AP’s intended management network and any native/untagged traffic it needs; an AP uplink carrying several SSIDs is a trunk, not a single-VLAN client access port.
3. Map the IoT SSID to its VLAN in the controller. Omada’s third-party-gateway guide and UniFi’s VLAN guide show the configuration.
4. For wired IoT access ports, set the intended untagged VLAN and PVID, and remove unwanted memberships—including default VLAN 1 where it isn’t intended. Adding a PVID alone doesn’t remove old membership. Keep the AP trunk’s management path intact.
5. Test with a client: expected network assignment, working permitted services and blocked access to a deliberately restricted trusted destination. Verify isolation rather than stopping at “it got Wi-Fi.”

For Home Assistant projects, keep discovery in mind. The Matter integration docs recommend putting Wi-Fi Matter devices and Thread border routers on the same VLAN as Home Assistant, with local IPv6 and mDNS traffic flowing. Follow that layout for Matter rather than blindly applying an isolated-IoT recipe. The Home Assistant hub has the device guides to build around it.

Install one, test the basics, then expand

Start with a wired uplink and one AP. Adopt it into the chosen controller, update it, name the SSIDs and confirm the negotiated Ethernet link and PoE status. Test the clients you actually care about before adding more APs.

Check trusted and IoT access separately, and test Home Assistant discovery as well as internet browsing. Save a controller backup once the basic configuration works. Then move on to placement and additional APs using your own observations.

Choose EAP650 for an Omada Wi-Fi 6 start, EAP723 for dual-band Wi-Fi 7, or U6+ to expand UniFi at gigabit. Choose U7 Pro when you specifically want 6 GHz. Get the cable, controller and PoE budget right, and the AP can get on with serving your devices.