no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
30 Reply
Re:no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513
2020-06-30 13:27:19

ok, downgrade directly over OC200 Webinterface works like a charm. 

 

Thanks

Kindly Regards

Ronald

  1  
  1  
#22
Options
Re:no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513
2020-06-30 16:08:36

I have also manually downgraded all our 50 odd EAP225s back to previous firmware and the dynamic data has started displaying back correctly. The controller interface is also not offering the backward un-compatible firmware, which means it may have been pulled off the update servers.

 

Thanks to TpLink team for resolving this quickly.

  1  
  1  
#23
Options
Re:no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513
2020-07-01 16:11:57

Same issue here.

Also, no release notes.

I guess the release note is: "Breaks statics for software run controller".

 

I'm downgrading the firmware to 2.5 right now...

  0  
  0  
#24
Options
Re:no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513
2020-07-01 19:33:07

Sorry. Breaks statistics*

  0  
  0  
#25
Options
Re:no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513
2020-07-09 00:35:55

Now the tool shows another firmware version available: 2.7.0 Build 20200113 Rel. 38287

  0  
  0  
#26
Options
Re:no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513
2020-07-09 00:49:14

@LucianoR 

 

that is currently the firmware I had prioir to the update that broke it all

  0  
  0  
#27
Options
Re:no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513
2020-07-09 15:44:30

@rtrevino Sounds about right. I had downgraded to 2.5.0 because that was the available firmware on their website. 

 

I found very interesting that I'm using a firmware that is not available on their site, so I can really check release notes - because Omada controller tells me to check the release notes on the zip file, but the file is nowhere to be found and not available on the website. ¯\_(ツ)_/¯

  0  
  0  
#28
Options
Re:no clientes after update eap225 to 2.20.0 Build 20200422 Rel. 70513
2020-07-10 14:24:57

I just hit the same issue with the 245.  The 245 product page has a firmware from 7/6/20 that requires the new controller software and I didn't realize it before upgrading.  Reverted to the previous firmware and all is good.  Hopefully the controller software hits soon.

  1  
  1  
#29
Options
1.20.0 Build 20200422 Rel. 70543
2020-07-19 18:11:53

@rtrevino 

 

rtrevino wrote

 

Hello,

 

after upgrade to 2.20.0 Build 20200422 Rel. 70513 my 2 eap225 now they dont have any clients assosiated, I have tried rebooting the contorller, rebooting the AP and still no luck

 

 

thnks for your help!

 

  0  
  0  
#30
Options
1.20.0 Build 20200422 Rel. 70543
2020-07-20 02:42:35 - last edited 2020-07-20 03:11:27

I too accepted the offer to upgrade my EAP225 to the new firmware and saw that the 3.2.1 controller no longer saw the AP. I went to the website and saw a 4.1.5 controller and thought that might be the fix but to install it, I had to first uninstall 3.2.1. I have a backup so I went ahead with the uninstall and installed 4.1.5; still no joy. It might be related to the fact that the new controller wanted me to use a stronger password than the older one but who knows.

 

I thought I'd go back to 3.2.1 and then downgrade the firmware but the uninstall shortcut doesn't work 

 

Is there a manual way of downgrading the controller?

 

What is the safe way to then downgrade the AP firmware so that I can use the backup file to restore the network to its working state?

 

Thanks

 

P.S.: Controller runs on Windows 10. And at least the network still works even if it cannot be administered

  0  
  0  
#31
Options
Related Articles