Business Community > WiFi > EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on May 6th, 2024)- [Thread Closed]
< WiFi

Early Access EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on May 6th, 2024)- [Thread Closed]

1111213...

Early Access EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on May 6th, 2024)- [Thread Closed]

275 Reply
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 02:22:39 - last edited 2023-09-07 04:41:35

  @jg1212 

 

ok i have three EAP610's and two EAP225's on the network. Ive updated two of the 610's so far. ill update the third shortly. i dont think theres any updated firmware for the EAP225's yet that allow lock to AP.

 

EDIT: updated all of the EAP610's to 1.1.3, now my wireless printer wont connect at all even though it sees all the access points and the network SSID but shows its disconnected and gives an error when i try to connect it. rolled back to 1.0.2 for now and its still giving me issues. what the heck?

 

EDIT 2: it appears the update changed my network security to WPA2/WPA3 and kept the old Canon printer from recognizing the network. i switched it back to WPA2 and it connected. either way, 1.1.3 seemed to not have lock to AP working very well as the devices i had set to lock, kept connecting to other AP's. i had to keep reconnecting them to get them to swap over.

  0  
  0  
#115
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 07:03:40

  @dictoresno I've been on 1.1.3 since the weekend, and so far it's all been perfectly smooth. I don't use the Lock to AP feature though. PPSK was why I upgraded.

  1  
  1  
#117
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 07:28:30

  @EyeBrowse I have the eap 650 and all of them upgraded to the beta version

 

ive enable locked to app for a few devices but some devices will hop to the other AP.

but they can do that because they are locked 

now I get a lot of messages sometimes in my log that acces is blocked , see image is that right ? So yes how can I solve that or hide that messages ? 

  0  
  0  
#118
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 07:53:17

Hello @jg1212,

 

jg1212 wrote

 @Fae 

One of my EAP610 V2 APs was received with firmware 1.1.1.  I tryied updating it to Beta 1.1.3 but it keeps failing saying that the upgrade file is invalid.  Do you know what the issue could be? My other two APs upgraded from 1.0.2 to 1.1.3 just fine. 

The EAP610 came from Amazon with this firmware a couple days ago.  

Here is the full model and firmware build:

Model:   EAP610(US) v2.0

Firmware Version:   1.1.1 Build 20230524 Rel. 74262

 

The 1.1.1 firmware is a newer firmware than the 1.0.2 firmware, which has changed the default port used for firmware upgrade.

To be specific, the 1.1.1 firmware use HTTPS Port for Controller Management during the firmware upgrade. If you use Omada Software Controller v5, the default port is TCP 8043, for OC200/OC300 with built-in Controller v5, the default port is TCP 443.

 

To fix the issue, you may check your firewall settings and confirm the required port for firmware upgrade is open.

If it doesn't help, you may forget the EAP610 V1 with 1.1.1 firmware, and try to upgrade the firmware in Standalone mode.

 

Please feel free to let me know if you need further assistance. We look forward to your update.

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  1  
  1  
#119
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 08:06:58

Hello @dictoresno,

 

dictoresno wrote

  @jg1212 

 

i updated one of my access points to 1.1.3 and even though theres a device in the same room with it and its set up to lock to that AP, it refuses to connect to it. this is the same issue i was having before. it appears to be favoring the one AP i didnt update of the three. do all the AP's on the network need to be lock capable for them to work right?

 

How about if you disable the Lock to AP feature on the client first, then enable it to lock to the target AP after the client is connected properly?

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#120
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 08:14:01

  @Fae 

 

I am going to give that a try. A few devices that I reconnected seemed to stay on the correct one. I figured that if you set the lock, the device should jump on its own but I guess it doesn't. I'll try again in a few days and see what happens. 

  0  
  0  
#121
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 08:19:31

Hello @Mariomark1541,

 

Mariomark1541 wrote

