-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Omada LXC - Updating instructions #402
Comments
Version 5.5.6
|
Version 5.6.3
|
Version 5.7.4
|
Version 5.8.4
|
Version 5.9.9
|
New version 5.9.31:
Release Notes:New Feature/Enhancement
Bug Fixed
|
No, the path is unknown |
Here is something you can use to get latest URL and version from the URL... latesturl=$(curl -fsSL "https://www.tp-link.com/us/support/download/omada-software-controller/" | grep 'x64.deb"' | head -n1 | sed 's/.*Controller\" href=\"//;s/\".*//')
latestversion=$(sed -e 's/.*ller_v//;s/_Li.*//' <<< "$latesturl")
echo "Latest version is $latestversion at $latesturl" This currently returns: |
Both scripts have been updated. To update Omada, run the following command in the Omada LXC console.
Compares versions
Thanks @thpryrchn |
Update script for latest version v5.13.23 is broken. Looks like the changed naming of deb file |
Their website shows v5.13.22 as the latest release. |
The command to check for the latest version also shows 5.13.22
|
If you look at the site source there is a new version available: https://static.tp-link.com/upload/software/2024/202401/20240112/Omada_SDN_Controller_v5.13.23_linux_x64.deb Only difference I see is linux vs Linux But somehow the Curl command doesn't bring the new version. |
Issue found.... it is not on the US site yet. It is on the NL site https://www.tp-link.com/us/support/download/omada-software-controller/ |
Also the EN (GLobal) site, it is not there yet: |
I'm sure I read something before on updating the Omada LXC - the suggestion at that point was to backup the config, delete the LXC, create a new one, and restore the config.
I did this once before to upgrade to 5.3.1, however this did uncover an issue; I have the Omada API providing stats into my Home Assistant. and the API requires sending in the unique Site identifier, which is a 32-bit GUID. A new GUID was assigned when Omada was installed in the new container, hence my API queries failed and had to be updated with the new GUID to continue working.
To upgrade to 5.4.6, I simply executed the 2 key lines from the install shell script, and the update kept the config, and really key, the GUID:
Obviously the URL will change depending on the new version release date and version, but might be worth adding this to the Upgrade Instructions for Omada?
Thanks!
The text was updated successfully, but these errors were encountered: