I bought a UniFi USW-Lite-8-POE switch to play around with before placing a bigger order, but the switch I got is having issues.
I started by downloading the UniFi-installer.exe, and once my switch was recognized, I initiated the adoption process. It reached 99%, but then the UI displayed “process interrupted.” I checked the tips in the provided link, but my only viable option was to click “remove.” This was my first attempt at adoption. I removed the device and was then advised to perform a factory reset, which I did, and the device reappeared. This time, I was able to complete the adoption successfully, and it worked for about 20 minutes until the UI stopped recognizing the device, even though it remained powered on and functioning as a switch. I cycled the power, but the UniFi manager still didn’t recognize it. I performed another factory reset, the device was recognized, but each time I attempt adoption, it shows as “interrupted,” leaving me with the only option to remove it. I cannot get the switch to work. I’m stuck in this cycle of adoption, factory reset, and removal.
This experience has been disappointing. I was considering a larger order, but now I’m questioning my confidence in their product.
I have always found the Windows version of the UniFi software to have issues, mostly because of all the other Windows programs such as third party security tools.
Overall I have had VERY few issues and we buy thousands of UniFI devices. We either sell the clients on a CloudKey for the controller or have them setup a Linux system dedicated to running it.
I think I might have broken something during the initial adoption phase. I didn’t realize I needed to have the UniFi network server setup. After I first got the switch, I was unplugging and reconnecting different ports, and the power cycled as I moved it to a local PC to connect it to my Ethernet port. I was expecting to be able to connect to the switch’s local HTTP server. While talking on Discord, someone mentioned that an update might occur in the background before the first adoption. It’s possible this process could have been corrupted?
I don’t fully understand how the UniFi ecosystem works. While raising my support ticket, I was able to access my local switch through https://unifi.ui.com/. I didn’t realize the devices operated this way. Is it possible to place all my devices on an offline VLAN so they won’t phone home?
The controller has the option of being tied to their cloud, the switches talk to the local controller. UniFi does offer a cloud hosted instance, but they charge for that.
I think I’m going to return that Ubiquiti switch and go with Cisco. The price point isn’t much different it’s only a few hundred dollars more for everything I need, and it’s also available on Amazon. I ordered one of the smaller switches to test it out. It looks like the product on amazon is from the Cisco store, but I’ll confirm that it’s covered under warranty with Cisco once I receive it.
I’ve installed the controller on a Mac and a Raspberry Pi (Linux) without a hitch. Never tried on Windows.
Out of the box without the controller installed, a Unifi switch just acts like a dumb switch.
No need for Unifi to phone home unless you want to use their hosted controller. It’s why I like their self hosted controller. If I hadn’t registered the products for warrantee purposes, they wouldn’t know I exist.
Also know that apart from a couple of features (guest portal, traffic monitoring) once setup, Unifi networking equipment works fine without the controller running. For the first couple of years I just ran it on my laptop when I needed to adjust anything. With pfSense as my router/firewall, it’s been a dream come true.
That’s fair. I’m sure ubiquiti has a good product and it works fine for some users, but whatever was going on with my switch turned me off. I’ve actually decided against getting the Catalyst 1200 and plan to go with the Catalyst 1000 because they come with Cisco iOS.
The 1200/1300 come with some Linux variation not iOS. I’d rather have the option of transferring my skills from tinkering at home to a certification later.
