As someone who is needing to rely on automation for deploying the Omada SDN controller on Linux using the tarballs, I often run into packaging inconsistencies that require me to put all sort of workar

This was reported on my repo for the container image I build. This is happening for both the beta and GA versions of 5.14.x: both of the latest beta versions, 5.14.0.11 and 5.14.20.9 and the 5.14.26.1

Since upgrading to 5.13.30.8, it looks like there is a warning message in the logs that is either just extra verbose or there is some sort of config issue. Someone started a discussion on the containe

I am not exactly sure when it stopped working but I noticed today that the cloud access connection has stopped working and I can't re-establish it. The logs from when I try to connect: https://gist.gi

I am curious if there is any sort of documentation anywhere that has a complete list of properties that would be required in order to configure MongoDB as an external service instead of being built in

@Clive_A @Hank21 @Fae Does anyone from TP-Link have any information about this, it is stupid to invest anything more in Omada SDN. i suspect this is the beginning of the end for Omada SDN, . The reaso