Quick Summary (TL;DR):
For a small Frigate installation, buy a standards-based Gigabit PoE+ switch with enough powered ports and at least 20–25% power headroom. Our compact managed picks are the TP-Link Omada SG2008P (four PoE+ ports, 62 W) and UniFi Lite 8 PoE (four PoE+ ports, 52 W). For six to seven powered endpoints, the NETGEAR GS308EPP offers eight PoE+ ports and a 123 W budget, although its uplink occupies one of those eight ports. The Omada SG2210MP adds eight PoE+ ports, 150 W and two dedicated 1G SFP slots; the Omada SG3210XHP-M2 adds eight 2.5GbE PoE+ ports and two 10G SFP+ uplinks. The UniFi Pro Max 16 PoE is our mixed-speed, higher-power choice: twelve 1GbE PoE+ ports, four 2.5GbE PoE++ ports, two 10G SFP+ uplinks and 180 W total PoE. Do not select a switch from its advertised port count alone: check per-port power, combined PoE budget, spare uplink ports, camera night-time load, AP data speed, fan noise and VLAN support. Frigate runs on your server, not on the PoE switch.
Best PoE Switches for Frigate and Wi-Fi: Verified Shortlist
| Switch | Powered copper ports | Total PoE budget | Data/uplink ports | Best fit |
|---|---|---|---|---|
| TP-Link TL-SG1005P (current UK listing) | 4 × 1GbE PoE+ | 65 W | 1 × 1GbE non-PoE | Budget, unmanaged 2–4 cameras |
| TP-Link Omada SG2008P | 4 × 1GbE PoE+ | 62 W | 4 × 1GbE non-PoE | Compact Omada / VLAN-aware home lab |
| UniFi Lite 8 PoE (USW-Lite-8-PoE) | 4 × 1GbE PoE+ | 52 W | 4 × 1GbE non-PoE | Quiet, small UniFi deployment |
| NETGEAR GS308EPP | 8 × 1GbE PoE+ | 123 W | No separate uplink; one RJ45 used | Fanless, several cameras/APs |
| TP-Link Omada SG2210MP | 8 × 1GbE PoE+ | 150 W | 2 × 1G SFP | Eight-device PoE with fibre uplink |
| TP-Link Omada SG3210XHP-M2 (V3) | 8 × 2.5GbE PoE+ | 240 W | 2 × 10G SFP+ | Multi-gig Wi-Fi APs, 10G core |
| UniFi Pro Max 16 PoE | 12 × 1GbE PoE+; 4 × 2.5GbE PoE++ | 180 W | 2 × 10G SFP+ | Larger mixed camera + Wi-Fi 7 network |
The figures above are manufacturer-rated outputs, not our measurements. Power supplies, port allocation and some hardware revisions vary by market. Confirm the exact model and hardware version on the retailer listing and manufacturer support page before ordering. In particular, older TL-SG1005P V1 documentation describes 802.3af/56 W, while the current UK TL-SG1005P product page specifies 802.3at/65 W. They are not interchangeable specifications.
Choose by Powered Devices, Not the Switch’s Total Port Count
A switch advertised as “8-port PoE” may have eight Ethernet ports all supporting PoE, or eight PoE ports plus separate uplink ports. The distinction matters when cameras fill the switch. For example, a GS308EPP has eight RJ45 ports total. Connect its uplink to the router or core switch and seven RJ45 ports remain for cameras and access points. By contrast, the SG2210MP has eight PoE RJ45 ports plus two 1G SFP slots, so an SFP uplink can leave all eight PoE copper ports free.
An SFP/SFP+ socket is not automatically a spare copper RJ45 port. It may need a compatible optical transceiver, DAC cable or approved copper module; the SG2210MP’s SFP slots are 1G, not 10G. Check the upstream equipment and transceiver support before counting them as usable uplinks.
PoE, PoE+ and PoE++: The Per-Port Limit Matters
| IEEE standard | Common name | Maximum switch-port power (PSE) | Maximum device-side power (PD) | Typical use |
|---|---|---|---|---|
| 802.3af, Type 1 | PoE | 15.4 W | 12.95 W | Fixed cameras, basic devices |
| 802.3at, Type 2 | PoE+ | 30 W | 25.5 W | Many PTZ cameras and Wi-Fi APs |
| 802.3bt, Type 3 | PoE++ | 60 W | 51 W | High-power APs, some PTZ devices |
| 802.3bt, Type 4 | 4-pair PoE | 90 W | 71.3 W | High-power specialist equipment |
The PSE figure is power delivered by the switch port; the PD figure is the maximum guaranteed at the far end under the standard, allowing for cable loss. A switch offering “180 W total PoE” does not imply every port can provide 180 W. Likewise, a 240 W eight-port PoE+ switch is still limited to 30 W per 802.3at port, even though its total budget could nominally support eight 30 W ports.
Read the powered device’s actual standard and maximum input requirement. Some cameras accept 802.3af, others need 802.3at or 802.3bt; some high-power PTZ equipment uses a manufacturer-specific injector or separate power input. Do not assume “PoE” in a product title guarantees interoperability. Standards-compliant active PoE negotiates power before delivery; passive 24 V/48 V PoE is different and should not be connected to ordinary endpoints without verified compatibility.
Calculate the PoE Budget Before Buying
Use each endpoint’s manufacturer-rated maximum power, not its observed daytime idle draw. IR LEDs, heaters, motors and Wi-Fi radios can increase load. Then leave headroom for losses, classification behaviour, ambient heat and one future device. A practical planning target is 20–25% above the summed maxima, but the required margin depends on the equipment and how the switch reserves PoE classes.
Required PoE budget ≈ sum of maximum device demands × 1.25
Example A — small mixed installation (illustrative):
3 fixed cameras × 9 W = 27 W
1 Wi-Fi AP × 21 W = 21 W
Estimated device maxima = 48 W
25% planning headroom = 12 W
Target PoE budget = 60 W
Example B — larger installation (illustrative):
4 cameras × 12 W = 48 W
2 Wi-Fi APs × 21 W = 42 W
Estimated device maxima = 90 W
25% planning headroom = 22.5 W
Target PoE budget ≈ 113 WThe 9 W and 12 W camera values are hypothetical planning inputs, not specifications for a particular camera. The 21 W AP example matches the documented maximum for a UniFi U7 Pro, which uses PoE+ and has a 2.5GbE uplink. A Gigabit-only switch can power that AP but limits its wired link to 1GbE. For a real shopping list, replace every value with the exact model’s datasheet rating and confirm that each individual switch port supports its required IEEE type.
| Illustrative deployment | Devices / power calculation | Headroom target | What to look for |
|---|---|---|---|
| 3 cameras + 1 AP | 3 × 9 W + 21 W = 48 W | 60 W | 4 PoE+ ports, at least ~60 W; SG2008P or current TL-SG1005P |
| 4 cameras + 2 APs | 4 × 12 W + 2 × 21 W = 90 W | 113 W | 6+ PoE ports, ≥123 W; GS308EPP or SG2210MP |
| 8 cameras + 2 APs | 8 × 12 W + 2 × 21 W = 138 W | 173 W | 10+ powered ports; UniFi Pro Max 16 PoE is one candidate |
| 6 APs at 21 W each | 6 × 21 W = 126 W | 158 W | Six compatible PoE+ ports; 180 W+ budget; choose 2.5GbE if useful |
These are sizing illustrations, not guaranteed device-count claims. Some switches reserve an entire PoE class when an endpoint connects, so available power shown in the switch dashboard may differ from instantaneous consumption. If a switch cannot allocate enough power, it may refuse to energise a port or shut down a lower-priority port.
Best Compact Unmanaged Switch: TP-Link TL-SG1005P
The current UK TL-SG1005P is the simplest low-cost answer when you have a handful of ordinary PoE cameras and do not need switch-managed VLANs. It has five 1GbE RJ45 ports, four supporting 802.3af/at PoE+, a 65 W total PoE budget, fanless construction and a dedicated fifth port for the uplink. No controller or subscription is required.
- Choose it for: a small isolated camera segment, or a few cameras behind a router that already handles security boundaries.
- Avoid it for: a switch that must enforce tagged VLANs, eight cameras, high-power PTZ devices or multiple 2.5GbE access points.
- Revision warning: the manufacturer’s V1 page describes 802.3af-only ports and a 56 W budget. Confirm the supplied hardware rather than relying on a marketplace listing that merges revisions.
The current UK product page lists 4.29 W maximum consumption without powered devices at 220 V/50 Hz; this is a manufacturer condition-specific figure, not a measured 24/7 idle average. A PoE switch’s electricity use also includes the power it supplies to cameras and APs.
Best Compact Managed Omada Switch: TP-Link SG2008P
The SG2008P is a better choice when the switch itself must carry VLAN-tagged camera and IoT traffic. It provides eight Gigabit ports, of which ports 1–4 are 802.3af/at PoE+, with a 62 W total budget. It is fanless and supports standalone management as well as Omada SDN management. The other four RJ45 ports remain available for the router, Frigate host or non-powered devices.
For a camera-and-AP mix, 62 W can disappear quickly: two 21 W APs already consume 42 W of their specified maxima, leaving just 20 W of nominal PoE budget for other endpoints. It is a compact four-port PoE switch, not a scalable eight-camera switch. The advantage over the TL-SG1005P is managed network segmentation and ecosystem integration, not greater power.
Best Small UniFi Switch: UniFi Lite 8 PoE
The UniFi Lite 8 PoE (USW-Lite-8-PoE) provides eight 1GbE RJ45 ports, four of them PoE+, and a 52 W total PoE budget. Its compact form factor and UniFi Network management make it suitable for a couple of cameras plus one or two modest access points in an existing UniFi installation.
Its limitation is 52 W across four powered ports. Four devices each requiring 20 W cannot all run at their rated maxima. Also, its ports are Gigabit: a Wi-Fi 7 AP with a 2.5GbE uplink will negotiate at 1GbE. Buy the Lite 8 because you want a quiet, centrally managed small switch—not because you expect four full-power PoE+ devices.
Best Fanless Eight-Port PoE Option: NETGEAR GS308EPP
The GS308EPP is a useful middle ground for a camera-heavy home: eight Gigabit RJ45 ports, all supporting 802.3at PoE+, with a combined 123 W budget. NETGEAR specifies a fanless design, basic management features, PoE prioritisation and per-port power controls. You do not need a full network-controller ecosystem to use it.
The main trap is the uplink. With one copper port connected to the rest of the network, you have seven ports left for powered devices. If you need eight cameras plus an uplink, add an upstream switch or choose a model with dedicated uplink slots. Also verify that the exact management feature set is sufficient for your VLAN design; “smart managed” is not synonymous with a full-featured enterprise switch.
Best Eight-Port Omada PoE Switch: TP-Link SG2210MP
The SG2210MP has eight 1GbE PoE+ RJ45 ports, two separate 1G SFP slots and a 150 W total PoE budget. It supports VLANs, ACLs, QoS, IGMP snooping and Omada management. For a cupboard with six to eight cameras and an existing Omada router, this is a sensible step up from compact four-port models.
Unlike the small fanless options, TP-Link lists one fan for the SG2210MP hardware specifications. Do not assume it is silent in a bedroom or living room. The SFP uplinks are Gigabit, so this is not the best fit when you need a 2.5GbE Wi-Fi access point or a 10GbE core uplink. If your upstream router has only copper Ethernet, plan a compatible SFP copper module or sacrifice a powered RJ45 port for the uplink.
Best Eight-Port 2.5GbE Omada Option: SG3210XHP-M2
The SG3210XHP-M2 (manufacturer UK V3 page) supplies eight 2.5GbE 802.3af/at PoE+ ports, two 10G SFP+ uplinks and a 240 W combined PoE budget. It is a strong option when several Wi-Fi 6/7 access points genuinely benefit from 2.5GbE wired connections and your core or NASAliExpress price network already uses 10GbE.
However, the 240 W figure is a total: each RJ45 port is still PoE+, not 60 W or 90 W 802.3bt. A device requiring PoE++ is not compatible merely because the switch has spare total wattage. TP-Link lists two fans and a rackmount 440 mm chassis; this is less suitable for a silent, compact home office. Check the exact SG3210XHP-M2 hardware revision and regional SKU before buying.
Best Larger Mixed-Speed UniFi Switch: Pro Max 16 PoE
The UniFi Pro Max 16 PoE combines twelve 1GbE PoE+ RJ45 ports, four 2.5GbE PoE++ RJ45 ports, two 10G SFP+ uplinks and a total PoE budget of 180 W. That layout makes sense when eight or more fixed cameras only need Gigabit, while two or more newer APs benefit from multi-gigabit links and possibly 802.3bt power.
It is not a 180 W-per-port switch. For example, eight hypothetical 12 W cameras and two 21 W APs add up to 138 W of maximum endpoint load; with 25% planning margin that becomes about 173 W, within the switch’s 180 W nominal budget. Ten powered devices also fit its port layout. But higher-power APs, PTZ cameras or future additions can exhaust the budget; calculate the real inventory before committing.
A 16-port mixed-speed managed switch is a different investment from an inexpensive five-port camera switch. Choose it for real VLAN, uplink and PoE++ needs, not simply because it is the premium option.
Do Frigate Cameras Need 2.5GbE or 10GbE?
Almost never individually. An IP camera streaming at a few megabits per second is nowhere near saturating a 1GbE port. The Frigate server normally receives streams from multiple cameras; the relevant question is aggregate bandwidth on the uplink, plus other traffic such as NASAliExpress price transfers and access-point clients.
| Illustrative recording streams | Aggregate camera traffic | Share of 1GbE line rate | Interpretation |
|---|---|---|---|
| 4 cameras × 6 Mb/s | 24 Mb/s | 2.4% | Gigabit is comfortably sufficient |
| 8 cameras × 6 Mb/s | 48 Mb/s | 4.8% | Gigabit still has substantial capacity |
| 16 cameras × 8 Mb/s | 128 Mb/s | 12.8% | Gigabit usually fine for camera traffic alone |
| 24 cameras × 10 Mb/s | 240 Mb/s | 24% | Check actual live-view, recording and other uplink traffic |
These are illustrative bitrates, not benchmarks or camera specifications. Actual bitrate depends on codec, scene complexity, frame rate, resolution and camera settings. Frigate recommends suitable detection streams rather than simply maximising resolution and frames per second. A lower-resolution detection substream can reduce decoding load while the main stream is retained for recording.
A 10G SFP+ uplink becomes valuable when the same switch aggregates several 2.5GbE Wi-Fi access points, NASAliExpress price traffic and high-speed clients. It is rarely necessary for a camera-only switch. If a Wi-Fi 7 AP has a 2.5GbE or 10GbE wired interface, choose that speed for the AP port if you want to avoid constraining wireless-to-LAN transfers. For more context see Best 2.5GbE Switches for a Smart Home and Home Lab.
The Right Network Layout for Frigate, NAS and Home Assistant
Power delivery and security are separate jobs. A PoE switch powers and connects cameras; Frigate receives their RTSP/other supported streams on a mini PCAliExpress price, server or NASAliExpress price. Home Assistant integrates with Frigate over the network. The NAS may store recordings, but the switch itself performs no object detection or video recording.
Internet / router / firewall
|
Managed core switch
/ \
Camera VLAN Trusted LAN / server VLAN
| |
PoE switch Frigate mini PC
| | | | |
IP cameras NAS storage
| |
(isolated) Home Assistant
Optional: separate Wi-Fi AP VLAN/SSID mappings
for trusted, guest and IoT wireless clients.Where your PoE access switch supports 802.1Q VLANs, use a tagged uplink to the router/core switch and assign camera ports as untagged/access ports in the camera VLAN. The router/firewall, not the VLAN tag alone, enforces cross-VLAN restrictions. Permit Frigate to reach camera streaming and management ports as needed; deny camera-initiated access to trusted PCs and the Internet unless there is a documented requirement.
If you use an unmanaged PoE switch, it can still be placed entirely on a dedicated camera VLAN via a single untagged upstream access port. What it cannot do is independently split its own downstream ports across multiple VLANs. Do not plug both trusted devices and cameras into the same unmanaged switch and assume that they are separated.
VLAN and Multicast Features Worth Paying For
| Feature | Why it matters | When you can skip it |
|---|---|---|
| 802.1Q VLANs | Separates cameras, IoT and trusted clients across a managed switch | All ports are on one dedicated upstream camera VLAN |
| Per-port PoE control | Remote power cycle of an unresponsive camera; prioritise essential devices | A tiny plug-and-play installation |
| PoE power reporting | Shows class reservations and actual draw where supported | Optional, but helpful during commissioning |
| IGMP snooping | Can constrain multicast distribution for discovery/video use cases | Most unicast RTSP camera traffic does not need it |
| LLDP | Helps document neighbours and power negotiation where supported | Simple unmanaged setup |
| ACLs / port isolation | Additional local restrictions; complement firewall rules | Segmentation already enforced upstream |
| SNMP / controller monitoring | Alerts for PoE faults, port flaps and uplink failures | You are content with manual inspection |
A switch does not need to be the same brand as the cameras or Frigate. Standard Ethernet, 802.3af/at/bt power negotiation and ordinary IP networking are the important interoperability layers. UniFi and Omada controllers are valuable for unified monitoring and provisioning, but they are not required to make standards-compliant PoE cameras work.
How to Avoid Camera and AP Power Failures at Night
A daytime installation test can miss the highest-load conditions. IR illumination may switch on after dark; an outdoor PTZ camera may simultaneously pan, tilt, heat its enclosure and illuminate the scene. A Wi-Fi AP can change radio utilisation as client traffic increases. The correct acceptance test uses the endpoint’s specified maximum load and the switch’s power-allocation dashboard, not only a quiet midday snapshot.
- Record the exact camera/AP model, PoE standard and manufacturer-rated maximum input power.
- Check the switch’s per-port power standard and combined budget; calculate spare power.
- Use good-quality solid-copper Cat5e/Cat6 cabling, correct termination and appropriate outdoor-rated cable/protection.
- Verify that each device negotiates the expected data speed and power class. Look for PoE-denied events or ports repeatedly resetting.
- Test camera night mode, IR, any PTZ movement and busy Wi-Fi periods. Check link stability and available PoE headroom.
- Confirm Frigate recording continues and that Home Assistant can still reach the integration after a camera or switch restart.
Avoid copper-clad aluminium (CCA) cable for PoE runs. Resistive loss and heating increase with current, cable length and poor terminations. For long runs, high-power devices or outdoor links, follow the relevant cable and lightning/surge-protection requirements. The usual 100 m copper Ethernet channel limit is not a guarantee that a marginal cable will deliver the required PoE power reliably at that distance.
Should You Use a PoE Injector Instead?
A separate standards-compliant injector is often better than replacing a good switch for one unusual device. If you already own a managed Gigabit switch and need one 2.5GbE Wi-Fi AP with 802.3at power, a suitable 2.5GbE PoE+ injector can be economical. Similarly, a single PoE++ camera or AP may be better served by a compatible 802.3bt injector than by buying a large PoE++ switch.
The trade-offs are extra mains adapters, more cables, a more complicated UPS plan and less central visibility of power faults. Check the injector’s data speed as carefully as its power standard: a 1GbE-only injector can silently turn a 2.5GbE AP installation into a Gigabit link. Never substitute a passive injector unless the endpoint explicitly requires and supports that voltage/pinout.
UPS Sizing: Include the Powered Devices, Not Just the Switch
When a switch powers cameras and APs, its UPS must cover the switch electronics plus the actual power delivered to endpoints, with conversion losses and battery derating. A 150 W PoE budget is the maximum power available to endpoints, not the switch’s fixed continuous consumption. The switch may draw far less when lightly loaded, but UPS sizing should use a credible worst-case or measured peak, plus router, Frigate server and NAS if those must remain running.
A PoE camera network staying online while the Frigate host or storage goes down does not preserve recording. Decide what needs continuity: router/firewall, PoE switch, camera links, Frigate compute, storage and any network link to the NAS. Also plan clean shutdown for systems with disks. A 10-minute UPS requirement is different from a 60-minute surveillance requirement; use the UPS maker’s runtime curve at the combined load rather than extrapolating from VA alone.
Power Consumption and Five-Year Cost: Do Not Double-Count PoE
A switch’s wall power comprises its own electronics and losses plus the power delivered to cameras/APs. If those endpoints would otherwise use separate mains adapters, the endpoint electricity is not an extra cost created by choosing PoE. Compare the switch’s overhead, PSU efficiency and always-on operating behaviour, not the PoE budget printed on the box.
Illustrative switch overhead comparison (not measured products):
6 W average overhead × 8,760 h / 1,000 = 52.56 kWh/year
15 W average overhead × 8,760 h / 1,000 = 131.4 kWh/year
Difference = 78.84 kWh/year
At an illustrative £0.25/kWh:
£19.71/year difference; £98.55 over five years
Add the powered cameras/APs separately only when calculating
the TOTAL network load; do not count their power twice.The example uses hypothetical 6 W and 15 W overhead and a hypothetical electricity tariff, not manufacturer test results or a forecast of UK prices. Fan-cooled multi-gigabit switches can use more power and produce more noise than small fanless Gigabit models, but exact consumption varies with transceivers, port speed, PoE load, firmware and temperature. A 10GBASE-T SFP+ module can also increase heat and power consumption compared with a short DAC, subject to compatibility.
Port Count and Uplink Planning for Four, Eight and Sixteen Cameras
| Camera deployment | Powered endpoints to allow for | Practical topology | Key constraint |
|---|---|---|---|
| 2–4 fixed cameras | 4 cameras, perhaps 1 AP later | 5–8-port switch with dedicated uplink | Four PoE ports leave no AP growth if all cameras use them |
| 6 cameras + 1 AP | 7 powered devices | 8-port PoE switch + upstream copper uplink | An eight-port all-PoE model uses one port for uplink |
| 8 cameras + 2 APs | 10 powered devices | 16-port mixed PoE switch or two switches | Budget and port speeds for APs |
| 16 cameras + several APs | 20+ powered devices | Dedicated camera PoE switch(es), separate multi-gig AP switch | Power distribution, UPS, uplink and physical cable management |
For 16-camera builds, two access switches may be preferable to one very large unit if the cameras are on opposite sides of a property. This can shorten cable runs and make faults easier to isolate, but it adds another switch, power supply and UPS location. If cameras span outbuildings, consider fibre between buildings for electrical isolation and surge resilience, with local power and suitable outdoor-rated installation.
Installation Checklist: From Box to Reliable Recording
- Label each camera cable and record its location, IP address, switch port and maximum power rating.
- Install the switch where airflow, cable bend radius, mains supply and access for maintenance are adequate. Do not seal a fan-cooled rack switch inside a small cupboard.
- Connect the uplink and verify the negotiated speed. If using SFP/SFP+, check the module or DAC against both vendors’ supported combinations.
- For managed switches, create camera/IoT VLANs, configure the upstream trunk/access port and confirm DHCP or static addressing.
- Connect powered devices gradually while monitoring total PoE allocation and port status. Keep the highest-priority camera on a priority PoE port if the model supports it.
- Add each camera to Frigate using the manufacturer-supported stream path; use suitable detection and recording streams, not unnecessarily high detection resolution.
- Test recorded clips, time synchronisation, nighttime IR, AP load, and recovery after a power cycle. Keep an export or backup of the switch configuration.
Frigate’s current documentation explains how to assign detect and record stream roles and why a lower-resolution detection stream can reduce decoding overhead. The switch does not change that software configuration, but reliable Ethernet and PoE are prerequisites for continuous streams. For compute sizing, see Best Frigate Hardware for 4, 8 or 16 IP Cameras.
Troubleshooting PoE Switches in a Frigate Network
| Symptom | Likely causes | First checks |
|---|---|---|
| Camera works by day, fails at night | IR/LED/heater peak, weak cable, insufficient PoE budget | Check max device rating, PoE denied logs, cable length/quality |
| Camera powers but no video | IP/VLAN/firewall, wrong RTSP path, codec, authentication | Ping camera from Frigate host; test supported stream in camera UI |
| AP reports reduced functionality | Wrong PoE class or insufficient negotiated power | Compare AP required standard with exact port IEEE capability |
| 2.5GbE AP links at 1GbE | Gigabit switch port, 1G injector, cable/negotiation | Check both endpoint PHYs and intermediate injector/switch |
| PoE port repeatedly reboots | Budget exhaustion, thermal limit, endpoint fault | Inspect per-port events and allocation; isolate device |
| Video freezes when NAS backup runs | Congested shared uplink or server/storage bottleneck | Measure uplink traffic, disk I/O and Frigate host load separately |
| Managed switch inaccessible | Management VLAN or controller adoption problem | Verify switch IP, tagged/untagged ports and upstream firewall |
| Unexpected noise/heat | Fan-cooled model, blocked vents, hot SFP+ module | Check fan specification, airflow, module power and ambient temperature |
If a camera fails, separate power, link, IP reachability, stream access and Frigate decoding/recording in that order. Replacing a PoE switch will not fix an invalid camera URL or a Frigate host that cannot decode the chosen stream.
Buying Verdict: Which PoE Switch Should You Choose?
| Your actual requirement | Recommended direction | Main caveat |
|---|---|---|
| Small plug-and-play camera setup | TP-Link TL-SG1005P (current 65 W UK version) | Unmanaged; verify revision and 4-port power total |
| Small managed Omada network | TP-Link SG2008P | Only 4 PoE+ ports and 62 W |
| Small UniFi camera/AP network | UniFi Lite 8 PoE | 52 W and Gigabit-only ports |
| Fanless 5–7 powered endpoints | NETGEAR GS308EPP | Copper uplink consumes one of 8 ports |
| Up to 8 PoE+ endpoints with SFP uplink | TP-Link SG2210MP | 1G SFP only; fan-cooled |
| Many 2.5GbE PoE+ APs, 10G core | TP-Link SG3210XHP-M2 | No 802.3bt PoE++; 2 fans |
| Mixed 1GbE cameras + 2.5GbE PoE++ APs | UniFi Pro Max 16 PoE | 180 W shared budget; higher complexity |
Our overall recommendation: for ordinary fixed IP cameras, buy a managed or unmanaged Gigabit PoE+ switch with sufficient ports, 20–25% budget headroom and a reliable uplink. A fanless 8-port model is often a better home purchase than a noisy rackmount multi-gigabit switch. Choose 2.5GbE and 10GbE for the access points and network core that can use them, and choose 802.3bt only for endpoints that explicitly need it. For existing UniFi or Omada installations, staying within your management ecosystem can simplify monitoring, but it should never override the electrical specifications.
Frequently Asked Questions
Will any PoE switch work with Frigate?
Frigate does not require a particular PoE switch brand. It needs IP connectivity to supported camera streams. The switch must supply the camera’s required IEEE power standard, sufficient per-port and total power, and reliable Ethernet. Camera stream compatibility is a separate question.
Can I use an 802.3at PoE+ port for a PoE++ camera?
Not if the camera requires 802.3bt power for normal operation. Some devices may support reduced-power modes, but that is model-specific. A switch with a large total wattage does not override its per-port IEEE type.
Can an unmanaged switch be used on a camera VLAN?
Yes. Place the entire unmanaged switch behind an untagged access port assigned to the camera VLAN on an upstream managed switch or router. The unmanaged switch cannot independently assign different downstream ports to different VLANs.
Is one Gigabit uplink enough for eight IP cameras?
Usually, yes for camera traffic alone. Eight hypothetical 6 Mb/s streams total 48 Mb/s, well below 1GbE. Measure actual bitrates and include live viewing, NAS transfers and other devices sharing the uplink.
Should I power a Wi-Fi 7 access point from a Gigabit PoE switch?
It may be electrically compatible if the PoE standard and power budget match, but the wired link will negotiate at 1GbE. A 2.5GbE PoE+ or PoE++ switch is preferable when the AP and client workloads can exploit higher wired throughput.
Do I need a UniFi or Omada controller for the switch to pass traffic?
Not necessarily. Standalone switching and basic management depend on the model. Controller software adds centralised configuration, monitoring and some ecosystem features. Check the exact switch documentation rather than assuming every feature works without adoption.
Related Home Server and Networking Guides
Manufacturer Specifications and Technical References
- TP-Link TL-SG1005P – current UK model and PoE budget
- TP-Link TL-SG1005P V1 – older hardware revision comparison
- TP-Link SG2008P – 4 PoE+ ports, 62 W and management
- Ubiquiti UniFi Lite 8 PoE – official technical specifications
- NETGEAR GS308EPP – 8 PoE+ ports, 123 W
- TP-Link SG2210MP – 8 PoE+ ports and 1G SFP uplinks
- TP-Link SG3210XHP-M2 V3 – 2.5GbE PoE+ and 10G SFP+
- Ubiquiti UniFi Pro Max 16 PoE – port layout and 180 W budget
- Ubiquiti U7 Pro – 21 W, PoE+ and 2.5GbE requirements
- Cisco – IEEE PoE types and maximum port power
- TP-Link – PoE power at switch versus powered device
- Frigate – camera setup and stream recommendations
- Frigate – camera roles and stream configuration