Replies: 1 comment 1 reply
-
They’re the same controller but one is through the TP-Link cloud connection which should be accessible anywhere and the other is directly connected over your LAN. Connect to the LAN or “on premises” one and it should update the version info. Believe it only updates that info after it connects. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Controller Version
5.15.24.17 & 5.13.330.8
Describe Your Issue or Question
Hi
I've just updated form v5.13 of the controller to v5.15 following the process
Stop container
Rename container
Use the docker run command form the docs to pull the new version
Everything came back up as expected and i got a notification on my phone that the cloud controller is connected.
I opened the app and I now see 2 instances for the controller listed
cloud management (1):
Home - Omada Standard - V5.15.24.17 192.168.0.100,... 0.1, 172.17.0.1
On-premise Management (1):
Home - Omada Standard - V5.13.24.17 192.168.0.100
I haven't deleted the old container yet but confirmed that it hasn't restarted any ideas why I'm still seeing 5.13 in the omada app?
Edit
Looking around inside the app for new features I found that under settings > maintenance the version is 5.15.24.17 so it seems the issue is just with the tile on the front page of the app reporting the incorrect version
Expected Behavior
N/A
Steps to Reproduce
N/A
How You're Launching the Container
Container Logs
MongoDB Logs
No response
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions