The Omada Fusion Pro 2.5G PoE puts the router, an eight-port PoE switch and the camera NVR in one box. Our review unit did all three jobs within an afternoon, but not by the route printed on the box. The Bluetooth setup in the Omada app died on a bare “General error.”, and the gateway only came up once we ran the web wizard from a laptop on a LAN port.
Omada sent the gateway, with a 1 TB SSD fitted, and two 8MP cameras for this Omada Fusion Pro review without payment, and the verdict is ours. This first look covers which model to buy, onboarding, firmware and recording. Setup and recording were captured on the pre-release build our unit shipped with, and the cloud failure was checked again on Omada OS 4.0.2 in November 2026. If you want cameras, buy the PoE model.
Pick the Right Fusion Pro Model
Omada ships two Fusion Pro gateways, and you only need one question to choose. Both give you the same Omada OS with the Network and Guard applications, both take one NVMe SSD for recording, and both manage up to 30 Omada devices and about 300 clients. The PoE model adds four more 2.5G ports, a 180 W PoE+ budget across eight of them and a larger touchscreen, so it can power cameras and access points without a separate switch.

| Fusion Pro 2.5G | Fusion Pro 2.5G PoE | |
|---|---|---|
| Ports | 1× 2.5G WAN, 4× 2.5G LAN/WAN | 1× 2.5G WAN, 8× 2.5G LAN/WAN |
| PoE | None | 8× PoE+, 180 W total |
| Touchscreen | 2.51-inch | 3.69-inch |
| Power | USB-C, 9 V / 3 A adapter | 54 V / 4.16 A adapter, 225 W max |
| SSD tray | 1× NVMe, up to 2 TB | 1× NVMe, up to 2 TB |
| Cameras on the SSD (recommended) | 12× 4K or 16× HD | 12× 4K or 16× HD |
| Price band at launch | $250 to $350, check the live price | $400 to $500, check the live price |
Whether you already own a PoE switch decides it. If you do, the plain Fusion Pro 2.5G saves money and still records cameras that your switch powers. If you do not, the Fusion Pro 2.5G PoE is the box that removes a device from your shelf. At launch prices, the gap between the two is roughly $150 for eight PoE+ ports and 180 W of power. Pairing the plain model with Omada’s ES210XPP-M2 switch costs more than the PoE model, so it only makes sense if you need what the switch adds: a 200 W budget, 90 W PoE++ ports for heavier devices and a 10G uplink. Our PoE switch guide for cameras and access points covers the other switch options.
Here is everything in this review with where to buy it. Prices move, so treat the bands as a guide and check the live price before you order:
| Product | Role | Price band | Buy |
|---|---|---|---|
| Omada Fusion Pro 2.5G PoE | The gateway we tested: router, 8 PoE+ ports, NVR | $400 to $500 | Omada store · Amazon |
| Omada Fusion Pro 2.5G | Same gateway and NVR, no PoE | $250 to $350 | Omada store · Amazon |
| Omada ES210XPP-M2 switch | 8× 2.5G PoE++, 200 W, two 10G uplinks; powers cameras for the non-PoE model | $200 to $250 | Omada store · Amazon |
| Omada 8MP Bullet | Outdoor 4K camera we tested | $90 to $110 | Omada store · Amazon |
| Omada 8MP Turret | Indoor/outdoor 4K camera we tested | $90 to $110 | Omada store (out of stock on Amazon) |
Check the Hardware Specs
These figures come from Omada’s specification sheet for the PoE model, read against what our unit reports. Watch the PoE budget, the SSD ceiling and the camera counts, because they decide how far your one box goes before you need an NVR.
| Item | Fusion Pro 2.5G PoE |
|---|---|
| Applications | Omada Network (controller) and Omada Guard (video), built in |
| Managed devices | 30 Omada devices, 300 clients (recommended) |
| Cameras | 16× HD, 14× 2K, 12× 4K or 6× 12MP on the SSD; up to 24 with one Omada or VIGI NVR |
| CPU and memory | Quad-core, 4 GB DDR4 |
| IPS throughput (Omada figure) | 2,364 Mbps |
| VPN throughput (Omada figures) | IPsec 1,332 Mbps, WireGuard 1,044 Mbps, OpenVPN 393 Mbps |
| Fan | One fan, fanless mode at low load, 28.0 dBA at 1 m max |
| Size and weight | 226 × 135 × 31.5 mm, 828 g without SSD |
| Mounting | Desktop; wall plate and rack kit sold separately |
The 2 TB SSD cap is the limit you plan around. At the 4.24 Mbit/s our Bullet streamed at night, eight 4K cameras recording around the clock would write about 370 GB a day and fill 2 TB in under a week. A larger site either records on motion only or adds an Omada NVR, which raises the ceiling to 24 cameras (Omada treats its own cameras as third-party devices on a VIGI NVR). Our unit shipped with a 1 TB Kingston NV3 already in the tray, and the Guard app reports 930 GB usable after formatting. Omada’s storage guide says retail units come without an SSD, so budget for one.

