@darksmile79 

Hey

I see multiple clients faied to connect to AP due to "WPA Authentication times out/failed".

This is simply a device that is out of range / too weak a signal to establish a conenction / or gone offline and therefore failed to complete the connection successfully.  You will get these, its not unexpected.

In terms of the DHCP, if you are not getting a DHCP its not the Access Point, likely your router that is the issue.   Especially if you can manually set a DHCP and it works.   I would check your router first, make sure the DHCP scope is large enough to cover you devices.   DHCP is not anything to do with the Access Point

  @Philbert I think the "WPA Authentication times out/failed" might be an error that is indicative of the overall issue, whatever that might be.  I have the same thing happen on an EAP670 on the latest firmware.  Devices start to be unable to connect, it seems predominantly to 2.4GHz channels.  Rebooting the AP fixes it for a little bit, maybe a day or two.  Completely factory defaulting and re-adding it seems to fix it for longer often a month or two.  Every time I can tell it is starting to be a widespread outage and not just a random single device because the logs will be full of the "WPA Authentication times out/failed" events for a bunch of devices.  And this is for things like, TVs, chromecasts, my robot vacuum base station, my bed.  Stuff that isn't moving around.  So I will forget the AP and let if factory reset and then re-adopt it to kick the issue down the line for another month or two.

I will then have zero of the "WPA Authentication times out/failed" events for a month or two until I start noticing stuff not connecting again and I check the logs and the errors are back starting when the wireless connectivity issues started.  No new devices added, no changes to the network.  In my case, my pihole is acting as a DHCP server separate from my router and has plenty of room in the ip pool.  And if it was an issue with either the router or DHCP server then factory resetting the AP would not fix the issue.

Maybe this guys issue is different, but it sounds like the exact same one I've been dealing with for the last 6 months or so.  No clue what the solution is though, hence why I search for anyone running into the same issue every month or two in case someone has managed to fix it so... if anyone has any idea's I'm up to try them.