I have found that if you have wifi mesh networking (like google wifi), you can have a lot of fun with Wemo and HE.
- the wemo's I have near my primary google wifi device, will appear to not respond to ssdp
- They can also have a hard time if you reset them them and want to reconnect to your wifi network
What appears to be going on: (first on the setting up the wemo devices near the primary router)
- google wifi advertises both 2.4gh and 5ghz wifi with the same name
- your mobile device used in setting up is likely on the 5ghz network, and during the handoff from the wemo private network to the wifi network, wemo app tells you could not connect.
- google in their don't be evil, are evil in that you cannot disable the 5ghz network.
So to setup the factory reset wemo devices, you need to move yourself, your mobile device and the wemos to be configured far enough away from the primary router that your mobile device switches to 2.4ghz, then with the devices near by to you, you can set them up.
So the next problem is the devices don't discover in the wemo connect app (and sometimes the wemo app). It was strange that a device near the other mesh router would be visible via ssdp, but not the wemo devices near / connected to the primary router.
- in my case I have the 2ndary mesh routers wired back to the primary router in other locations.
- if I move (temporarily) the switches that won't discover, by the 2ndary router, then the discovery works in HE and I can add the devices to HE
So all this gets down to wemo wants 2.4Ghz, and it appears to me google is has issues with 2.4ghz devices broadcasting and that being forward properly from the primary router.
I have seen strangeness in the wemo app thru this, but it seemed to see the device much sooner than Wemo Connect/HE did.
The question I have is if the ssdp returns to not seeing the device, but HE has already configured the device, will wemo connect correctly keep the device working and subscribed?