How To

Set Up Omada Fusion Pro: Onboarding, Firmware, Cameras and Fixes

This post contains affiliate links. If you buy through them, we may earn a small commission at no extra cost to you. Learn more.

Setting up an Omada Fusion Pro is one five-step wizard, and you can finish it from a laptop in under ten minutes. The box points you at the Bluetooth setup in the Omada app instead, which failed on our unit with a bare “General error.”. The web wizard on a LAN port finished every time once we picked a local account, so that is the path this guide follows.

Original content from computingforgeeks.com - post 188535

You will connect a laptop, pick the account type that works, adopt your cameras, upgrade Omada OS and the camera firmware, and see what each error means. Omada sent the gateway and two 8MP cameras for review without payment; our Omada Fusion Pro review has the verdict and the hardware, and this page is the setup on its own. We tested every step on a Fusion Pro 2.5G PoE in November 2026, from the shipped 4.0.0 build up to Omada OS 4.0.2.

Check what you need first

The wizard runs in a browser and needs nothing installed, but it does need the right cable in the right port. Before you start, make sure these are true:

  • Your internet line or upstream router is plugged into the Fusion Pro’s WAN port.
  • Your laptop is plugged into any of the LAN ports with a cable, not on Wi-Fi.
  • Your cameras are on the PoE ports if you bought the PoE model.
  • Your SSD is in the tray, if you plan to record, with the gateway powered off while you fit it.

The cable matters more than it looks. The gateway does not serve its management page on the WAN side, so a laptop on your existing network cannot reach it even when both share a router. On a LAN port, your laptop gets an address in 192.168.188.0/24 by DHCP and the gateway answers at 192.168.188.1. Still choosing a model? The review explains why the PoE version is the one to get for cameras, and our PoE switch guide covers the separate-switch route if you already own a PoE switch. The PoE model is on the Omada store and Amazon.

Open the setup wizard in a browser

Once the touchscreen says it’s ready for setup, open https://192.168.188.1 on the laptop. Omada’s quick start guide also gives https://omadafusion.net, but we used the IP address, which doesn’t depend on your laptop’s DNS settings. The gateway uses a self-signed certificate, so your browser will warn you; that’s normal here, and you can click through it.

The first screen is Network Detection. If your upstream router hands out addresses, you’ll see “Internet Connected” with WAN1 on Dynamic IP and you can press Next. The Speed Test link on that screen is worth a click, because it proves the WAN side works before you go further. If the gateway doesn’t connect, open Internet Settings and pick your connection type from the five the wizard offers:

Omada Fusion Pro web setup WAN1 Internet Settings with Dynamic IP, Static IP, PPPoE, MAP-E and DS-Lite

Dynamic IP fits a gateway behind another router, PPPoE fits most fibre and DSL lines that hand you a username, and Static IP is for a fixed address from your ISP. MAP-E and DS-Lite carry IPv4 over an IPv6 line, and your ISP will tell you if you need one.

Sign in, or create a local account

Step 2 asks you to sign in with a TP-Link ID, which links the gateway to Omada’s cloud and is what Omada’s own getting-started guide recommends. Try it first. On our unit the cloud refused the sign-in every time, and if that happens to you, you don’t need the cloud to finish setup. Click Create a Local Account under the Sign In button:

Omada Fusion Pro web setup Sign In step with the Create a Local Account link under the TP-Link ID sign-in

Fill in a username and a password twice, then press Create and Sign In. This account only works on your local network, and it’s the one you’ll use to log in to the gateway from now on, so store it in your password manager. A local-only gateway gives up remote access through the Omada app and the cloud firmware check, and ours also logged failed ad blocker database updates. You can still bind a TP-Link ID later from Cloud Access in Settings, which the last step covers.

“Something went wrong. Please try again later or contact our technical support.”

This toast is what the TP-Link ID sign-in showed us on every try, with a working account. The page doesn’t say more, but your browser’s developer tools do: under Network, the bindAndRegisterLocal response read {"errorCode":-1,"msg":"Device's device secret not match"}. That points at Omada’s cloud not accepting this particular gateway rather than at your password, and retrying didn’t change it. Use a local account and carry on; you can come back to the cloud once Omada support has looked at the unit.

Name the controller and set the time zone

Step 3 sets up the Omada controller that runs inside the gateway. The time zone matters more than it seems, because every camera recording, event and log line gets its timestamp from it. Fill in the screen like this:

