@d0ugmac1 

Ok everything adopted and works well .

 I changed OC200 to Ip 192.168.1.XXX.. Everything works on that subnet 1.xxx. Once I create Vlan Interfaces and wireless Interface, The OC200 Controller becomes very unstable and starts shutting down switches. I get heartbeat and disconnected issues. The Vlans have not been activated. If I activate a vlan on 100 and set the profile to the correct Tagged port and Untagged port. Even setting the port assigment Loses internet all together Things go haywire. The controller disconnects itself from the network and lose all connectivity. I have to manually reboot the controlller to bring it back up. I NOT DOING SOMETHING RIGHT. i HAVE EVERYTHING WORKING ON THE SUBNET 1.XXX its the only way to have interent.

Any suggestions.

Im not convinced that I need to use this controller. Before adopting all switches and APs never missed a beat. Been in place for over a month before using controller

  @d0ugmac1 

Ok would it not be better to allow the Controller to handle all vlans and let Pfsense handle just DHCP ?? as router only

At this point probably need a little more detail about which device is connected to what.  The controller can build this Topology map for you graphically once devices are adopted, and you can turn on Labels, to get more detail like port numbers.  However, perhaps this following will be more immediately useful to you.

It looks like you have a number of interfaces defined on the Pfsense router.  Presumably these interfaces can be configured as Access or Trunk physical ports, the difference being that if a port is say an access port for VLAN 30, then it is a member of VLAN 30 and 30 is set as the PVID This is How I had it setup on Switch prior to Controller

(meaning any untagged traffic is treated as belonging to VLAN30 and will get an IP from the VLAN 30 subnet via its DHCP server). 

However, Omada works more with trunk ports, which means a single port on the router connects to a single port on the first downstream switch.  The router port MUST be configured with all necessary VLANs, ie all VLANs used by any device below the router (so, 1, 50,100,200 and maybe 30) and the PVID will be set to VLAN 1 meaning that 192.168.1.X subnet is untagged, and traffic on the all the other subnets is tagged appropriately.  The connection at the downstream switch will be configured automatically by the OC200 so that it is also a member of VLANs 1,50,100,200 and it's PVID is set to 1 (so again VLAN1 traffic is untagged).  It is CRITICAL that all ports servicing Omada controlled device downstream are also a member of VLAN1 (but the controller should take care of this automatically once the switches are adopted).

Now let's look at the case of a downstream AP which is configured with two SSIDs, one for IOT and one for Management.  This AP now needs access to subnets 192.168.1.x, 192.168.100.x and 192.168.200.x via VLANS 1, 100 and 200 respectively.  So the port the AP connects to is configured as a member of those 3 VLANs (1,100,200) and its PVID is again set to VLAN 1.

One thing to consider in all of this is that the trunk port on the Pfsense router needs to be able to deal with all the VLANs arriving from the master switch immediately below it.

  @d0ugmac1 

Ok I have reinstated the network without the Controller for now going to do some more research on Pfsense. I know it is a ME unstanding issue. But I'll will figure it out.

Thanks again Talk back soon  @d0ugmac1

  @d0ugmac1 

You are RIGHT!! I got so Frustrated (ALL ME) I hate when I miss something. I need to take a couple of days off from this and come back to it. Im gonna make it work with the controller. Hang in there with me so I can LEARN Brother. 

Be back on Wednesday to try again

Thaniks Again  @d0ugmac1

Big_12ms