Här finns lite info!
A BIG shout out to @UI-Payne, who helped me get this resolved and will be looking into the logs I provided to hopefully repro and solve this problem in-house.
Basically, it seems to be an issue that happens with this firmware when on the UniFi network. Assuming it’s due in some way to DHCP or possibly that the fallback settings work but DHCP doesn’t in that FW version. Either way, the solution is to connect the ULTE to a non-DHCP network and then use SCP/SSH to manually update the firmware.
In my case, the step-by-step looks like:
- Set up an old router with IP of 192.168.1.1
- Disable DHCP on the router
- Connect the ULTE and a laptop to that router. (You will probably need a PoE injector to power the ULTE)
- Set the laptop to have a static IP of 192.168.1.19 (or whatever you want as long as it isn’t 1.20 because that is the ULTE’s fallback IP)
- Test ping to the ULTE at 192.168.1.20.
- If that works, follow the instructions here: https://help.ubnt.com/hc/en-us/articles/204910064-UniFi-Changing-the-Firmware-of-a-UniFi-Device#SSH
- Download the program WinSCP. This will allow an SCP session over SSH with a folder structure GUI. Use the SSH credentials to login into the UniFi Device.
- Download the bin file from our Downloads page. Please verify you are downloading the firmware .bin file specific to your device (UAP, USW, USG, etc) and not the UniFi Network Controller software.
- Move the .bin file to the device’s /tmp/ folder by dragging and dropping the file and rename the file to fwupdate.bin.
- Connect via SSH and issue the following command to initiate a local upgrade: “syswrapper.sh upgrade2 &”
- The ULTE should reboot. After the reboot, you can SSH into the ULTE to confirm that the update was applied.
- Disconnect the ULTE from the old router and connect it to your UniFi network.
- Now adopt/update/etc… works fine.
That should get you going. I hope this helps lots of people.