@Bignose21 

If you have already tried 'forgetting' them on the controller and they still won't re-Adopt, and they aren't broadcasting some 'TPLINKXXXXX' SSID (ie they factory defaulted somehow) then your shortest path to getting them back up and running is to reset them manually using the switch inside the ethernet cover.

Unlike the EAP110's which can be reset from the passive POE injector block, you have to physically access the EAP225's to reset. 

Let me tell you how 'happy' I was the (one) time I lost control of my wired EAP225...at -20'C

  @Bignose21 

Ah, you neglected to share the power bump info :).  Also, I do miss the UK, just haven't been back since Brexit.

Let me guess, you have all the APs in full AUTO mode?  If so, I think what you saw was a re-convergence problem as in AP's upstream in the mesh came back from the power bump on a different channel thereby isolating them.  They would have reset, come back, been Adopted...but the config file pushed down would still have their old back-haul channel in it, which would take them off-air again.  I engineer my 5Ghz back-haul channels for all my wired EAP225's, so that when the meshed units come back online, their default profiles will already be set to the correct channel, and they usually come back online in a minute or two.  Just fix the 5ghz radio channel at whatever it is now for your wired EAPs, instead of leaving it at auto and this shouldn't happen again.  Leave the meshed units on full AUTO so if they have to, they can re-converge via another wired node if there is a failure somewhere.