On Omeda application not showing my connected client

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

On Omeda application not showing my connected client

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
On Omeda application not showing my connected client
On Omeda application not showing my connected client
2021-09-22 09:28:35
Model: EAP225  
Hardware Version: V3
Firmware Version:

Hi,

We have 4 Eap225 V3 Access Point. And tri to enable Omeda application but i m looking that there are no connected client showing in Omeda application while all access point showing connected. showing 100% using of 1 access point from all access point. Another 3 are showing 0% using. while centralization features is in it. I am trying to connect customer care they are saying we can not help in this.

  0      
  0      
#1
Options
4 Reply
Re:On Omeda application not showing my connected client
2021-09-23 18:35:42

@nukleus 

 

Can you provide a screenshot of what you are seeing?

 

Also are you running the APs via a controller or standalone, also state any firmware versions on the APs if you can

 

Thanks

 

  0  
  0  
#2
Options
Re:On Omeda application not showing my connected client
2021-09-25 05:10:57

@Philbert 

Dear Tplink team,

 

Some screenshots are attached.

only 1 Access Point is using 100% usage.

I think this is not any

centralisation of devices

  0  
  0  
#3
Options
Re:On Omeda application not showing my connected client
2021-09-25 05:11:57
while all client is connected network via Access Point.
  0  
  0  
#4
Options
Re:On Omeda application not showing my connected client
2021-09-25 14:43:36 - last edited 2021-09-25 14:44:23

@nukleus 

 

Hey

 

This has been mentioned a few times on the forums and quite a common thing, seen it before :)

 

Basically, the Firmware on your 225 v3 is  5.0.4 which is designed (requires) a controller running SDN v4 (4.4.4 is the latest), you are running v3.xx controller and that's the cause

 

You have two choices really..

 

1.  Update the controller to v4.4.4 (latest).  

OR

2. Downgrade the APs to firmware 2.xxx  which was the last one for the v3 controller  (available here  https://community.tp-link.com/en/business/forum/topic/264504  )

 

Personally, I would go for the SDN upgrade, v3 controller was end of life in 2020 and v5 has been mentioned for Q4 2020 / or Q1 2022

 

It looks like you are running a software controller, should be easy to update :)

  0  
  0  
#5
Options