@forrest Thanks for the reply and appreciate you testing.  Yes, I'm about 20 feet from the AP so signal strength is very strong, I have a second AP (245v1) on the second floor both managed by the controller.  I performed a manual upgrade via the controller (manual as in I had to download the file and then point the controller to it) as the controller was reporting the firmware was already up-to-date (with v2.2).  When I get some time I'll retest.  Cheers.

PS: should have mentioned iphone 7 and ipad 5th gen...if that matters to anyone.

@shberge I do have a VLAN on one SSID.  On the SSID page I have the VLAN ID entered (10), how would this change with the new firmware?  I wasn't trying to connect to that VLAN though, it's only used for IoT devices.  I'm not fully understanding what you changed to make it work with the new f/w.  Thanks!

@shberge Oh, now I understand.  In my case, VLAN 10 is tagged and my default (primary LAN SSID) would be VLAN 1 and is untagged (configured like your VID 300).  So this is a different setup and issue I seem to have (still need to retest at some point).  Thanks for the clarification. 

@shberge Reinstalled 2.3 this morning, problem was I had the switch configured as tagged default VLAN instead of untagged.  It was correct on the AP, but the switch was wrong but still worked with 2.2...didn't occur to me to check this (until you posted about the VLAN).  Switching that to untagged allowed the devices to connect successfully to the network (they were apparently connecting to the AP...just no further connectivity).  Thanks again for the help.  Cheers.  :)

@shberge That makes sense, didn't bother trying that once I changed the switch setting.  My 245v1 continues fine working like the v3 on the 2.2 firmware; that's probably why I set up the v3 as I did.  Wonder if we'll ever see an update for that v1...thinking not.  I appreciate the clarification.