This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Utilization EAP235
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
When we replaced one of our old EAP 115-Wall with a new EAP235-wall I had to recognize, that the Omada 4.x doesn't show RX/TX-Frames and the Calculated Interference for the EAP235 as it did for the EAP 115.
This feature was never precise but anyway quite helpful to analyze if the channel is occupied by clients or other devices/foreign APs.
Will this behavior be back any time soon by firmwareupgrade or should we stay with an EAP225 to fix this?
As we don't mandatory need the 3 rj45-plugs we gave a try also to the eap230-wall which has the same behavior.
I suppose the 3.0 Firmware which both AP's have in common has a general problem.
Furthermore we recognized, that the eap230 and the eap235 both have a quite high rx-drop-rate counted.
That's not like it on the other AP's even if we exchange them in their position and channel-setting.
.Dear @fishbone222,
fishbone222 wrote
As we don't mandatory need the 3 rj45-plugs we gave a try also to the eap230-wall which has the same behavior.
I suppose the 3.0 Firmware which both AP's have in common has a general problem.
Furthermore we recognized, that the eap230 and the eap235 both have a quite high rx-drop-rate counted.
That's not like it on the other AP's even if we exchange them in their position and channel-setting.
I tested with one EAP235-Wall but haven't encountered the issue you mentioned above.
To better assist you, I'd like to escalate your case to the TP-Link support team who could help you more efficiently.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Once the issue is addressed or resolved, I'd encourage you to share it with the community.
Thank you so much for your cooperation and support!