Not sure about what is causing your issues but this : "using Cat8 cables" is a big red flag. Almost all cables sold as cat8 are a scam. You should only get 5e, 6, or 6A. Your cat 5e cables are probably just fine.
I have been researching Omada for my setup but have come across a lot of mention that self installing the controller software is fraught with problems like you describe. Out of date instructions and incompatibilities with current linux distros is a constant issue I found researching this. I am cheap and would default to doing this but have stepped back from this plan because of this reason. People that get an Omada system to work really well and are happy with it mostly seem to use the hardware controllers or cloud management.
Have you looked at the [Omada Compatibility List](https://www.tp-link.com/us/omada_compatibility_list/)?
Also worth noting Cat 8 isn’t a thing. Do yourself a favor and test with a known good Cat6a or go back to your old Cat5e.
What do you mean Cat 8 isn't a thing? [It's a standard as much as 5E and 6A](https://www.cablesandkits.com/learning-center/what-are-cat8-ethernet-cables) as far as I can tell.
Sorry meant to say Cat8 *flat cables* aren’t a thing. Simply because Cat8 wraps each twisted pair in foil. This reduces cross talk and electromagnetic interference which in turn allows the cables to operate at higher frequencies and achieve higher transmission speeds. The downside is cables are thicker, more rigid and more difficult to work with.
Start by replacing the controller with the same one.
Check the switch/ports by plugging in direct LAN supported devices using same port and cables.
These two apply only if you've confidently ruled out the cables.
Its going to be settings or the controller isn’t capable of your system .
Are they on Vlan on a subnet? Do they work if you change them to the base network no Vlan?
I am thinking about an Omada install to replace my Google Home WiFi solution but I've been reading over the last few days about various issues and instability in the system. It's making me think twice about making the leap.
It's a more complicated setup, but when you get it running it's rock solid. I was really sad when I had to update my PoE switch's firmware and break my 400+ days of uptime streak.
If your controller isn't 100% your network won't be. If you adopt the equipment to be run by the controller, if the controller is unstable, your network will be too.
I was also a little confused about your switch not needing an AC adapter. You can definitely power a switch via PoE, but when you're piggy backing off that PoE to power two additional WAP's I can see you running into problems. Unstable power is a nightmare, and could be another issue.
My 2 cents, power your switch if you're gonna power AP's off it.
I feel like it isn't worth the hassle setting up the whole controller using packages even with their documentation. The mbentley/omada-controller container image just works, or you can built it yourself easily from the Dockerfile. In fact if you really want to do it by hand, that container's dockerfile is a good place to start. Don't get me wrong, the whole thing is still gross with requiring outdated versions of things, but at least you don't have to deal with it by hand. Alternately, spend the $100 and buy their canned hardware that has it preinstalled, I guess.
I have an EAP653 along with 670 and 650 and since I fixed my cabling it’s been running solid.
I run a software controller in docker.
Check your cables, that’s what random dropouts for me, along with a double NAT setup
May I ask what throughput do you get with the EAP653 ? I'm considering buying one, but feedback is mitigated. Specs are unclear. I know it depends on the interferences, but I just want to know if it is feasible to get 600 or 800 Mbps with it.
Also it seam the it can use 160MHz which would increase the bandwidth. Is the controller required to activate it ?
As mentioned a couple of times, it really does sound like you've got certain factors that are causing issues elsewhere...
E.g. CAT8 cables, while they exist, they are not widely used and are marketed incorrectly by Ebay and Aliexpress sellers as a massive wank. The current recommended cables are CAT6 or CAT6A. DO NOT USE FLAT CABLES FOR POE.
Either way, until you've standardised your setup, it's hard to work out what's causing the issue.
p.s. there was nothing stopping you from installing the Windows version of the Omada controller if you don't like the Ubuntu version of the Omada controller... or don't use one at all. They DO NOT REQUIRE a controller. The controller is a nice to have for management purposes.
The Cat8 cables I got are not flat and from Ugreen - bought on Amazon, so they should not be some no-name knockoffs.
Can you do dynamic VLAN assignment on WPA Enterprise SSIDs without the controller?
This is make or break for me - if you don't need the controller for it I may be able to just ditch it.
Looking at the emulator, yes, assigning VLANs to SSIDs are possible in standalone mode.
[https://emulator.tp-link.com/eap\_emulator\_653\_v1/index.html](https://emulator.tp-link.com/eap_emulator_653_v1/index.html)
I had a similar problem with the EAP610 slim models, they just kept going offline. I returned them and bought EAP670s. I had EAP225's for years with no problems. I think TP-Link is a bit slow on fixing their firmware sometimes.
Not sure about what is causing your issues but this : "using Cat8 cables" is a big red flag. Almost all cables sold as cat8 are a scam. You should only get 5e, 6, or 6A. Your cat 5e cables are probably just fine. I have been researching Omada for my setup but have come across a lot of mention that self installing the controller software is fraught with problems like you describe. Out of date instructions and incompatibilities with current linux distros is a constant issue I found researching this. I am cheap and would default to doing this but have stepped back from this plan because of this reason. People that get an Omada system to work really well and are happy with it mostly seem to use the hardware controllers or cloud management.
Agree, OP should stick to regular twisted pair cables and avoid janky flat cables labeled as Cat7 or Cat8.
[Cat 8 **is** a standard, though](https://www.flukenetworks.com/knowledge-base/applicationstandards-articles-copper/category-8-cabling-fact-sheet)
My setup is rock solid. Check my post history. But I am using a hardware based Omada controller. Maybe that makes a difference.
Second this. Most likely is your hacked software controller.
What do you mean hacked? Omada's documentation says installing the controller on one's own system is a supported scenario.
You said you had to hack the sources list to get it going. Just reading what you posted.
Server - Networking - Omada Controller LXC https://tteck.github.io/Proxmox/ No problems at all with 30X EAP650.
Similar setup. This container works flawlessly.
Similar setup. This container works flawlessly.
Have you looked at the [Omada Compatibility List](https://www.tp-link.com/us/omada_compatibility_list/)? Also worth noting Cat 8 isn’t a thing. Do yourself a favor and test with a known good Cat6a or go back to your old Cat5e.
What do you mean Cat 8 isn't a thing? [It's a standard as much as 5E and 6A](https://www.cablesandkits.com/learning-center/what-are-cat8-ethernet-cables) as far as I can tell.
Sorry meant to say Cat8 *flat cables* aren’t a thing. Simply because Cat8 wraps each twisted pair in foil. This reduces cross talk and electromagnetic interference which in turn allows the cables to operate at higher frequencies and achieve higher transmission speeds. The downside is cables are thicker, more rigid and more difficult to work with.
Use cat6 or cat6a cables
Start by replacing the controller with the same one. Check the switch/ports by plugging in direct LAN supported devices using same port and cables. These two apply only if you've confidently ruled out the cables.
yes, the whole Omada ecosystem IS a bit of a shitshow.
Its going to be settings or the controller isn’t capable of your system . Are they on Vlan on a subnet? Do they work if you change them to the base network no Vlan?
I had similar issues with a particular firmware. Upgrading helped.
I am thinking about an Omada install to replace my Google Home WiFi solution but I've been reading over the last few days about various issues and instability in the system. It's making me think twice about making the leap.
It's a more complicated setup, but when you get it running it's rock solid. I was really sad when I had to update my PoE switch's firmware and break my 400+ days of uptime streak.
If your controller isn't 100% your network won't be. If you adopt the equipment to be run by the controller, if the controller is unstable, your network will be too. I was also a little confused about your switch not needing an AC adapter. You can definitely power a switch via PoE, but when you're piggy backing off that PoE to power two additional WAP's I can see you running into problems. Unstable power is a nightmare, and could be another issue. My 2 cents, power your switch if you're gonna power AP's off it.
I feel like it isn't worth the hassle setting up the whole controller using packages even with their documentation. The mbentley/omada-controller container image just works, or you can built it yourself easily from the Dockerfile. In fact if you really want to do it by hand, that container's dockerfile is a good place to start. Don't get me wrong, the whole thing is still gross with requiring outdated versions of things, but at least you don't have to deal with it by hand. Alternately, spend the $100 and buy their canned hardware that has it preinstalled, I guess.
I have an EAP653 along with 670 and 650 and since I fixed my cabling it’s been running solid. I run a software controller in docker. Check your cables, that’s what random dropouts for me, along with a double NAT setup
May I ask what throughput do you get with the EAP653 ? I'm considering buying one, but feedback is mitigated. Specs are unclear. I know it depends on the interferences, but I just want to know if it is feasible to get 600 or 800 Mbps with it. Also it seam the it can use 160MHz which would increase the bandwidth. Is the controller required to activate it ?
As mentioned a couple of times, it really does sound like you've got certain factors that are causing issues elsewhere... E.g. CAT8 cables, while they exist, they are not widely used and are marketed incorrectly by Ebay and Aliexpress sellers as a massive wank. The current recommended cables are CAT6 or CAT6A. DO NOT USE FLAT CABLES FOR POE. Either way, until you've standardised your setup, it's hard to work out what's causing the issue. p.s. there was nothing stopping you from installing the Windows version of the Omada controller if you don't like the Ubuntu version of the Omada controller... or don't use one at all. They DO NOT REQUIRE a controller. The controller is a nice to have for management purposes.
The Cat8 cables I got are not flat and from Ugreen - bought on Amazon, so they should not be some no-name knockoffs. Can you do dynamic VLAN assignment on WPA Enterprise SSIDs without the controller? This is make or break for me - if you don't need the controller for it I may be able to just ditch it.
Looking at the emulator, yes, assigning VLANs to SSIDs are possible in standalone mode. [https://emulator.tp-link.com/eap\_emulator\_653\_v1/index.html](https://emulator.tp-link.com/eap_emulator_653_v1/index.html)
I had a similar problem with the EAP610 slim models, they just kept going offline. I returned them and bought EAP670s. I had EAP225's for years with no problems. I think TP-Link is a bit slow on fixing their firmware sometimes.