i've recently moved into the omada ecosystem using the self-hosted controller.

I own EAP620HD & EAP225 AP's, and over the weekend i've added a pair of SG2210P (v5) switches, with a SFP port LACP LAG group between them.

i've also a pair of Netgear switches (GS724T & GS108Ev3), which the SG2210P's are replacing the GS724T.

620HD was connected to GS724T, EAP225 remains untouched on the GS108Ev3. 620HD is now connected to one of the SG2210P switches.

AP's are in mesh with identical SSID's broadcasted. 4 SSID's on different vlans. my primary SSID is on vlan1, as is all management interfaces.

the problem i'm seeing is that when the 620HD is connected to the SG2210P switches, vlan1 SSID does not work unless i untick vlan in the omada SSID config.

This was not a requirement of the 620HD on the GS724T, and also breaks the vlan1 SSID on the EAP225. So as a workaround I've copied the wifi group. one with SSID vlan1 configured (for EAP225), the other without (for 620HD).

SG2210P port profile is set to 'all' for the 620HD interface.

I don't think I've a way to prove things more, but i also have other ports (servers) running with 'all' profile to trunk the vlans without issues so it does appear specific to having a device both with an omada management IP and access/edge service on that device, using the same vlan.

based on the above, i've come to the conclusion that there's something incorrect with my SG2210P configuration. I cannot see anything i can change that would help so it's either a well hidden/non-obvious setting, or theres a bug i've encountered