Beta Software EAP783_V1_1.1.92 Beta Firmware (Update on 23th May, 2025)
This Article Applies to: EAP783_V1 Fully Adapted to Omada SDN Controller v5.14 or above
Release Notes:
New Features/Enhancements:
1. Supports displaying Configuration Result.
2. Supports cluster deployment in Controller mode (CBC does not support).
3. Supports Radius Proxy.
4. Supports OWE.
5. Supports custom Channel Range.
6. Supports upgrading firmware through cloud in Standalone mode.
7. Supports Portal Logout.
8. Supports disabling HTTP protocol in Standalone mode.
9. Supports DHCP Option43.
10. Supports multiple Radius Servers for MAC-Based Authentication.
11. Supports configuring NAS ID with WPA-Enterprise encryption.
12. Supports DNS Queries.
13. Supports configuring Rate Limit with Portal in Controller mode.
14. Supports configuring the Device Name in Controller mode, which can be carried in LLDP/SNMP/DHCP interaction.
15. Supports viewing status information and making some simple configuration through Standalone management page when the EAP is managed by the Controller and disconnected with Controller currently.
16. Supports displaying the maximum associated clients based on the EAP model in Controller mode.
17. Supports displaying the radio bandwidth of the EAP in Controller mode.
18. Supports configuring wireless mode in Controller mode.
19. Supports statistics of Multicast/Broadcast packets.
20. Supports 1024 PPSK entries.
21. Supports 802.11 a/n mixed in 5G.
22. Supports Non-stick Roaming function.
23. Supports authentication type of EKMS and Generic Radius with Unbound MAC for PPSK with Radius.
24. Supports Multicast Filtering with IPv6 address.
25. Supports reporting default OFDMA status.
26. Supports MAC Filter with 2000 entries per MAC Group profile.
27. Support DNS adoption.
28. Supports Multicast/Broadcast Rate Limit.
29. Enhances security protection.
30. Improves stability.
31. Improves support for more SSH commands.
32. Optimizes Automatic Power Optimization function.
33. Optimizes the configuration of Beacon Interval.
34. Optimizes roaming function.
35. Optimizes logs displayed in Controller.
Bug Fixed:
1. Fixed the issue that RSSI information display error in WLAN Optimization.
2. Fixed the issue about LLDP-MED packet forwarding exception.
3. Fixed the issue that URL Filtering cannot work properly when TLS1.3 is enabled in the browser.
4. Fixed the issue that HTTPS Redirection and Pre-Authentication Access don’t take effect in some special scenarios.
5. Fixed the reboot issue of EAP when client try connecting tri-band MLO SSID.
Notes:
1. This version of firmware is applied to the Omada APP v4.17 or above.
Beta Firmware Download
Attention
Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
EAP783_v1_1.1.92_Build_20250507(Beta)
EAP783_v1_1.1.90_Build_20250115(Beta)
Notes:
(1) The above firmware is applied to EAP783 V1.
(2) Your device’s configuration won’t be lost after upgrading.
(3) The above firmware is fully adapted to Omada SDN Controller v5.14 and above
Update Log
23th May, 2025
Provide the beta link for EAP783_1.1.92:
EAP783_v1_1.1.92_Build_20250507(Beta)
18th Mar, 2025
Update the release note.
17th Jan, 2025
Provide the download link:
EAP783_v1_1.1.90_Build_20250115(Beta)
Feedback
Any further feedback on the new firmware, please feel free to comment below or start a new thread from HERE.
To get better assistance, you may check Tips For Efficiently Reporting an Issue In The Community.
When reporting an issue, especially it's about firmware upgrade, it's suggested to include the following info:
- Management mode (Controller or Standalone)
- Device Model(s) and Hardware
- Device Firmware (previous and current)
Thank you in advance for your great cooperation and support.
Recommended Threads
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Current Available Solutions to Omada EAP Related Issues [Constantly Updated]
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Vincent-TP Does this fix the AP sending out a German country code in Australia?
- Copy Link
- Report Inappropriate Content
Nope, it's now sending out a US code 
- Copy Link
- Report Inappropriate Content
Hi @chrisdfw
Thanks for posting here. Yes.
What's the crash mean? Please give us more details about the crash:
1. which bands are affected?
2. how to recover the crash?
3. When crashed, are the affected SSIDs avisible?
4. How often will the MLO SSID crash?
5. A screenshot of the MLO SSID settings.
chrisdfw wrote
I have tryied 1.1.92 MLO is still crashing with 1.192 and with OFDMA off stil getting crashes I have rolled back to stable do you need me to collect data?
To the users with the connection issues did you set PMF to capable?
PMF
MandatoryCapable
- Copy Link
- Report Inappropriate Content
Thanks for posting here. Yes.
What's the crash mean? Please give us more details about the crash:
1. which bands are affected? Mostly 6GB but 5G will crash also.
2. how to recover the crash? Reboot
3. When crashed, are the affected SSIDs avisible? NO
4. How often will the MLO SSID crash? Normally when MLO device joins
5. A screenshot of the MLO SSID settings.
- Copy Link
- Report Inappropriate Content
Dear TP-Link Team,
Thank you for your continued work on the EAP783. I understand that firmware development takes time and appreciate your efforts.
That said, I’m a little concerned that since the initial beta firmware (1.1.90) was released in January 2025, and the updated beta (1.1.92) in May 2025, there is still no stable firmware available.
For a product positioned as business-grade, it feels somewhat disappointing that we are still relying on beta firmware after more than six months.
Could you please share any update or approximate timeline for the release of the next stable firmware? Even a rough schedule would help to set expectations.
Thank you again for your work, and I look forward to your response.
Best regards,
- Copy Link
- Report Inappropriate Content
The same issue with eap772v1..., but you have beta version.It is not enterprise support, company, hardware.
- Copy Link
- Report Inappropriate Content
Hi @chrisdfw
Thank you for the info.
We recommend submitting a support ticket via email for efficient assistance.
Please include the following information in the email:
1. This Forum ID 736358;
2. your community nickname;
3. The type of controller you are using;
4. The config file of the controller.
chrisdfw wrote
Thanks for posting here. Yes.
What's the crash mean? Please give us more details about the crash:
1. which bands are affected? Mostly 6GB but 5G will crash also.
2. how to recover the crash? Reboot
3. When crashed, are the affected SSIDs avisible? NO
4. How often will the MLO SSID crash? Normally when MLO device joins
5. A screenshot of the MLO SSID settings.
- Copy Link
- Report Inappropriate Content
Agree.
TPLink folks - What is the timeline for next EAP firmware release??
And when can we expect a stable (not beta) version with fixes?
- Copy Link
- Report Inappropriate Content
I don’t understand why everyone here is being so forgiving about this. I spent €5,000 on EAP783 APs for two locations.
They are almost two years old, and yet they still can’t reliably deliver the basic Wi-Fi 7 MLO functionality that was advertised.
TP-Link keeps asking for endless debugging details on the forums, but why? This is an easy bug to reproduce. Just take any modern iOS device, connect via Wi-Fi 7 MLO, and the APs will crash. It happens in both stand-alone mode and with a controller.
If you contact TP-Link support about these crashes, you get dragged through pointless, time-wasting troubleshooting steps, and in the end, nothing is fixed. They never acknowledge or tell you about the obvious, that this is a known, well-documented bug in their software.
This is absolutely ridiculous. Start communicating with us. Tell the truth. You know about this bug. You know how to replicate it. What is holding you back after more than a year? Or are you simply stalling until warranties expire, before telling us it was a hardware bug all along?
- Copy Link
- Report Inappropriate Content
@nikisima what i am afraid of is this: the hardware is defective. No amount of software/firmware will ever fix faulty HW.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 10483
Replies: 126
Voters 2