The front is all touchscreen. Before setup it shows “Ready for setup” with a QR code for the app, then the MAC address and the default LAN IP, which is all you need to start. Omada lists a live speed test, port status, health score and CPU, memory and temperature readouts for it after setup, with a screensaver after 3 minutes and the screen off after 15.
See How the Lab Is Wired
Our test bench keeps the gateway behind an existing router. Its WAN port takes a DHCP address from that network, and its own LAN runs on the factory default, 192.168.188.0/24. Both cameras sit on PoE ports 2 and 3, and a Mac on LAN port 6 does the management:

Camera traffic never crosses the WAN. The cameras stream to the Guard application on the gateway, and Guard writes to the SSD. The only thing that wants to leave the building is the cloud binding, which our unit could not complete.
Set Up Fusion Pro From a Laptop
Omada’s pitch is under 10 minutes from unboxing to a live network over Bluetooth with the Omada app. On our unit the app found the gateway, brought the WAN up, created the TP-Link ID and formatted the SSD, then failed at the camera step with “General error.” on every retry. The phone was on cellular data, not on the gateway’s LAN, which matters for the reason below.
The web wizard is the fallback Omada documents, and it worked. Our Fusion Pro setup walkthrough covers every screen and fix, and the short version follows. Plug your laptop into any LAN port, let it take a DHCP address, and open https://192.168.188.1. The certificate is self-signed, so expect a browser warning. The wizard runs five steps:
- Network Detection: WAN type, with a speed test
- Sign In: a TP-Link ID, or Create a Local Account
- Set Up Controller: name, country, time zone, terms
- Add Devices: the device account and the cameras it found
- Complete: a summary, then the dashboard

From the internet settings page to the dashboard took us about seven minutes, and about three and a half of those went on the failed sign-in described below and the switch to a local account. Both cameras showed up in the first scan, and the device account step that broke in the app went straight through. That account becomes the login on every adopted camera, so pick a real password here rather than the auto-generated one if you plan to pull RTSP streams later.
Error: “Something went wrong. Please try again later or contact our technical support.”
This toast appeared every time we signed in with a TP-Link ID in the web wizard. The wizard’s API call behind it returns {"errorCode":-1,"msg":"Device's device secret not match"}, which means Omada’s cloud rejects this unit’s identity, not your account. Choosing Create a Local Account on the same screen skips the cloud entirely and lets the wizard finish. Until binding works you lose remote access through the Omada cloud, the cloud firmware check and the ad blocker’s database updates. We haven’t yet tested what it means for app alerts.

We think the same cloud rejection sits behind the app’s “General error.”, since the app’s camera step runs through the cloud account the wizard couldn’t bind. Binding from Settings, Cloud Access after the firmware upgrades failed the same way, and the cloud status check returned -1500, “TP-Link Cloud Server is busy”. The error points at this unit’s cloud record rather than the firmware, so a retail unit may bind fine, and we are taking it up with Omada.
The knock-on effect you can see is a dashboard alert that the ad blocker database could not update because it “Failed to verify cloud service authorization”.
Error: “General error.” in the Omada app
The app shows this after Set Device Account, with no code. Our unit was on a pre-release build, and a later public update fixes a Bluetooth setup timeout, so a retail unit may never show it. Omada’s own advice for the timeout is to connect from the same local network and retry, and the web wizard on a LAN port is the cleanest way to do that. If your phone is on cellular or on a network upstream of the gateway, it is not on the Fusion Pro LAN.
Upgrade the Firmware First
Our unit arrived on an Omada OS build older than the first public release, and the cloud updater offered nothing: Settings > OS & Applications > ⋮ > Cloud Upgrade on the Omada OS card reported “No new release” on the Stable, RC and Beta channels. That likely ties back to the cloud problem, since the update check asks the same cloud that refused to bind, though a pre-release build may also sit outside every update channel. The images on Omada’s download page are the way forward: each is a .zip, so extract the .bin inside and pick it under ⋮ > Local Upgrade on the same card, which accepts files up to 2 GB.

