This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.EAP225(EU) V5 & OMADA software controller 5.7.4
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi all,
i'm a brand new user of the Omada solution .
My HW part is made of ER605 V2 , TLSG2210-P as main switch , 1 EAP115 V4 , 1 EAP115V2 ( standalone ) , and last 5.7.4 Omada software controller running on ubuntu server .
Everything is running fine in this configuration.
Yesterday, i received a new EAP225(EU) V5 and it seems not to work properly when paired to the controller. In standalone mode , it works fine , i can see the SSID and connect without problems. If i pair the eap with the controller , nothing works , my networks are created in the controller but not seen , and eap is always deconnecting/reconnecting every 5 minutes to the controller .
I've tried others patch cables , direct POE power injector , but no way , always the same behaviour .
here is a log sample :
Could it be that this V5 version is "too young" for the controller and need an update ? ( no FW available on the support page for this version )
I will use it in autonomous mode for now but it would be really nice to have it integrated in the main system .
Regards.
Hello,
finally it's working ! 
The problem was linked to the second concern i've posted in post #2 about SNMP activation on the EAP225 V5 : if you try to activate on the EAP in standalone mode , when you save the config , the AP reboots and the config is not taken into account .
Global SNMP was activated on my controller so i turned it off and after that , i was able to adopt the EAP225 without any issue .
I also have an issue for that opened at Tplink France support , let's wait for a solution .
Hi all,
i've tried today with a fresh install of 5.7.4 controller under Win10 , and behaviour is exactly the same , AP is always connecting/provisionning/disconnecting in cycle .
Edit : another concern i faced this morning : as i'm using the AP in autonomous mode right now , i've tried to enable the SNMP function on this AP and everytime you click on save , the AP reboots , and SNMP config is not taken into account 
, even after a reset and config from scratch .
Ok , here are the tests made this morning :
Plug the AP into another switch port ( POE ) : same behaviour
Plug the AP into another switch port but with the supplied POE injector : same behaviour
So , i took another POE switch out of the main network, plug the AP on it , and just a computer with fresh install of the controller software under windows : it's working , AP is well adopted and configured , i can see after the wifi network .
After that, i decided to totally uninstall my main controller on my ubuntu server , install from scratch , and start the config process from zero : ER605 , SG2210P, EAP115 , and finally , the EAP 225 and then , troubles came back : same behaviour than before , the EAP225 is looping connected/configuring/heartbeat missing .
I don't understand what could be the problem 
Yes, it looks like the port is open, so that's not the problem.
it doesn't seem like the controller supports EAP225 v5, only v3 is in the supported device list, but strange it worked with windows ?? I think I would send an email to TP-Link support about this, there is probably something buggy here.
EDIT:
maybe I misunderstood a bit on the device list, it says and above versions, so then v5 should be supported
I will 
I have until end of January to return the product so i will see if there is a solution during that time .
BTW , i can confirm that on my other controller in windows , after erasing of the database and adapting only this EAP225 , it works fine .