Omada Controller 4.3.5 does not find SG2008P switch
I have a basic setup, with Omada Controller 4.3.5 running on an Ubuntu Server 20.04 machine and two EAP225 Access Points, all three of which are connected to an SG2008P switch.
Switch IP is 192.168.10.31
EAP #1 IP is 192.168.10.35
EAP #2 IP is 192.168.10.36
Controller IP is 192.168.10.49
The controller finds and adopts the EAPs without issue, but never detects the Switch. I can ping the Switch from the Controller command line, and I can ping the Controller from the Network Diagnostics tab in the switch page. I have tried the switch on FW v1, and v1.0.1 and it doesn't make a difference. I have tried with "Cloud-Based Controller Management" both disabled and enabled in the Controller Settings Tab on the Switch. I'm not sure if this applies to a local Controller or just the cloud option so I tried both ways. When enabled I tried both with and without the Controller IP entered in the "Inform URL/IP Address:" box.
I noticed that the switch automatically adds port 29810 to the end of the IP so I captured traffic on the network on port 29810 and can observe both EAPs reach out to the controller on this port during bootup but no traffic at all from the switch. Is there any setting I am missing here? How do I get the switch to become available for adoption?
On a possibly related note, I am running several instances of Omada Controller v3, and I set the Mangement VLan for all my TP-Link devices. How can I do this with v4?