Omada Fusion Pro web setup Set Up Controller step with controller name, country, time zone and terms checkbox
  1. 1Controller Name
  2. 2Controller Country/Region
  3. 3Controller Time Zone
  4. 4I accept the Terms of Use
  5. 5Next
  1. Type a name in Controller Name. It shows in the header of every page.
  2. Pick your Controller Country/Region.
  3. Check the Controller Time Zone the wizard filled in.
  4. Tick I accept the Terms of Use.
  5. Press Next.

If you skip the tick box, the wizard stops with “To use the controller, you need to agree to TP-Link’s Terms of Use.” at the top of the page. Ticking it and pressing Next again is all it needs. A pop-up then asks you to join the User Experience Improvement Program; “No, thanks” is fine and changes nothing about how the gateway works.

Set the device account and adopt your cameras

Step 4 is where the Fusion Pro takes over the cameras plugged into it. The device account you type here becomes the username and password on every camera it adopts, and it’s also the login that RTSP and ONVIF clients use. If you plan to run Frigate or Home Assistant next to the gateway, use a real password you can find again, not Auto Generate:

Omada Fusion Pro web setup Set Device Account step with two Omada 8MP cameras found and selected
  1. 1Username
  2. 2Password
  3. 3Refresh
  4. 4Next
  1. Type a username in Username.
  2. Type a password in Password.
  3. If your cameras aren’t listed yet, press Refresh and give them a minute after power-on.
  4. Leave each camera ticked and press Next.

Both of our cameras appeared on the first scan in the web wizard. The Omada app had found none on its first scan the night before, and only listed them after a rescan 11 minutes later, so give a slow scan a second try before you go looking for cabling faults. The last screen sums everything up:

Omada Fusion Pro web setup Success screen with controller name, time zone, device account and WAN type

Note the line in the blue box: you can change the device account later under Settings > System Settings > Access Config > Device Account, and the wizard notes that adopted devices take that account as their login. Press Go to Dashboard. From the Internet Settings page to the dashboard took us about seven minutes, and half of that went on the failed TP-Link ID sign-in.

“General error.” in the Omada app

If you started in the Omada app over Bluetooth, this is the step where ours failed. Our app found the gateway, set up the WAN, created and activated a TP-Link ID and formatted the SSD, then stopped at Set Device Account with nothing but this:

Omada app showing General error. at the Set Device Account step of Fusion Pro setup

The message carries no code and retrying gave the same result. We think it is the same cloud failure as the TP-Link ID error above, since the app’s setup runs through the cloud account the gateway couldn’t bind. Two details may matter on your unit: our phone was on mobile data, not on the Fusion Pro’s LAN, and Omada’s own workaround for app setup trouble is to join the same local network and retry. The release note for Omada OS 4.0.1 also fixes Bluetooth setup timing out, so a gateway that ships on a newer build may never show this. Either way, you don’t need to factory reset anything: plug a laptop into a LAN port and run the web wizard, which starts fresh because the app never finished setup.

Format the SSD if it shows Unformatted

The gateway records to an NVMe SSD in its tray, and a new drive ships blank. In the app’s wizard, ours showed as Unformatted at 931 GB, and one tap on Format turned it to Normal with “The disk is ready for video recording.” and 930 GB of capacity, 14 GB of it already in use.

If you set up through the web, open the Guard app (the camera icon in the header), then Guard Config > Storage Management, and press Format if the disk isn’t marked Normal. Formatting wipes the drive, so do it before you have footage you care about.

Recording starts on its own once a camera is adopted and the disk is ready; you don’t have to switch it on. About seven minutes after the wizard finished, Guard counted 13 minutes of recordings across our two cameras: 2 GB of footage, next to 4 GB the system reserves. Loop recording was already on when we checked, so the oldest footage is overwritten when the disk fills.

Upgrade Omada OS with a local file

Check your firmware before you do anything else in the dashboard. Try Cloud Upgrade on the Omada OS card first. On our unit it answered “No new release.” on the Stable, RC and Beta channels while the shipped build was older than the first public one, most likely because its cloud link was broken. If Cloud Upgrade offers nothing newer than Omada’s download page lists, use a Local Upgrade with a file from that page:

Omada Fusion Pro OS and Applications page with the Omada OS menu open on Local Upgrade
  1. 1Settings
  2. 2Current Version
  3. 3â‹®
  4. 4Local Upgrade
  1. Open Settings, then OS & Applications.
  2. Compare the Current Version on the Omada OS card with the download page.
  3. Open the â‹® menu on the Omada OS card.
  4. Choose Local Upgrade, browse to the .bin file and press Update.

