Beta Software Omada Controller_v5.1.6_Windows For Trial (Beta Edition) - [Closed on 23 May 2022]
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Updated on 23 May 2022:
So far, Omada Controller v5.1 has been officially released,
Check this thread for details if you haven't noticed this update yet.
Most of Omada EAP devices have released official firmware to support PPSK function.
Please check for updates via cloud or via the TP-Link Official Website manually.
Thank you so much for your valuable feedback as always!
------------------------------------------------------------------------
Updated on 28 February:
Add the beta firmware of EAP245 v3 and EAP620HD v1 which are adapted to Omada Controller v5.1.
Kind Note:
Omada Controller v5.1.7 Windows has been released on 25 February. If you would like to test more with the EAP beta firmware, please install the Controller v5.1.7 (Windows) instead.
There is no other Controller version for test yet, this post will be actively updated if more test firmware is available.
We appreciate your attention on this topic, welcome to comment below with your real feedback on this trial.
Any other feedback about the Omada SDN solution, welcome to start a new thread from Here.
Many thanks for your great cooperation and understanding!
------------------------------------------------------------------------
Hello Everyone,
We are excited to announce that we now have the Beta firmware of Omada Controller v5.1.6 (Windows) for trial!
The Purpose Of The Beta Firmware
We hope to offer you with a chance to experience the new features added in the Controller v5.1 in advance, and also give us TP-Link the opportunity to fully test the firmware in your real network environment and scenarios before the official release.
Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
The Main Features To Tests
1. Heatmap
Go to Map -> Map, import your map, edit your map scale, place EAPs, then simulate.
2. Private Pre-Shared Key (PPSK) - it requires upgrading the EAP to the adapted firmware.
For “PPSK without RADIUS”, you can create PPSK profiles (Settings -- Profiles -- PPSK).
3. the Report page
Try to view, export and email network reports.
4. Facebook Wi-Fi 2.0 - it requires upgrading the EAP to the adapted firmware.
Go to Settings -> Authentication -> Portal to configure the Facebook Wi-Fi 2.0.
5. Upgrade Schedule
Go to Settings -> Services to configure the Upgrade Schedule.
6. IPTV - it requires upgrading your ER605/ER7206 to version 1.2.0.
Go to Settings –> Services -> IPTV to configure it.
7. Connect FTP/TFTP/SFTP/SCP file servers for backup and restore
Go to Settings –> Maintenance –> Backup & Restore
For more detailed Release Note, please check the attached documentation at the end.
Download Link For Beta
Omada_SDN_Controller_5.1.6_Windows (Beta)
Kind Note:
Omada Controller v5.1.7 Windows has been officially released on 25 February.
Check this thread for details if you haven't noticed this update yet.
There is no other Controller version for test yet, this post will be actively updated if more test firmware is available.
Omada EAP:
EAP620HD V1_1.1.0 Beta Firmware (Fully Adapted to Omada Controller v5.5)
EAP660HD(EU)_v1_1.1.1_Build 20220209 (Beta)
EAP660HD(US)_v1_1.1.1_Build 20220209 (Beta)
EAP225(EU)_v3_5.0.8_Build 20220209 (Beta)
EAP225(US)_v3_5.0.8_Build 20220209 (Beta)
EAP245(EU)_v3_5.0.5_Build 20220224 (Beta)
EAP245(US)_v3_5.0.5_Build 20220224 (Beta)
EAP225-Outdoor(EU)_v1_5.0.8_Build 20220209 (Beta)
EAP225-Outdoor(US)_v1_5.0.8_Build 20220209 (Beta)
Most of Omada EAP devices have released official firmware to support PPSK function.
Please check for updates via cloud or via the TP-Link Official Website manually.
Omada Gateway (official version):
ER605(UN)_V1_1.2.0 Build 20220114 Release Note >
ER7206(UN)_V1_1.2.0 Build 20220117 Release Note >
Kind Notes:
1. Cloud Access is unavailable for the Beta Controller 5.1.6.
2. We strongly suggest you save the backup file before upgrading.
3. To revert to the previous Controller version from this Beta firmware, you must completely uninstall it.
Feedback:
Any further feedback on the new firmware, please feel free to comment below.
When reporting an issue, especially it's about firmware upgrade, it's suggested to include the following info:
-- Omada Controller version (previous and current)
-- Device Model(s) and Hardware
-- Device Firmware (previous and current)
Note: if you decide to downgrade the firmware before sending feedback to us, we recommend you save a copy of the current Log file* and Backup Config file** before you do that, which might be helpful to address the issue you suffered from the new firmware.
* The Log file of Controller can be exported under Settings -> Services -> Export Data -> Running Log.
** The Backup Config file of Controller can be exported under Settings -> Maintenance via local access.
Thank you in advance for your great cooperation and support!
We look forward to hearing from your real and valued feedback here!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Amen
- Copy Link
- Report Inappropriate Content
OMG... your neglegence to detail... who said anything about ProtonMail?! It's ProtonVPN.
You say they are in a "demo" state?! Hahahaha... this is why well known companies have been using them for long time, like InvizBox...
Tell me more "pro"... hahaha.
I leave you two insulting kids enjoy each other.
- Copy Link
- Report Inappropriate Content
you leaving so soon and i here i was hoping you would eat the cookie as you promised
- Copy Link
- Report Inappropriate Content
@DaSmith you must be hardcore woke genious who can not read, here for the idiots:
I had lol after you claimed protonvpn as leading big company :). As second, protonvpn is by far not a big company offering vpn services, they are in demo stage with their vpn services. All big brands offer since already almost 2 years and there are several solutions how different providers resolve ip storage in ram (as it is what you talk about).
For such a woke person one seems needs to remind you that you were talking about vpn and yes, protonvpn is still in demo phase, luckily I was their beta tester for vpn, I would have denied to help if I knew that it would raise such customers like you. Thanks for a pro, I never said anything about me, but nice that you recognized it ;)
- Copy Link
- Report Inappropriate Content
EAP660HD (EU) EAP620HDv1 (EU) has some issues,
I use PPSK and beta version in this thread since it is the only one that supports PPSK
The problem probably has nothing to do with EAP beta but since I use it I post it here.
I also use Omada Controller 5.2.4 on Ubuntu. also beta.
But this problem is nothing new and I do not think it has anything to do with beta, I have probably had these problems since EAP6xxx
1. Fast roam does not work right away. it is only when I have roamed a round that it works. it seems like EAP needs to learn the WiFI device first. before I have taken a round with device the device disconnect from the WiFi completely before it roams to the new EAP, When all EAPs know the device, it goes much easier with fast roam.
I have tried most settings that have to do with roam without it helping.
2. Unscheduled Automatic Power Save Delivery does not work. If you take a power cycle on EAP, it works for a while but it stops working
3. WPA Authentication times out/failed, There is a lot of this.
4. WPA3, I have tried to connect with WPA3 but have not been able to do this yet.
5, Batch config missing up a lot of settings that should not be changed.
6. No Acknowledgement, if enabled nothing work.
Since Fast roam does not work so well, I have started to have problems with some devices that previously roamed well now hanging on EAP with weak signals.
- Copy Link
- Report Inappropriate Content
Dear @shberge,
Thank you very much for taking the time to post your feedback. We appreciate it.
For the issues you reported, I'll comment below one by one.
shberge wrote
But this problem is nothing new and I do not think it has anything to do with beta, I have probably had these problems since EAP6xxx
1. Fast roam does not work right away. it is only when I have roamed a round that it works. it seems like EAP needs to learn the WiFI device first. before I have taken a round with device the device disconnect from the WiFi completely before it roams to the new EAP, When all EAPs know the device, it goes much easier with fast roam.
I have tried most settings that have to do with roam without it helping.
Here is a new article about Fast Roaming feature for your reference,
Getting To Know Fast Roaming (aka Seamless Roaming) of Omada EAP Products.
If you still have issues with the Fast Roaming, welcome to Start a New Thread with more detailed information so that we can discuss more and try to help you out.
2. Unscheduled Automatic Power Save Delivery does not work. If you take a power cycle on EAP, it works for a while but it stops working
I noticed the feedback in the following post, and has reported it to the support engineer for further investigation.
Unscheduled Automatic Power Save Delivery not working as it should?!
If there is anything new, I'll update in the post above.
3. WPA Authentication times out/failed, There is a lot of this.
Regarding WPA Authentication times out/failed issue, do you have any clients that are actually seeing issues?
If you would like to discuss it and try further troubleshooting, please Start a New Thread with more detailed information.
4. WPA3, I have tried to connect with WPA3 but have not been able to do this yet.
Ensure both EAP and wireless client support WPA3 firstly to enjoy Wi-Fi protected by WPA3.
If you have further trouble, welcome to Start a New Thread with more detailed information so we can discuss further and try to help.
5, Batch config missing up a lot of settings that should not be changed.
There is one feedback related to batch config on the community, see the post below, it's already been fixed in controller v5.1.7.
Omada SDN 5.0.3 batch config BUG
If you find other new bugs, don't hesitate to Start a New Thread with as more details as you can to help us improve the Omada system.
6. No Acknowledgement, if enabled nothing work.
Enabling No Acknowledgement can bring more efficient throughput, but it may increase error rates in a noisy Radio Frequency (RF) environment. It's disabled by default and recommended leaving it disabled if the RF environment is not pretty good.
- Copy Link
- Report Inappropriate Content
I register that you have an explanation for all the points I have mentioned, but it does not help much. points 1-6 are still bugs and should be reported to those who develop, and it should also be fixed,
What I have mentioned should also be easy to reproduce if you want.
As I also mentioned, both controller and EAP are in beta so this is of course something that can be expected when you use beta and that it is already fixed in the official release.
if it ever comes? 
I think many would be happy if you could update EAP soon.
EDIT:
WPA3: it looks like this does not work with PPSK , but with WPA Personal WPA3 works.
EAP Batch Config: when enable or disable Unscheduled Automatic Power Save Delivery VMM is also disabled on all EAP
More EDIT:
I steel use beta so I post in this thread
Regarding roaming, to test a little more, I replaced all EAP6xxx with some very old Unifi AP-AC-M access point, same channel same encryption same location, with this setup it roams without problems.
Now I have a lot of complete disconnect when roaming with EAP6xxx , this applies to all units that I have tested with.
Sometimes I have to manually connect to the network again. and YES my device have fast roam,
PLS add this fast roam display in Omada to se device that is fast roam compatible.
I hope roaming works when the new EAP firmware arrives sometime.
I want to use tp-link and not unifi so I hope you do effort to make this work.
- Copy Link
- Report Inappropriate Content
Dear @shberge,
shberge wrote
EDIT:
WPA3: it looks like this does not work with PPSK , but with WPA Personal WPA3 works.
EAP Batch Config: when enable or disable Unscheduled Automatic Power Save Delivery VMM is also disabled on all EAP
The WPA3 issue has been reported to the support engineer for further checking.
The EAP Batch Config issue has been located, and it's planned to get fixed in Controller v5.4.
BTW, the EAP firmware adapted to controller v5.1 is on the release process now, it will take some time, please wait patiently.
- Copy Link
- Report Inappropriate Content
I have replaced EAP660 HD with EAP245, now roam between EAP620 HD, EAP245 and EAP225-Outdoor is without problems, it seems that the problem is EAP660 HD that miss up WiFi network for me.
But I do not want to leave TP-Link's most expensive access point on the shelf. so come up with a fix or maybe there is something wrong with it?
there is steel a lot of WPA Authentication times out/failed but this is reduced with 75% or more.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 7
Views: 9386
Replies: 32
Voters 5
