@xmtr34 

I do exactly the same thing and haven't had this issue.  I am using an OC200 (5.0.30 and now 5.1.7) as the Omada controller for meshing, what are you using?

Also, please make sure the following Site->Services settings are enabled:

  @xmtr34 

I always use DHCP to assign IPs for all my devices, but with Reserved IP's configured for my switches/APs so I can easily find them...so yes, my router is also 192.168.0.1, the switch .2 the APs begin in the .10's etc. :)  This allows all the magic auto-discovery/auto-provisioning bits of the Omada solution to do their thing.  I have tested and I can factory default a remote 225-outdoor and it will get auto discovered, and auto-reprovisioned back to it's proper config and IP once it boots back up.

  @xmtr34 I think these settings for each AP are more important, and I keep the fallback IPs in the same subnet for what it's worth.

  @xmtr34 

Ok so I re-read the thread and the one logical difference I see is that your remote SG2008P is managed as part of the Omada SDN solution.  In my case I have an old unmanaged Netgear POE switch powering the 225 and 235-Wall AP that is subtending it.  I also fixed the channel that my wired Mesh node is operating at (this shouldn't make a difference).  However, for an apples-to-apples comparison here, can I ask that you 'Forget' and default the 2008 at the remote site assuming you don't have VLANs configured between those 2 AP.  If that makes a difference, maybe you can connect them via some port isolation (ie link POE ports 3&4,untagged and plug your remote APs into those ports)

In my case, the Meshed 225 remote end shows up as wirelessly linked and the 235 shows up as a wired connection on the same switch port as my wired 225.

  @xmtr34 

What else are you doing with that remote 2008???  Why do you need VLANs configured on it, it should just be a glorified POE injector, think two POE injectors with a cross-over cable between their LAN ports, which will work too, and it preserves the VLANs of users on different SSIDs from either the outdoor or indoor AP.  

Even if you have local client devices plugged into the switch (I do, I have a VOIP adapter plugged into the remote non-Omada switch and it gets a management LAN IP, for now, my next iteration will have it plugged into a VLAN enabled port on the EAP235-wall, but that's another thread to come).

In short make sure you aren't tagging packets between the remote APs and it should work as intended (my mVLAN isn't tagged...if yours is, I may have to think more!)