now I get a lot of messages sometimes in my log that acces is blocked , see image is that right ? So yes how can I solve that or hide that messages ? 

 

If you don't want to receive the wireless clients failed to connect messages, please access your Controller via browser and navigate to Logs > Notifications > Client, disable all notification on "Client Connection Failed (Wireless)".

 

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#122
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 09:20:46

  @Fae okay but it is correct so make sure that I get this message when I pin devices to a certain access point.
why do devices still try to connect to a different access point?

  0  
  0  
#123
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 11:11:07

The whole idea of "lock to AP" is at best a dream, but more likely a nightmare, especially for TP-Link's support staff.  It's simply impossible to guarantee ANY client device always and only ever connects to a specific AP unless every AP has a unique SSID....PERIOD!  With wifi, the client makes the decission which AP to attempt to connect to, when to roam, etc...that's how wifi works, written into the standards.  While I appreciate TP-Link's creativity trying to develop a feature to bring a level of control to the situation, it's simply not going to be reliable, particularly for the type of clients it's generally intended to be used for....stationary IoT devices.  It has a very good chance of reliability with modern clients that fully implement 802.11r/k/v standards such as smart phones, tablets, and laptops.  However, the typical IoT device like smart switches/outlets, printers, etc are built on the cheap, usually with 2.4GHz only, and antiquated support of wifi standards.

 

While it's a clever feature that TP-Link is trying to make work, AP pinning/locking is going to be frustrating for most users and TP-Links support staff fielding support cases when it's not "working".  It's simple, if it's not working for you, it's the client device's fault, not the Omada system.

  3  
  3  
#124
Options
Re:EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Aug 31st, 2023)
2023-09-07 12:54:34 - last edited 2023-09-07 12:55:24

Fae wrote

Hello @jg1212,

 

jg1212 wrote

 @Fae 

One of my EAP610 V2 APs was received with firmware 1.1.1.  I tryied updating it to Beta 1.1.3 but it keeps failing saying that the upgrade file is invalid.  Do you know what the issue could be? My other two APs upgraded from 1.0.2 to 1.1.3 just fine. 

The EAP610 came from Amazon with this firmware a couple days ago.  

Here is the full model and firmware build:

Model:   EAP610(US) v2.0

Firmware Version:   1.1.1 Build 20230524 Rel. 74262

 

The 1.1.1 firmware is a newer firmware than the 1.0.2 firmware, which has changed the default port used for firmware upgrade.

To be specific, the 1.1.1 firmware use HTTPS Port for Controller Management during the firmware upgrade. If you use Omada Software Controller v5, the default port is TCP 8043, for OC200/OC300 with built-in Controller v5, the default port is TCP 443.

 

To fix the issue, you may check your firewall settings and confirm the required port for firmware upgrade is open.

If it doesn't help, you may forget the EAP610 V1 with 1.1.1 firmware, and try to upgrade the firmware in Standalone mode.

 

Please feel free to let me know if you need further assistance. We look forward to your update.

 

@Fae 

Thank you for the advice.  I forgot the EAP610 "V2" with 1.1.1 firmware and logged in as standalone mode and the firmware updated to 1.1.3 just fine.  This may be a re-occurring question if a lot of these devices shipped with 1.1.1.  You may want to have the controller team add some code to check for which port is being used for firmware upgrades.

 

  0  
  0  
#125
Options
1111213...

Tags

Firmware Update Official
Related Articles
 EAP Beta Firmware for Omada SDN Controller v5.8 (Released on Sep 26th, 2023)-[Thread Closed]
1871 0
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
31936 9
 EAP firmware for old Omada Controller v3.2.x
2963 2
 EAP620HD V1_1.1.0 Beta Firmware (Fully Adapted to Omada Controller v5.5)
3009 4
 Firmware Update EAP 's in SDN cloud controller
654 0
Omada Controller v5.9 for OC200/OC300 Release Date
5255 12
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.