This post made my eye twitch a little, if you are going to run enterprise-grade hardware at home you should come up with a networking strategy/layout before just plugging things into it and clicking checkboxes. One of the biggest features of Unifi, IMHO, is the ability to easily create VLANs and isolate low performance or insecure (IoT) devices from the rest of your network. It may also be beneficial to create a separate SSID that only runs on the 2.4 ghz channel just for these devices. This way certain networking features such as “Auto Optimize Network” won’t try to force them to incompatible bands. On top of all that removing IoT devices from your main VLANs/SSIDs allows you to tune your other networks to your hearts desire without worrying what may break.
p.s. @nlucia if you have a fully configured Unifi setup at home the only thing you should ever be rebooting is at most your cable modem. Unless you’ve upgraded that to better hardware too. Unlike standard consumer-grade hardware that is riddled with bugs and generally has very low hardware specs, Unifi equipment won’t be fixed by a reboot. The only way it breaks it when something is misconfigured, a firmware upgrade goes awry, or rarely when hardware fails. In your case, a new device trying to run the network was added. This is one of the main reasons that server hardware typically runs Linux because things don’t just stop working.