Hi,

1. I was trying to use the locate feature but it doesn't seem to work.

Do you mean that you want to locate the AP in Omada Controller, but you failed? What's the version of your Omada Controller? We optimize the AP Locate feature in the version of Controller 3.1.4. When you click Locate button, the led of the EAP will flash 10 minutes in default. You can also use Omada APP to Locate the AP, but please use the version of 2.1.4 or above.

2. Additionally, the EAP turns green even when it does not have network connectivity.

For this, the led of the EAP will be green when it is powered normally; it is not related to the network connectivity.

3. Lastly, It would be a great feature if the AP's light changed color (blue) when clients are connected.

Now we can see the client list in Omada Controller, could you please tell us why you want such a function?

1. I was trying to use the locate feature but it doesn't seem to work.

Do you mean that you want to locate the AP in Omada Controller, but you failed? What's the version of your Omada Controller? We optimize the AP Locate feature in the version of Controller 3.1.4. When you click Locate button, the led of the EAP will flash 10 minutes in default. You can also use Omada APP to Locate the AP, but please use the version of 2.1.4 or above.

When I click locate, the AP's LED does not flash, just remains solid green. I'm running the latest WIndows version of the controller and have the latest AP firmware.

2. Additionally, the EAP turns green even when it does not have network connectivity.

For this, the led of the EAP will be green when it is powered normally; it is not related to the network connectivity.

I'm requesting that the AP LED should not show green if the AP has no network connectivity for example.

3. Lastly, It would be a great feature if the AP's light changed color (blue) when clients are connected.

Now we can see the client list in Omada Controller, could you please tell us why you want such a function?

I'm requesting that the AP LED should chnage to Blue if a client is connected to that specific AP.

Thank you!

Hi, just wanted to add that I'm having the same problem as @RJS1.

In my case it happens with an EAP 245 V3. Yesterday I installed 1, it had firmware version 2.0 on it (shipped version) and it didn't work so I updated to version  2.1.0 Build 20181107 Rel. 39421 (latest version as of today 2019/04/02) but it didn't solve it.

Best,

Olivia

PS: forgot to mention, the Omada Controller is version 3.1.4.

liv3010m wrote

Hi, just wanted to add that I'm having the same problem as @RJS1.

 

In my case it happens with an EAP 245 V3. Yesterday I installed 1, it had firmware version 2.0 on it (shipped version) and it didn't work so I updated to version  2.1.0 Build 20181107 Rel. 39421 (latest version as of today 2019/04/02) but it didn't solve it.

 

Best,

Olivia

 

PS: forgot to mention, the Omada Controller is version 3.1.4.

Hi,

We have optimized the AP Locate feature in Omada Controller3.1.4; it can be available only when we upgrade the firmware to the corresponding version. The bundled firmware of EAP245v3 with Controller3.1.4 has not released and it will be released in these days. By then, please upgrade it and the AP Locate will be OK.

Hi @forrest, thanks for your reply. Hopefully it's available soon. 

I'll report back by then.

Best,

Olivia

This is suposed to be a business grade product and yet the software development and testing is like pre-school. The Omada locate function is still not working! Using the latest Bundle Omada Controller 3.2.3. with Bundled Firmware. Model:OC200 1.0, Firmware Version:1.2.0 Build 20190823 Rel.42002, Controller Version:3.2.3, EAP320 Version 1.4.0 Build 20180925 Rel. 50612, EAP330 1.4.0 Build 20180925 Rel. 37155.

@Tomasin 

This appears now working with Omada Controller (OC200) running firmware 1.2.1 Build 20191126 Rel.59455 and Omada Controller 3.2.5

and EAP245 v3 running 2.3.1 Build 20191029 Rel. 61589

@volkswagner 

Running firmware 1.2.1 Build 20191126 Rel.59455 & Controller Version 3.2.5. The locate still does not work on EAP330 or EAP320. However, it does work on our EAP225-Outdoor units. So much for investing in TP-Link hardware if they make models EOF so soon after release and then not support them. How can I trust TP-Link in future.

@Tomasin 

Let me explain it to you. 

Now the EAP320 and EAP330 don't support locate features. We add this feature at the firmware of 2019, but the EAP320 and EAP330 are EOF in 2018, and since then, we didn't update the firmware of the EAP320 and EAP330. That's why EAP320 and EAP330 don't support this feature. 

Normally, when the models are EOF, we may not upload new firmware on the website unless there are some bugs to fix. 

Locate feature only exists on the new models of the EAP, this may bring you inconvenience, but how can we ask that we have to add new functions to the device which is EOF?

We may not make new firmware for the devices which are EOF, we will will still provide support for you.