12-06-2018 12:11 PM
Following the directions on the link would remove ALL my WEMO devices from HomeKit, which is hardly the result that I am looking for. I want to be able to have all my devices show, and when I get the "Not Responding" on the tiles, it is for ALL my WEMO devices at the same time.
The only fix that works is if I reboot the bridge. The last time that I did a reboot was on Sunday and the devices are all showing up in HomeKit when I checked right now. Eventually they will all show up as "Not Responding" again, just a matter of time.
12-06-2018 04:38 PM
Please allow our Escalation Engineers to look into this further, sabresoft. They can also assist you in checking the latest available firmware of the Wemo Bridge. For us to proceed, please send an email to WemoCares@belkin.com with the following information
▪ your username and link to this thread for reference
▪ model numbers of the Wemo devices connected to Homekit through the Wemo Bridge
▪ model and iOS version of the handheld device you are using
▪ Home app version
▪ your name
▪ phone number
12-07-2018 10:02 AM
12-07-2018 11:30 AM
What is the LED status of your Wemo devices? Is this the same when you're connected to a different wireless network? Please try to use a different mobile device and connect it to your home network and see if the devices will still show as not connected. You can also try to reboot or power cycle one of the Wemo devices for isolation, and make sure that your phone is connected to the 2.4 GHz network.
12-07-2018 12:23 PM
12-07-2018 01:02 PM
The real answer is that belkin made a few poor technical decisions early on. I get the impression most if not all of the original designers are gone and the ones that are left have no idea how to fix things (I suspect most of the dev work is outsourced too).
Wemos use SSDP for discovery which typically will not cross network boundaries. This is especially true between the 2.4GHz and 5GHz segments on routers (even though they're in the same subnet), and often SSDP will not work in mesh networks either. (There's another issue there with how wemos select access points but if yours are not flashing amber that's not the issue). If the wemo is not flashing amber then it's connected to your wifi and to the belkin cloud.
The belkin app itself, when it sees the phone is connected to your home SSID, will use SSDP to find the devices. This will often fail if you're on the 5GHz band and the devices will be marked as non-responding. If the belkin app sees a different SSID, or connects using data, it goes straight to the belkin cloud to control them (this is the root of the "no multi-location" problem). As long as that cloud is up the wemos will be marked as active. Result - no connection at home, success when remote. It's also why renaming your 5GHz SSID can work - the belkin app goes into remote mode even when you're at home, so your device control makes a long round trip out of and back into your home via the belkin cloud servers.
The belkin homebride appears to be built from freeware that is fairly buggy - it doesn't stay up for very long (hence the advice to power cycle it often). It's also pretty much abandon-ware so I would recommend anyone that hasn't bought it not to bother.
12-07-2018 02:30 PM
Thanks Mike for a much more candid response than i have seen directly from WEMO folks. Their suggestion to delete non-responding devices was of no help because when I get "not responding" it is all the devices at once. I have a couple of spare WEMO Minis. Now I know what to do with one of them. Put it in to power the bridge and cycle the power either periodically, or at least when I get a hung bridge (as I can always see the devices in the app and could then reboot the bridge remotely).