Hi @alexindigo 

Thanks for posting in our business forum.

alexindigo wrote

  @Clive_A 

 

> Sub this to get the update timely: Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates.

 

Looks like that post is locked and doesn't get posted recent updates, 

 

Example, for "Recent releases / Early access", it lists v1.2.0 for ER8411 from January of this year (11 months old)

 

> ER8411 V1_1.2.0_Build 20240112 Beta Firmware for Omada Controller V5.13 (Released on Jan 12th, 2024)

 

While my current software version for ER8411 is 1.2.2.

 

And this is the one that has any mentions of the Omada version in the range you posted (v5.15 and 5.16), so it's not clear if there was no version bumped for the whole 2024 from 5.13, and for how long we'd need to wait to get our hands on 5.15 and 5.16, or that updates haven't been posted, and 5.16 is much closer than 2027.

 

Thank you.

1. I don't decide what dev's project and their progress. I think I cannot answer or reply anything else to what you described here. Nor do I affect the version and firmware release cycles. I am only providing the information and what I have or I could get about the product.

Firmware adaption follows the controller update. When a feature is on the Controller, its adapted firmware follows and will be marked out as adapted to the X.Y.Z Controller.

2. The last public beta was that time ago. And the official firmware release has it clearly on its adaptation. 1.2.1 and 1.2.2 are minors. If they were released with minor changes and fixes, they have the chance to not be opened for public beta. What would be wrong with that?

The latest release actually works well with the V5.14 since it was released. If there are no major features added to V5.14(as an example), it may not specify what firmware it adapted. There were no major GW functions were added during V5.14. That many features were on V5.13 so the release note was written in that way.

3. The post only got updated by the forum mods and we don't intend to open it for users to comment.

My best effort is to get your voice heard. But don't decide when the dev's gonna begin the development of your request. You could happen to request a feature that is on the road or in high priority.

If it is not planned, or it is planned in the long-term future, I may not be able to help you push it as I don't have the power to do so.

Dev shares the information about their plan on what version they plan to release a version. However, due to the division changes, I might soon lose first-hand access to the dev. I am afraid the information down the road is more limited.

Due to previous replies we had with other customers, we no longer provide any guarantee or estimated timeline for any features. We have clearly disclaimed that the development may be advanced or delayed but some users chose to ignore this. We will release the beta/pre-release firmware without any notice. If there is one, I will work with the team and upload it soon. Therefore, please pay attention to the post and pinned threads.

  @ttocsr 

ttocsr wrote

  @Clive_A Now that the beta controller 5.15 is out, do you have an update on FQDN?

If we won't get FQDN, would it be possible to use a script to update the peer IP address using the open API?
If so, do you have an example of what that would look like?

As it explains if you could read it again.

OpenAPI is not a reign of my ability. It's under the controller. AFAIK, we do not support script or API to do that.