[Help]: Controller doesn't seem to find new firmware updates

[antarean]

Controller Version

5.15.24.19

Describe Your Issue or Question

I have a ER7412-M2 V1.2 router/gateway controlled by the Omada controller running in docker (using the default docker-compose.yml file) on a dedicated system.
There has been no firewalls configured (apart from the gateway providing standard NAT and "protection" settings)

Currently, the gateway is on firmware version 1.0.1.
I can see a 1.2.0 available on the TP-Link website.

But the controller is not showing this. Not even when I enable the "Early Adopter" settings.

Expected Behavior

I expect the controller to inform me of new firmware versions.

Steps to Reproduce

Click on the "check for new firmware" button in the Devices list

How You're Launching the Container

I run it using the docker-compose.yml file found here.

Container Logs

When I click, I get this:

10-29-2025 15:47:54.486 INFO [comm-pool-4] [] c.t.s.o.m.c.f(): Checking Device Last Firmware...
10-29-2025 15:47:54.497 INFO [https-jsse-nio-8043-exec-5] [] c.t.s.c.l.a.AbstractReadWriteLockService(): [readWriteLockService]writeLock: java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock@5c04f8f3[Locked by thread comm-pool-4], businessId:omadac.id:108ff29e7f3971c1600c4da4dce7c6b5 get writeLock module:manager:upgrade.online.check fail, execute onFail.
10-29-2025 15:47:58.967 INFO [https-jsse-nio-8043-exec-12] [] c.t.s.o.a.d.LoginController(): cookies:[{"name":"TPOMADA_SESSIONID","value":"iam-525e97f8fc07407894ad1c69ee1661de","attributes":{},"maxAge":-1,"secure":false,"httpOnly":false,"version":0}]
10-29-2025 15:47:58.967 INFO [https-jsse-nio-8043-exec-9] [] c.t.s.o.a.d.LoginController(): cookies:[{"name":"TPOMADA_SESSIONID","value":"iam-525e97f8fc07407894ad1c69ee1661de","attributes":{},"maxAge":-1,"secure":false,"httpOnly":false,"version":0}]
10-29-2025 15:47:58.967 INFO [https-jsse-nio-8043-exec-4] [] c.t.s.o.a.d.LoginController(): cookies:[{"name":"TPOMADA_SESSIONID","value":"iam-525e97f8fc07407894ad1c69ee1661de","attributes":{},"maxAge":-1,"secure":false,"httpOnly":false,"version":0}]
10-29-2025 15:47:58.967 INFO [https-jsse-nio-8043-exec-2] [] c.t.s.o.a.d.LoginController(): cookies:[{"name":"TPOMADA_SESSIONID","value":"iam-525e97f8fc07407894ad1c69ee1661de","attributes":{},"maxAge":-1,"secure":false,"httpOnly":false,"version":0}]
10-29-2025 15:47:58.967 INFO [https-jsse-nio-8043-exec-9] [] c.t.s.o.a.d.LoginController(): central sessionId:null
10-29-2025 15:47:58.967 INFO [https-jsse-nio-8043-exec-4] [] c.t.s.o.a.d.LoginController(): central sessionId:null

MongoDB Logs

No response

Additional Context

1.2 firmware can be found here:
https://support.omadanetworks.com/us/product/er7412-m2/v1.20/?resourceType=download

I can't see if this is released, beta, pre-release, RC,.... But even when selecting "Join Early Access Program" in: "Global / Firmware", it doesn't show.

[mbentley]

I would suggest filing an issue on the TP-Link community forums or contacting TP-Link's support team. It looks like the firmware check is failing for some reason but I can't really debug app problems.

[antarean]

I was wondering if there might be something I need to adjust (from defaults) to get this to work.
Especially because of that writelock error (2nd line in provided log) makes me wonder if it's something in my environment?

I also emailed support (phoneline is not for Omada...) but as that takes time, I am also trying other options :)

[mbentley]

I'm not aware of any settings or deployed configuration that would specifically trigger that sort of event that would potentially block unless you're in a scenario where you network might be blocking things. Only other place I have seen that message is #405 and they have a proxy server they need to go through.

Any sort of network proxies, intrusion detection, SSL decryption/reencryption type devices in your environment?

[antarean]

I saw that one as well, but as I don't use a proxy server (I do have one, but it's not enforced).
There are firewall rules and all network devices are TP-Link and controlled by the controller.

I only have IDS and IPS enabled enabled, but this issue was already present before I enabled it.
And disabling those have no effect on this.

See my other reply about the differences between the US and NL sites. (UK shows the same as NL).
Changing location to United States (in the controller) doesn't change anything.
I don't want to put my controller behind a cloud-vpn to work around an issue with TP-Link's website

[antarean]

Some more digging, might be an issue with how TP Link provides the firmware.

When I go to the Dutch site (NL), I only see model V1 for the firmware (see dropdown on this page):
https://support.omadanetworks.com/nl/download/firmware/er7412-m2/

When I go to the US site, I see V1, V1.2, V1.26 and V1.60 (see dropdown):
https://support.omadanetworks.com/us/download/firmware/er7412-m2

I agree it's likely an issue with the TP Link software and/or site. I will have to wait for support to get back to me.