I have never had such a bad experience with a product! And now that I look back at these posts there are some from last year that are having the same issues. LAST YEAR!!!!! Rules disappearing!! This is extremely frustrating. Anytime I group bulbs together, I cannot assign a rule to them because the rule disappears. So Wemo support says this was supposed to be fixed with the last update --- it wasn't! How many other times was this supposed to be fixed? I was given a replacement Wemo Link device to see if that was the problem -- still not working! I just don't understand how a product can be such an epic fail. Who engineers these things? Monkeys? 12 year old children? It baffles me how this can be going on for over a year now and maybe even longer and Wemo STILL can't get it right! Worst thing is that I'm stuck with them --- Wemo Link and 16 bulbs because it's way past my 14 day return policy from where I purchased them. Don't even bother buying Wemo Light Bulbs. I'm going to make sure that this product is negatively advertised all over social media. EPIC FAIL!
My daughter started suddenly to have fear of the dark. I bought WeMo Lighting set with a hope that I could create a system that fades out lights without her noticing. BUT I wanted the light to stay on all the time. So Sleep fader doesn't quite cut it, because after the fade, light is switched off.
API for the lights is not open so I can't even write the feature myself.
IFTTT channel is very limited too. There is only Sleep fader and dimming the light without steps.
Technically feature like this should be really easy to implement. For example there already is Dim the light - action in IFTTT. Optional parameter for the fading time needs to be added. Also 10% steps for the light brightness are too coarse. In my specific case I need something like "Dim from the current brightness to 1% in 45 minutes."
As a computer graphics developer, I also dream about support for different interpolation curves than just basic linear. For example I might want the lights to dim quite fast at first and then slow down - or vice versa. But that is very advanced and probably useless for 99.9% of the users.
The Wemo IFTTT chanel the Wemo App need to enable color rules for tunable LED lights. For instance, it should be possible to chagne the color temp of the Osram white tunable light LED light according to a schedule or an ITFFF trigger.
Which is great, but it would be nice to add a 'toggle' option.
This is already available in the IFTTT integtation, but would be better to have it locally too as it's a bit more reliable!
I have my sun blinds connected to a WeMo Maker - and at sunset I'd like to 'reverse them'.
If it's been hot and sunny and they are closed to stop the house turning into a greenhouse - I want to open them to cool the house. If it's been normal day and the blinds are open I want to close them.
I have other uses for toggle where I've integrated WeMo maker into my own circuit and so would just like to switch state.
I too would like to be able to make rules that allow me to link two switches together.
What I would really like is for my Lightswitch to be able to control other switches.
Example: I have a Lightswitch controlling the recessed lights in the livingroom. I also have a Switch hooked up to a lamp. I would like it if when I pressed the Lightswitch that both toggled.
IFFT tries and fails at accomplishing this. I wonder if it would only work if it is initiated by the app and not switch?
This would also help in creating 3-way switches.
Example: I have a Lightswitch for my outside lights which is located downstairs. I would be able to hard wire a Lightswitch that is not actually hooked up to a light upstairs and use it to control the outside lights.
I have been looking for a wireless lamp socket (standard base) for at least three years. I mainly want to control the individual recessed lights in my family room for various functions and times of day (reading in one of several chairs, watching TV, playing games, etc). I do not want wireless bulbs as the selection is always going to be very poor (or at east for the next 10 years or so). With a wireless socket, I can chose color, and beam angle for each location on the same circuit, timing them and turning them off as needed. THe controller can be phone based, desktop or wall based.
byPeterJameson08-13-201509:27 AM - edited 08-13-201509:33 AM
Dear Belkin Developers of WeMo
Thank you for the latest version of the WeMo app for Android Belkin, although I must say that I really can't see much difference. What a pity that you didn't address some very simple issues that go on and on update after update. These are many, but include:
*Making the setting of timed rules function in just one time format instead of switching back and forth between 12 and 24 hour at different stages of setting up.
*Making the "Delete Rule" button further up the screen so that it cannot be pressed accidentally whilst pressing the Android back-button.
*Making the "Delete Rule" button show an "Are you sure" message rather than deleting instantly.
*Providing screen rotation for tablets.
These are just a few tedious and annoying issues that always seem to be ignored by you. They are all simple, and would be easy to implement I'm sure. They have all been mentioned by me to Belkin staff before, but nothing ever happens.
I shall watch eagerly to see if you reply to this post. No doubt many others will too. If you do not reply then we will all have our fears about Belkin's apparent lack of care confirmed, and that would be very sad.
It'd be nice if a single grouped LED could still be controlled individually via the App. I guess that's wishful thinking considering all the other problems with the app, though.
It's better but far from what it should be! It's REALLY irritating when you press a button and the app scrolls and ANOTHER button is pushed! "Sorry Sweetheart, I didn't mean to turn on the bedroom lamp and wake you!"
I understand "rescanning for devices" but have Belkin App programmers ever heard of BOOKMARKING? Why does the display have to go back to the top only to have you hit a rogue button???
I started using WeMo as an entry point into home automation. Recently, I have been forced into using a lot of different third party applications to get the interface and performance that I had always wanted out of the offical WeMo application on both Android and iOS. I tend to use my iPad to interact with any sort of automation when I am lounging around the house, but when I come home from work I still want that same experience on my Nexus 6 when I walk through the door.
I had a little free time at work this afternoon and took about 15 minutes to do some mockups on what I believe would be a good direction for Belkin to take the offcial WeMo application. Since I did not put much time in these at all, I'm sure there are some things that do not strictly follow platform specific design guidelines, however, I believe they are a decent start to get an updated design for the offical mobile applications.
I understand Belkins does not carry outdoor RGB LED Flood Lights (wish they did!) but anyone know if it is doable to modify a regular remote controled RGB LED Flood Light to be managed by the Wemo App?
I'd like to be able to configure a pin (ex 4 digit code) for toggling on/off a specific device. I've had to stop using my Maker for the garage door because my wife has accidentally pressed it a couple of times. She wasn't a big fan of being home alone with the garage door wide open.
You should be able to set the pin per Wemo device when in the Wemo app "edit" mode. There should also be a toggle for "always require pin". This would force a user to enter the pin to change the state. If this option was not selected, when prompted for the code in the app - the user could select a "remember pin" so that individuals could not toggle state without specific intent to do so.