I just upgraded to 5.14.32.2 also, and it seems to be working ok so far.  It was just a few commands, basically the same as before, just with the updated URL/filename.

cd /tmp
wget https://download.tplinkcloud.com/firmware/omada_v5.14.32.2_linux_x64_20240920174223_1727578445400.deb
sudo apt install /tmp/omada_v5.14.32.2_linux_x64_20240920174223_1727578445400.deb

New interface for controller! Jan 9th 2025

5.15.6.7 is out and running great.

cd /tmp

wget https://download.tplinkcloud.com/firmware/omada_v5.15.6.7_linux_x64_20241128140044_1733188152890.deb

sudo apt install /tmp/omada*.deb

If you don't reboot, clean your /tmp directory:

rm -f omada*.deb

Hello everyone,

A few months ago, I installed the Omada Controller on a Raspberry Pi 5. Everything runs perfectly, even with the latest controller version.

I still have an old Raspberry Pi 3 B lying around, and since yesterday, I've been desperately trying to install the Omada Controller on the Pi 3. The actual installation process is relatively simple, but unfortunately, the controller just won’t start for me.

The last thing I see is: "Starting Omada Controller. Please wait....." It gets stuck at 60%—and in my current attempt, it's been stuck there for about 60 minutes.

The same thing happened last night, and I eventually gave up because I had to go to bed. I installed Pi OS Lite 64-bit, then MongoDB and Java, exactly as described in the instructions—just like I did on my Pi 5.

Today, I started a completely fresh attempt, reinstalling everything from the OS onward.

I’m aware that the Pi 3 is significantly slower, but it can’t possibly take this long, can it?

The original poster writes that they got it running on a Model 3B+. Could the model difference be the issue?

Does anyone have any idea what the issue might be?

Marda236 wrote

Hello everyone,

A few months ago, I installed the Omada Controller on a Raspberry Pi 5. Everything runs perfectly, even with the latest controller version.

I still have an old Raspberry Pi 3 B lying around, and since yesterday, I've been desperately trying to install the Omada Controller on the Pi 3. The actual installation process is relatively simple, but unfortunately, the controller just won’t start for me.

The last thing I see is: "Starting Omada Controller. Please wait....." It gets stuck at 60%—and in my current attempt, it's been stuck there for about 60 minutes.

The same thing happened last night, and I eventually gave up because I had to go to bed. I installed Pi OS Lite 64-bit, then MongoDB and Java, exactly as described in the instructions—just like I did on my Pi 5.

Today, I started a completely fresh attempt, reinstalling everything from the OS onward.

I’m aware that the Pi 3 is significantly slower, but it can’t possibly take this long, can it?

The original poster writes that they got it running on a Model 3B+. Could the model difference be the issue?

Does anyone have any idea what the issue might be?

  @Marda236  When I first posted about this it "worked" on a 3B+ in the sense that i started and I could access the setup pages - I never used it as a production machine. 

Since then it appears that the memory requirement of newer controller version gradually increased to the point where even a Pi 4B takes several minutes to start up the Omada controller. 

There was a previous discussion in the thread that even the hardware controllers from TP-Link are brutally slow.

It's all about memory. Just forget about using the 3B, get at minimum a Pi 4B with 4GB - a Pi 5 with 8GB runs fantastic.

I briefly inserted the SD card into the Pi 5, and it runs without any problems.
It's a shame that the Pi 3 is no longer suitable for it.
Thanks for your answers!

For information to anyone else, I've just installed the latest version of the controller (v5.15.20.18) using the link pulled down from the controller download page.
 

I followed the instructions in the original post, installing Mongodb 4.4.18, openjdk-17-jrc-headless and jsvc. But then I found I needed to add a symbolic link to the openjdk directory to avoid a controller installation message that Java Home could not be found:

$  cd /usr/lib/jvm

$ ln -s java-17-openjdk-arm64 default-java

After that, everything worked.

Thx. Worked for me on Pi5 (lite x64) Just needed to change the link for the latest version of controller.

And if you're like me, using ufw, here the list of ports need to allow :
ufw allow 8088/tcp     # Accès HTTP
ufw allow 8043/tcp     # Accès HTTPS
ufw allow 8843/tcp     # Portail captif HTTPS
ufw allow 29810/udp    # Discovery
ufw allow 29811/tcp    # Management v1
ufw allow 29812/tcp    # Adoption
ufw allow 29813/tcp    # Upgrade
ufw allow 29814/tcp    # Management v2
ufw allow 29815/tcp    # Transfert v2
ufw allow 29816/tcp    # RTTY
ufw allow 27001/tcp    # Appli mobile

And if you're like me, using proxmox on Raspberry, on a lxc container, mongodb will not be happy because one of his dependencies (libssl1.1), you need to install manually the dependancy before install mongodb
wget http://ftp.us.debian.org/debian/pool/main/o/openssl1.1/libssl1.1_1.1.1n-0+deb11u4_arm64.deb
dpkg -i libssl1.1_1.1.1n-0+deb11u4_arm64.deb

mechanic123 wrote

Just to clarify:

When I install the omada software controller on a raspberry pi 4, then I have to use mongodb 4.4.18 as in the opening post?

I tried installing mongodb 7.0.7, but when the controller wants to start, it says: "Fail to start mongo DB server".

 

Any thougts on this?

Thanks.

  @mechanic123  That's why the instruction says to use MongoDB 4.4.18 (or earlier).  Any version later than that does not work.

There is a known reason why this is the case, but I dont remember why and I dont have time to google it now