@Santaklon 

Santaklon wrote

  @Clive_A 

 

Is there any Update on the matter? When can we expect a firmware update that reliably fixes this?

 

In my case I have had frequent problems controlling basic IoT devices: End devices are throwing communication errors because of IP verification issues. Maintaining and debugging RTU Modbus communication is higly problematic. And it all only happens to devices connected to this specific switch (On other Omada switches they work perfectly fine). It really is a problem!

 

It seems this switch was released prematurely - just setting it up and adopting it was a nightmare already. If it says Omada on the box, it really should to be fully compatible from day one - it's the whole reason we are buying Omada over standalone devices in the first place.

 

An update on the matter would be most appreciated.

The forum team does not provide information in reply about the development progress or details. 
Neither do we provide the estimated time for this feature, nor details and explanations for the roadmap. 

As this is an ongoing request and was previously addressed, your request is already known to the dev team.

Please refer to the final firmware release notes for this feature. 
Thanks for your understanding. 

  @Cepheus0815 

We are a smart home integrator and use Omada network solutions for all our installations. I was keen to test the ES range as a replacement for unmanaged switches; features such as Omada integration, port labelling, and VLAN support would be beneficial. As such, I purchased an ES206GP to replace an unmanaged switch at my home. I cannot believe that IP addresses from connected clients are not reported to the controller. It was fine with a basic Netgear switch, I've 'upgraded' to a switch that reportedly is a business-grade switch with Omada support, and now I can't see the IP address for the clients connected to it... madness! This is a basic requirement of any network management platform.

We will not specify these switches until this issue is addressed.

  @Flo30 

In my case, ARP detection wasn't help :( 

I have an ER707-M2. Firmware update is avaliable on release candidate to 1.3.0 in early access program

  @zakrzu 

Hello,

I must admit I’m a bit confused after rereading the forum. Just to confirm, the feature still doesn’t work on the ES switch series, right?

For your information, here’s my current setup:

• ER707-M2 v1.20 (firmware 1.2.3)   --> EDIT: test with 1.3.0 and ARP detection  --> Not working too

• ES205GP v1.0 (firmware 1.0.3)

• 2 X ES220GMP v1.0 (firmware 1.0.1)

• Omada Controller 5.15.24.18

• Several WiFi APs

And it is not working on ES205GP /  ES220GMP ....

Given this, should I consider returning everything to my supplier, or is there still a chance that TP-Link will enable reading the client IP addresses directly through these switches? :)

  @Flo30 

You're right...

ES205GP v1.0 does not support ARP Table and somehow couldn't reach an IP addresses via Router.

I'am only using it for powering EAPs for now.

TP-Link team knows the issue and try to fix this in future update, at least i hope :) 

Some of you, I update my ER707 to 1.3.0 and ARP and no change. it is not working on ES 205 and ES220

  @Clive_A 

I have ARP detection enabled.
I have the latest Omada firmware installed on my ER707-M2 router (FW 1.3) and ES210GMP router (FW 1.0.3).
If I can read the IP assigned to a given MAC address from the logs, the controller should also be able to logically handle it. I admit, it's a bit of a hassle buying Omada equipment and not being able to directly check the IP address on the controller. Is there anything else I should do?

  @Sarlet 

Sarlet wrote

  @Clive_A 

I have ARP detection enabled.
I have the latest Omada firmware installed on my ER707-M2 router (FW 1.3) and ES210GMP router (FW 1.0.3).
If I can read the IP assigned to a given MAC address from the logs, the controller should also be able to logically handle it. I admit, it's a bit of a hassle buying Omada equipment and not being able to directly check the IP address on the controller. Is there anything else I should do?

If you have a new question regarding this, please create a new post and elaborate your question in detail and with a diagram.