We have 2 cases of 2 different Omada controllers that fail to adopt EAP225 v3. They constantly stay in status: Adopting but never get adopted.

EAP Version: 5.1.1
Omada SDN Controller Version: 5.12.9
Omada Controller Model: OC200 v2.0
Omada Controller Firmware Version: 2.11.3

I have searched for information about similar cases and I have found that with EAP225 version 5.0.5 something similar happened and it was because the communication ports between Omada Controller and EAP were changed, but in our case they are all open and belong to the same network.

Can you please help us?