Current connection issues (problems with setup)
Current connection issues (problems with setup)
Earlier I was inquiring about coverage options and what equipment to purchase. Now I’ve acquired everything. The configuration looks like this: Telus Fibre modem → ER605 router → TL-SG1008P unmanaged switch (2 EAP620HD access points). The PC connects via the switch, not the router, as specified in the setup instructions for all devices. I’ve installed the latest Omada Controller version (V5.9.31) and completed a quick setup, but no devices appear to show up. For some reason, the software isn’t performing the expected actions. I thought any switch could work since it’s from an unknown vendor, and some YouTubers share their setups with routers/APs. Could my switch not being Omada-compatible be causing this issue? When I connect to the router directly, it assigns DHCP client names and IPs to the APs. Anyone with experience could help me troubleshoot.
Verify that the EAPs are receiving power and linked to the appropriate POE+ ports on the switch. Consider employing the EAP Discovery Utility to share the Controller Host's IP with the EAPs.
My router has given the APs DHCP client IDs, and I can reach them from my PC, but they aren’t showing up in the discovery tool or Omada Controller software. My PC gets assigned 0.100, while the APs are 101 and 102. It seems they’re powered on and connected correctly. They run on PoE only, so giving them extra power might help, though that wasn’t the original plan. I can manually configure each AP using its address. The whole setup doesn’t appear to function as expected—none of the devices meant for discovery show up. I’ve taken the topology map from TP-Link, but it’s not resolving the issue. I’m unsure what else I should try. Also, the switch support mentioned refers to a non-Omada-specific switch.
You're still puzzled about what's not functioning correctly. Routers don't display switches unless they're managed switches. This suggests the TPLink control software might not be recognizing the APs. Since the APs have IP addresses and can be pinged, the problem likely lies elsewhere. You haven't used TPLink before, so it's unclear what should appear in the discovered devices section. Try accessing the AP directly via its IP address—does it show a web interface for configuration? Or can you input that IP into the search bar under discovered devices? It might be checking for firmware mismatches or needing updates on either the controller or the APs. What you're certain of is that unmanaged switches are invisible to routers, which shouldn't affect this issue.
Have you checked the IP addresses for the EAPs in the Discovery Tool? Omada functions similarly to UniFi in this regard, though it doesn’t use switches. The user mentioned they’re not using one because it’s unnecessary. It’s a PoE switch, which aligns with their experience with UniFi as well. Apparently, EAPs can enter standalone mode if you first log into them via their LAN IP, rendering them invisible to the Omada system. Give them another try and let them reconnect to the Controller.
I've noticed that entering each AP would launch it in standalone mode, which is why I've reset them several times to ensure they're working correctly. The only step I haven't taken is updating the firmware. Given the numerous versions of the Controller software and different firmware available for the router and APs, it seems possible there could be a mismatch. I plan to proceed with updating the firmware and retrying everything.
I've refreshed the firmware on all my gadgets. Everything has been restarted yet they remain invisible in my controller. Could there be a subnet configuration issue I overlooked or something misconfigured? It looks like everything is factory reset and powered on. My line from the modem connects to the router, which is linked to port 8 (the leftmost port) of the switch. My PC is connected nearby, and the two APs are on ports 1 and 2, both PoE enabled. Through my research, I thought everything should appear correctly, but it isn't. It seems there might be a small oversight I missed. My PC functions normally, and when I connect to the APs using my phone, browsing works as expected—though the connections are currently unsecured.
Your router is showing the AP's IP addresses (like .101 and .102), and since you can connect through them, they're reaching the network. The problem lies in applying them to your Omada controller. You might need to input either the MAC address or the local IP of the AP during the device search. Regarding the 'Batch Setting' button, it likely directs you to a configuration menu. Installing TP Link mesh networks has left me wondering about potential software issues or incomplete implementations. Although they're budget-friendly, many releases seem to have unstable software, making setup frustrating. I've spent considerable time troubleshooting various Deco products at homes.
The Discovery Utility isn't detecting anything, even when searching by MAC addresses or IPs. The Batch Settings only prompt to "Select at least one device." This doesn’t make much sense. Perhaps it’s best to spend $110 on a hardware controller, as others have reported similar problems. It’s frustrating having to pay extra just to get things working as expected. I still suspect there might be something missing. Likely it’s minor—otherwise it would be obvious. EDIT: It seems my PC is acting as the controller rather than being a separate device, which could be causing the issue. Maybe I should look into setting up my Raspberry Pi instead. I’m even more unfamiliar with this setup and expect some challenges along the way.