@WilliamNL 

I assume you have a working WAN port and that you have your top level switch connected to port 5 (rightmost ethernet port) of the 7206.

I assume you have created the 5 LAN subnets as defined below...did you assign them VLANs or leave them all at VLAN1?

Have you created switch port profiles yet?

If you connect your laptop to the top level switch, what IP address is assigned (ie which LAN subnet is assigned by DHCP)?

Honestly, I'd be tempted to 'Forget' your 7206 and re-adopt it as this just sounds like it's a bit confused and see where you are at (especially if you adopted it before defining all your networks in the OC300)

  @WilliamNL 

Ok, I think it's as simple as the port profile ALL only accepts untagged traffic on 192.168.0.X/24.  YOu can see this if you go to Controller->Wired Networks->LAN->Profile then click the 'eye' for the ALL line.  Essentially every switch port you have right now is only working on 192.168.0.0/24.

To verify:

You will see that the Native network is LAN (in my case that's the 192.168.0.0/24 subnet) for the ALL profile

You will now want to make sure that the other 4 subnets you defined, ie the .50's, are listed in the Untagged Networks line in the All profile if you want devices on those subnets to interact with each other (multi-netted)

Down the road you can create profiles like Camera, which would use the Camera subnet as it's native network instead of LAN...then devices connected to that port and belonging to the correct .50's subnet don't have to have tags and will switched back to router with the appropriate 'Camera' tag where they can then interact with other subnets, if so permitted.

Clear as mud?

  @WilliamNL 

Ok, let's have a look at what your 7206 thinks it's routing table is, so can you go here in the Insight section (light bulb) of the controller

and post the Results of both the Gateway and Switch tables?  You should XX out your public IP for safety before posting.

  @WilliamNL 

OK, your Gateway setup looks identical to mine (I have 4 extra subnets for different SSIDs configured, much the same as your .50's) and the Gateway table matches.

Your switch table on the other hand is very confusing!  I have a couple of sites, one with only a single local subnet and the above (5 local subnets).  In both of my cases my Switch table looks like this:

Basically Switch to 0.0.0.0 is via the Router, and Switch to any other management VLAN IP goes via the switch (ie stays local).  Presumably you have a lot more switches in your setup, and your expanded table is mapping any 192.168.0.0/24 IP's to the local IP of that switch.  What's weird is that NONE of your switches have the 0.0.0.0 DESTINATION defined...which of those switches is actually physically attached to a Router LAN port?

For what it's worth, here's the corresponding table excerpt from the Gateway of the system for which I show the Switch table above, you'll see the 5 defined subnets.

  @WilliamNL 

So for fun and giggles...I happened to have a spare switch kicking around and I just plugged it in below the main switch I'd shown above, and lo two new Switch routing entries were added:

So you definitely have something funky in your WAN/LAN setup on your controller.

  @WilliamNL 

And if it helps, please check your subnet settings.  I have shown the LAN setup I have, but it's the same thing for the other 4 subnets.  You must make sure that your subnets get tagged to the router port feed downstream switches.  For instance if you have a .51 devices plugged into switch B which plugs into switch A which plugs into LAN2 on the router, then your .51 subnet needs to have LAN2 ticked.  If you don't tick 'auto gateway' make sure you know what your doing!

My management VLAN: