Luckily, I’m already on most, if not all of your sites 
and even better news, it’s fixed.
I’m not sure the how or the why, but your L3 interface (the one going to the S8-PoE) was set for untagged VLAN 2 which had the subnet of 192.168.0.0/24. So after I corrected that, the switch came up shortly after on the 192.168.101.0/24 subnet. The AP didn’t refresh so I just power cycled that from the switch and when it booted back up, it too had the proper subnet.
I suspect this is a classic chicken/egg problem. The Route10 boots with a default subnet and default DHCP scope. Clients get that scope and they’re stuck there until it’s time to renew their DHCP lease. We’re having discussions about improving this, the leading thought right now is to allow the ability to set the LAN subnet at the initial configuration point on the Route10’s web interface.