I bought into the Omada setup with several devices for my home office which also includes my shops. I did a bunch of research but now that I've actually obtained everything I'm a bit more confused.

I bought:

• OC200 Omada controller (that works fine, have it powered via PoE) 
• TL-R605 router
• TL-SG3428 24 port managed switch (with four SFP slots)
• TL-SG2210MP 8 port PoE switch (with two SFP slots)
• 2X EAP-235 wall access points
• 2X EAP-225 ceiling access points
• EAP-225 outdoor access point

The intention was to replace my aging wi-fi and infrastructure setup with this and have full control. The router, two switches and Omada controller are all in my data closet; the two ceiling units will be installed in my house, the two wall units in my two shops on my property and the outdoor unit on one of the eaves of my house. (I have a LOT of IoT devices.)

What I wanted to do was move from a 192.168.x.x to a 10.x.x.x ip schema with two VLANS - one for my own computers/tablets/TV's and one for all my IoT devices (I have quite a few of them and will be expanding in the future.) I was hoping the SDN would simplify this for me. Create three (yes, three) SSID's - one for 5GHz devices, one for 2.4GHz devices and one for 2.4GHz IoT devices. Obviously the IoT would be separated from the other network completely, with only access to the internet itself. I wanted to keep the 5GHz SSID separate because I currently have a (not very reliable) mesh system that "auto negotiates" between the two bands and I can't tell which one a device is running on. I'd like to make that decision myself. What I DO want is for these EAP's to all have the same SSID's so that I can move seamlessly between them with my tablets/laptops/phones (my desktops and TV's/etc. are all hardwired.)

Currently everything is connected in a segregated manner (no internet connection at the moment as I am still using my existing infrastructure as to avoid disruption of service.)  I have two of the SFP slots on the 3428 connected to the two SFP slots on the 2210 (wanted to do link aggregation to get more throughput) and all the wireless AP's are connected to the 2210 for power and ethernet. The OC200 is also connected here as well. The R605 is connected to the 3428 but I wasn't sure there was much point in connecting the other two SFP slots to it (as it will just be my internet router/firewall when its all said and done.) My internet is a cable modem and currently running as the router/firewall itself, but can be switched into bridge mode (which I will do once I get this network figured out.)

That being said I originally tried running the Omada controller in Docker on my QNAP NAS - which while it worked fine, I wasn't sure if it was adopting properly and in between stints I flat out forgot the password and just plain gave up on it, breaking down and getting the OC200. The real trouble was when I got in, and found that most of the equipment had to have the firmware updated to work with the OC200 - so I did that (a major pain) and now none of the devices seem to want to adopt outside of the two switches. 

I have several questions:

• Do I need to go in and change the admin password on the devices that don't want to adopt to the one in the Omada controller?
• Do I have things connected right, and/or is there a particular sequence to how I should adopt these devices? I suspect I just need to find the device password in the OC200 and make it match on the EAP's - I have the 3428 and 2210 adopted fine so far. I don't remember if I have the R605 adopted just yet.
• Do I need to connect just one ethernet cable to the R605>3428? Is having two connections confusing things? (Again, I have the R605 connected to the 3428 via SFP ethernet adapters.)
• Can I move the whole system from a 192.168.x.x environment that it defaults to, to a 10.x.x.x environment? (Will have two VLAN's, again, one being 10.x.x.x and the other being 10.y.y.x) 
• Will I need to use two interfaces on the R605 for the two VLAN's?
• Can I forward the DHCP requests on the IoT VLAN to the other VLAN so I only need one DHCP server? (I want to use Pi-Hole as an overall DNS server and be able to manage it from a single pane of glass rather than have to have two separate DNS servers, or worse - just route the IoT requests straight to the internet, giving me no visbility. Also wanting to have more control over DHCP where I can add options like an NTP server so everything is in sync.)

Any thoughts or ideas are greatly appreciated! Just a little guidance - most everything here is wired that can be to avoid any bandwidth hogs. I also have several laptops (and an MS Surface) to access the OC200 directly with, so that isn't an issue.