04-03-2018 03:47 PM
I want to be happy that Belkin has updated the Wemo Link for the KRACK exploit instead of abandoning it like the Wemo Maker.
But I can't. This new version has made the Wemo Link even more unreliable. In the previous release the link would lose one bulb out of 12 every few days. Sick of that I moved all of the bulbs I could to my Hue leaving only 5 on the link - two wemo LEDs and three sylvania. I would still occasionally lose a bulb every week or so. With the new firmware I now lose a bulb most every day and I need to power cycle it to get it back. Pretty much defeats the purpose of automation, don't you agree Belkin?
I want my money back for the link itself, the belkin leds, and the sylvania bulbs you told me were compatibile (and are not compatible with anything else). This thing is not fit for purpose and you're clearly unable to fix it. Who do I contact for an RMA?
04-05-2018 09:13 AM
Still broken, one bulb per day becomes "not detected" and needs to be power cycled.
How's my RMA and refund coming?
04-06-2018 03:32 AM
04-06-2018 03:37 AM
04-06-2018 03:40 AM
04-06-2018 03:49 AM
04-06-2018 04:19 AM
@Jethro327 Apologies. Know that we're eager to help you out in any possible way. We can still have this taken care of by our Escalation Engineers for further diagnosis with the Wemo Link. Please email us at WemoCares@belkin.com along with your contact details (Full Name, Phone Number, Location - City/State), firmware version, community username and a link to this post for reference.
04-06-2018 07:21 AM
@carl_s wrote:@Jethro327 Apologies. Know that we're eager to help you out in any possible way. We can still have this taken care of by our Escalation Engineers for further diagnosis with the Wemo Link. Please email us at WemoCares@belkin.com along with your contact details (Full Name, Phone Number, Location - City/State), firmware version, community username and a link to this post for reference.
"Possible", there's the rub. This firmware bug predates you deciding the link was unprofitable and leaving us holding the bag. I expect it is NOT possible for your engineers to fix this bug. If you can't fix it have the decency to open source and unlock it. Or give me my refund as it's unfit for purpose as is.
Another power cycle needed again today. How could your process allow an unmaintained device's firmware to be made worse with an unrelated security fix?
04-06-2018 04:49 PM
04-06-2018 04:50 PM