Read the release notes before you jump. The notes for the next update name a minimum starting build newer than the one our unit shipped with. The latest notes list no minimum, so we took the safe route through the intermediate image. That made two hops:
| Step | Omada OS | Guard app | Upload | Reboot |
|---|---|---|---|---|
| As shipped | 4.0.0 Build 20260910 Rel.63053 | 2.3.0 | n/a | n/a |
| Hop 1 | 4.0.0 Build 20260914 Rel.73217 | 2.3.0 | 148 s | about 4 min |
| Hop 2 | 4.0.2 Build 20260924 Rel.31345 | 2.3.1 | 156 s | about 4 min |
Each image is about 1.27 GB. The Browse button in our automated test browser never opened a file picker, so we sent both files through the same upload call the dialog makes. Each upload took about two and a half minutes over the wired LAN, then the gateway rebooted for roughly four more. The cameras dropped off during each reboot and came back without help, and recording resumed on its own. Guard updated itself to a newer build in the second hop, so check the versions page afterwards rather than assuming only the OS moved.

Cameras update from the Guard side, under Devices. We updated ours one at a time, and each took about two and a half minutes including its reboot. The Update button in that prompt ignores clicks while the dialog is still fading in, so give it a second before you click.
Record Cameras to the SSD
Recording starts as soon as you adopt a camera. Guard turned on loop recording by default with 5 seconds of pre-recording. Seven minutes after the wizard finished, Guard counted 13 minutes recorded across the two cameras and 2 GB of recording space in use, next to the 4 GB the system reserves on the drive.

Both cameras together drew 9.8 W of the 180 W PoE budget, so power is not what limits this box: storage is.

Guard’s storage page is where you check the drive. It reports the model, firmware, life span, temperature and power-on hours, which is more than most small NVRs expose. Ours read 100% life span at 39°C.

In the browser, live view puts both camera feeds side by side, with snapshot, recording, two-way talk and siren controls under each tile. Night vision, AI detection accuracy and the siren get their own write-up once we have three nights of footage.

You are not locked into Guard either. Both cameras serve RTSP on port 554 and ONVIF on ports 2020 and 80 with the device account from the wizard, while Guard keeps recording. We probed both with ffprobe from the LAN:
| Stream | Video | Audio | Night bitrate, Bullet / Turret |
|---|---|---|---|
rtsp://<user>:<pass>@<camera>:554/stream1 | 3840×2160 HEVC Main, 25 fps | G.711 A-law, 16 kHz mono | 4.24 / 1.35 Mbit/s |
rtsp://<user>:<pass>@<camera>:554/stream2 | 848×480 HEVC, 25 fps | G.711 A-law, 16 kHz mono | 0.36 / 0.38 Mbit/s |
| ONVIF port 2020, profile 3 | 640×360, listed as JPEG | not checked | not measured |
One detail matters if you plan to feed these cameras into a Frigate NVR. ONVIF labels the first two profiles H264, but the RTSP streams are HEVC. Frigate decodes HEVC through ffmpeg, but browser live view over WebRTC may not play it in some browsers, so you either switch the camera’s encoding to H.264 or live with a fallback in the browser.
We have since run both cameras through Frigate and added them to Home Assistant over ONVIF. Our Omada cameras in Frigate guide has the tested config and the defaults to change first. The first is the 12-second keyframe gap of the default H.265+ main stream, which plain H.265 or H.264 brings down to 2 seconds. The Bullet now sits in our Frigate camera picks. The night bitrate sample above is a single 30 seconds after dark, and the storage-per-day maths needs day and night averages, so treat it as a rough number for now.
Buy the Fusion Pro 2.5G PoE If You Want Cameras
After the first day, the Fusion Pro 2.5G PoE does what it claims once it is set up. It routes, powers both cameras on about a twentieth of its PoE budget and records to the SSD without being asked. It also exposes standard RTSP and ONVIF, so your footage is not trapped in Omada’s app. It is a good fit for:
- a small office or studio with up to about a dozen cameras
- a homelab moving off separate router, PoE switch and NVR boxes
- an Omada network already, with the controller built in
Skip it if you need more than 2 TB of local recording without buying an NVR, or if cloud management on day one is a hard requirement and you can’t wait out a problem like ours, where the unit still can’t bind to the Omada cloud. If you are weighing it against Ubiquiti, our Omada vs UniFi comparison covers the controller side and the UniFi Cloud Gateway roundup covers the boxes this one competes with. The Omada 8MP Bullet we tested is available alongside it.
Still to come on this page: gateway throughput with IPS on and off, power at the wall idle and with both cameras, fan noise under load, and whether the cloud binding works once Omada resets our unit. We couldn’t test multi-site SD-WAN or an access point yet, because we have one site and the AP hasn’t arrived.