@Bug_do_Ti 

it's good you got it working but what you say doesn't make sense, I've never used default ip on any of the networks I manage, reason #1 is that if I do, I immediately rule out vpn between the sites, so for the last 35 years that I have been dealing with networks, I make sure that everyone gets unique networks on the lan, when it comes to your problem, I have several networks with ER605 and none of them have standard ip, in these networks there is also EAP225 as with you. all work perfectly. so that it started to work for you when you used the standard IP on the LAN is probably more random than a bug. but anyway good that everything works for you.

  @MR.S  It's simple to test, change a default IP to 10.1.1.1/24 and create 3 more VLANS with the EAPs225. After that, do the tests.

I know that theoretically there is no problem, but I have already identified this error twice. So, I no longer change the default IP to the 10.1.1.1/24 range. But I appreciate your comment.

  @Bug_do_Ti 

I don't have the opportunity to test this, but you may be right, I have never tested 10.1.1.1/24, so you may have hit on an ip range that is problematic. it will be interesting to hear what TP-Link has to say on the matter. I'm following this thread :-)

  @Clive_A 

Thank you very much for your reply, I'm going to close this topic and create another one, it really has nothing to do with the 10.x.x.x network it's another problem that's keeping me up at night

Problem not discovered yet