I can confirm that dhcp issue persisted. After upgrade, all devices were restarted and from 3 devices which get wrong address, two had wrong address and only one had the from reservation. I clicked on each device to reconnect, now I am waiting to see when wrong address will get assigned, the only difference which I can see it at least lasts now for over 12 hours.

Really ironic for me is that only tp-link's wireless devices get wrong address, their firmware seems to be buggy and for some reason they request new dhcp assignment to the dhcp server, getting it as second address, this is something which you can test with your pc, when you are connected, run command to renew dhcp and you will get another address from one which you reserved, this would be the second address (you can assign as much as technically possible), where your pc would be reachable on both ip's, the old and the new, you can then verify which ip is shown in omada. So far, it would be just a visual glitch as dhcp works then properly. In my case, the only devices which get wrong address are tp-link's wireless devices where one can not set static ip and looking at previous firmware updates there already issues with wireless.

I can reproduce the issue without wireless and with wired connection as explained above, it is very strange that tp-link seems not to be capable to reproduce the issue. If they are incapable to reproduce and fix the issue, then it is remarkable that tp-link is not interested in fixing it or at least making a workaround possible by simply offering setting of static ip's, at least in my case it would resolve the problem, I am not sure about workaround for you, but if devices which get wrong address are from tp-link, then you probably should try either getting a refund for your purchase as it obviously is not working as stated in specifications or tp-link should provide a fix or workaround. I personally gave up on idea running omada for anything more than just to manage mesh network, it's not worth the hassle, even cheapest $ 10 device with openwrt would do the job for XX years without touching it once in that period.

  @Fae nice to hear that you noticed it as you did mDNS issue, but the question remains when this beta will be available and if it will be again windows version and then who knows when linux? I consider dev team can tell you the ETA for those issues which you gratefully could share with community, especially because DHCP is some very basic functionality and if your team was able to reproduce, then it must be on highest priority as those who could reproduce it are aware that every customer using buggy soft has this issue. Another point which I see here is, your team should maybe check why there are not so many posts about this issue if since last few versions this issue persists, where by the way, since which version is it broken?

For linux controllers on linux, curl is present on most systems and curl can be used for ddns and many other things, for windows a binary could be used or you could add it to your code (which is better you do not do, from feeling, I guess it would produce further bugs). Next to those useless few options for dynamic dns, I at least would prefer ability to click on "Custom" and enter curl command, especially taken in mind that to purchase a domain and have much higher amount of possible subdomains and features, without ad's or similar crap, those few which you offer were already few years ago obsolete.

curl, mdns, wireguard, iptables, dnsmasq, ... all of it is present for controller and those packages work. If your software is buggy, which it is, then it forces your customers to use alternatives and I bet most who bought in omada because of centralization would prefer ability to control those things at least on their controller.

Another point which I do not understand is why at all do you supply iperf2 instead of iperf3?