Guide for Meross (WiFi) deployment in Multiple AP environments
Guide for Meross (WiFi) deployment in Multiple AP environments - Lemmy.World
No one asked for this as far as I know, but I’ve spent a little over a week trying to get a Meross smart product (Homekit compatible, WiFi based) to play nicely in my 2-AP UniFi deployment. In the spirit of trying to build a body of knowledge for others that doesn’t exist only on Reddit, I’m writing down what worked for me with the hope that one day in the future, a weary reader will find it and get help. My setup: - Unifi gateway (UCG-Max) - Unifi U7 Pro - Unifi AC-Pro - dumb switch - Various bulbs and switches from Phillips and Lutron that work over hubs connected via ethernet to switch. (Never had an issue with these) - Meross Homekit compatible, wifi, powerstrip - the problem child. I use Homekit because I like it and it’s good. I run a RPi with homebridge when I need to. The WiFi devices are the bane of my existence, but a large number of available products out there still, sadly, use it. I couldn’t find a power strip that doesn’t. Getting it connected in the first place is a bear. 1st step is to create a separate SSID for IoT devices, 2.4 Ghz only, WPA2 only. Unifi console has a once click switch to set this up nicely for you. This will usually make a successful connection and your device will likely work fine for… a while. The problem for me is that 24 hours later, it would be offline again. The missing step and TL;DR is this: lock the smart wifi device to a SINGLE AP. Unifi lets you do this easily and I’m sure others do as well. DO NOT allow this device to attempt to roam to different APs. It can’t handle it, because it’s stupid. I gave it a static IP as well for good measure. I hope this helps you, weary traveler. If anyone knows of a power strip that’s thread enabled and not WiFi, for under a billion dollars please let me know…
