Stuck in the middle of Omada migration, help!
Sorry for the crosspost fromm the General Discussion, but I'm unsure as to which forum this belongs in. Mods please feel free to delete whichever one is in the wrong forum.
I'm in the middle of migrating my 3 EAP225's from a Windows-based Omada 3.2.10 controller to a new install of version 4.2.11 running in a Docker container. I've backed up the current site and succesfully restored it to the new one, but when I go to migrate the AP's, the new site says disconnected for all 3, when I click the little red exclamation mark on the AP, it says the device is not compatiable, to manage it I have to upgrade it first. I've read the migration guide and it says that in order to be managed by Omada 4, the AP's must be at the latest firmware, but if I upgrade them the old site cant manage them. I tested this by upgrading 2 of the 3 AP's to the latest firmware through the current site. They upgraded fine and show as connected in the current site, but now the existing site cant see anything about them or manage them, and the new site shows them as disconnected. If I re-run the migration process, the new site sees all 3, but they still show as disconnected, even though it is now picking up the fact that they are at the latest firmware.
What do I do now?
At the moment I've cancelled the migration and am sitting with 2 AP's at firmware 5.0.0 Build 20201016 Rel. 39324, and one AP at 2.7.0 Build 20200113 Rel. 38287, all managed by the 3.1.2 site.
Help!