The files come from the Fusion Pro 2.5G PoE download page, one per build, each a .zip of about 1.27 GB with the .bin inside:

Omada support download page listing Fusion Pro 2.5G PoE firmware 4.0.2, 4.0.1 and 4.0.0 builds

Read each build’s release note before you pick one, because a release note can name a minimum starting build. The 4.0.1 note asks for at least 4.0.0 Build 20260914, which our shipped 20260910 build was older than. So we went in two hops, first to 20260914 and then straight to the newest build, whose note lists no minimum. We didn’t test a direct jump from an older build to the newest one, so if you’re older than 20260914, install that build first; it’s the path we know works.

Each upload took about two and a half minutes over the LAN and each reboot about four. One honest caveat: the Browse button never opened a file picker in our automated test browser, so we sent both files through the same upload call the dialog makes; in a normal browser you pick the file and press Update. The cameras dropped off during each reboot and came back on their own, and recording carried on without any help.

Update the camera firmware from Guard

Camera updates come through the Guard app, not through the download page. Open Guard, go to Devices, and look for an upward arrow next to a camera’s version number. Clicking it shows what the new build changes:

Omada Guard Devices page with the New Version 1.0.7 Build 260911 update prompt for an Omada 8MP camera

Press Update and wait for the “update succeeded” toast before you start the next camera. Each of ours took about two and a half minutes, reboot included. One small trap: the Update button ignores clicks while the prompt is still fading in, so if nothing happens, wait a second and click again.

Turn on Cloud Access if you need remote access

Cloud Access is what lets you manage the gateway and watch cameras from the Omada app away from home. You can skip it if you only manage the box on your own network, which is how ours runs. To turn it on, go to Settings > Cloud Access, flip the toggle, and enter your TP-Link ID in the Log In and Bind dialog.

“Device’s device secret not match” and “TP-Link Cloud Server is busy”

On our unit, binding failed with the same “Something went wrong” toast as the wizard, even on 4.0.2:

Omada Fusion Pro Cloud Access Log In and Bind dialog with the Something went wrong error

Behind the toast, the bind response in the browser’s developer tools read Device's device secret not match, and the cloud status check returned error -1500, “TP-Link Cloud Server is busy”. Neither firmware upgrade changed it, which points at this gateway’s record on Omada’s side rather than anything you can fix on the box.

If you see it too, keep running on the local account and contact Omada support with the gateway’s serial number; don’t factory reset the box unless support asks you to, since a reset wipes your setup.

Check that your setup is complete

Before you call it done, go through this list. Each item is something we checked on our own unit after setup:

  • You can log in at https://192.168.188.1 with your local account.
  • Omada OS on the OS & Applications page matches the newest build on the download page.
  • Every camera shows Connected in Guard > Devices, on the newest camera firmware.
  • Storage Management shows the SSD as Normal, with recording time growing.
  • You’ve saved the device account somewhere safe, because RTSP and ONVIF clients need it.

If all five hold, the gateway is ready for daily use. From here, you can pull the camera streams into Frigate or Home Assistant with the device account; our guide to running Omada cameras in Frigate and Home Assistant covers the stream URLs and the camera settings to change first. If you’re still weighing the platform, our Omada vs UniFi comparison and the UniFi Cloud Gateway roundup show where Fusion Pro sits against the UniFi gateways.

Keep reading

Free CCNA 200-301 Practice Questions with Answers Networking Free CCNA 200-301 Practice Questions with Answers Configure Samba File Share on Debian 13 / 12 Debian Configure Samba File Share on Debian 13 / 12 WireGuard VPN Setup: Ubuntu 26.04/24.04, Debian 13, Rocky 10 Debian WireGuard VPN Setup: Ubuntu 26.04/24.04, Debian 13, Rocky 10 Best Networking Books: TCP/IP, Routing and Troubleshooting Books Best Networking Books: TCP/IP, Routing and Troubleshooting Omada Fusion Pro Behind a Router: Port Forwarding for LAN Access Networking Omada Fusion Pro Behind a Router: Port Forwarding for LAN Access Nginx vs Apache vs Caddy vs HAProxy: Performance Benchmark (2026) Networking Nginx vs Apache vs Caddy vs HAProxy: Performance Benchmark (2026)

Leave a Comment

Press ESC to close