@d0ugmac1 I got around to changing one of the EA225 Outdoor to ROOT. I also connected one of the remote EAP255 to it so that it has similar conditions as the ROOT EAP610.

The ROOT EAP225 dropped from the client list of the UDM within a few minutes just like the EAP610 does. 

  @d0ugmac1 I took the TPlink switch out and put a Yuanley YS 2080G-P 8 Port POE switch that I had on hand anyway. The same issue occurs with the 610 and 225 when wired to the switch and adopted by controller. So I think the switch itself has been ruled out.

I put one of the 225s on the new switch but in standalone mode. It has remained visible in the UDM Pro client list. So it appears to be something with the EAP being the Root EAP of a Mesh. The Root EAP, whether its the 610 or 225, always shows a small slither of activity whenever I first connect it or make changes that make it show back up in the client list again. So the report graph looks like this. All the little green sections are not traffic, but just when a condition changes, usually brought on by me changing settings. Also it shows no up / down packet info like the remote EAPs and the Standalone EAP do (see 2nd image)

Remote EAPs and Wired Standalone have this info and a solid green wired experience bar.

  @Hank21 thanks I just responded to them.  I have temporily switched hardware to test as replacement for the Omada system so I was not in the position to see if the problem persisted.  I have the Omada system back in place now and the EAP610 still only shows in the client list of the UDM-Pro immediately after a reboot of the EAP610, then it goes away and shows not activity. The network still works however so I don't think its that critical.