Securifi Community Forum
Sensors and Home Automation => Home automation => Topic started by: KRC on December 11, 2014, 08:19:02 am
-
I connected a couple of these to my Alomond+ and they work perfect.
-
They do appear to be a good deal that does a good job. One oddity I found was when removing them. They can be removed from the Almond+ easily but will not add back on. You need to reset them at that point. Resetting is done by powering the light (with a normal switch or such) off (wait 3 second), on (wait 3 seconds) and repeat that off/on pattern 5 times. They will blink a few times to report that they are no reset. Then you can add them back in to the Almond+.
-
I connected a couple of these to my Alomond+ and they work perfect.
What firmware are you on?
I read another thread somewhere that they stopped working with a newer firmware.
I'm apprehensive to upgrade since I too have some working and would like them to keep working!
-
Thanks @fillibar for the info.
I'm on R69.
-
I am also on R69. No problem with previous version. I had one that was across the upgrade and 2 added recently.
Hope that tip helps. Found it after digging around GE's site a bit but of course saw it on the Tested Sensors thread for the bulbs after I posted it in this one.
-
Okay so I updated to the latest version and they still work. :-)
I'm excited to start making rules for them so if I turn one on more come on at the same time and so on.
Definitely the cheapest option for switched lights and the brightness and color are really good on them too. IMHO of course.
-
I'm having three GE Link bulbs connected to my A+. After weeks of reliable service I had the first hard crash of my A+, screen went dark, router was completely dead, disconnect / reconnect power brought it back to life. After that all the bulbs still worked, but randomly they became unresponsive. Unfortunately I didn't save the log ... :-[
Now all of a sudden none of the bulbs could be controlled anymore and I had to remove / add all of them which worked smoothly on the first try. Anyone else having similar issues?
-
Sorry, no. Have never had that. Can you readily remove one and add it back in to see if that helps?
-
Thanks fillibar. After removing one the other ones still didn't work. Removing all of them and re-adding solved it. But now I'm not sure how reliable the set up is. Other sensors like a door / motion sensor were still working fine.
-
Now that it has been a few days... has your Almond+ remained stable and the bulbs are still working?
-
Thanks for checking in. Yes, all back to normal. They have been perfectly working for weeks before all went AWOL at the same time.
-
I've had a single GE Link bulb installed and have had no problems with it. (other than someone switching the light off with the wall switch)
I'm looking forward to the automation firmware release with time triggers- Wake me up with a slowly increasing light and I'll be happy.
-
Have you had success automating it? I can toggle and dim mine fine from the app and webUI, but they aren't automating any functions.
-
In 69cb the bulbs should show up in the Rules section... However the really only set the dim value to 0 no matter what. It is a bug in the build. So if you want them to turn off... The rules work great for that. :)
-
In 69cb the bulbs should show up in the Rules section... However the really only set the dim value to 0 no matter what. It is a bug in the build. So if you want them to turn off... The rules work great for that. :)
What do you mean by off? Are you talking you can have a switch turn off muiltiple bulbs, or that you can turn off one bulb in a set and the rest go off?
I can only get them to turn off in rules if it is turned on by motion detector it will turn off after a certain time. Also have it tied to a GE switch that my porch light is on and it will turn one off and on. I have two in a fan I can have them both turn on if I just turn one on, but have to turn them off separate the rule doesn't work for off.
-
I mean that when you have a rule to turn the bulb on, for example based on a motion detector, it sets the dim value of the bulb to 0, so it appears off. Controlling the bulb outside of the Rules beta works normally. As for multiple bulbs... I suppose you could make multiple rules to control multiple bulbs with the same trigger, but I have not tried that and scenes (including controlling multiple things at once) is not in yet.
-
In 69cb the bulbs should show up in the Rules section... However the really only set the dim value to 0 no matter what. It is a bug in the build. So if you want them to turn off... The rules work great for that. :)
You have to set the brightness percentage in the rule. Mine were all defaulted at 45%. I set them to go to 90% on trigger (door open) and 25% or off (depending on which light) on trigger (door closed)
-
You guys are aware that you can have multiple IF's and THEN in a rule, right?
So you can add, say five bulbs in the THEN part and you'll be turning them all on/off when the IF state is true.
-
Yes. Although I only have one bulb per location so that does not help much.
I did run into a scenario that did not work and not exactly sure why...
If time between 4pm and 11:59pm, Motion Sensor = true, Bulb = off
Then Bulb = on
Result: Bulb never turned on.
A similar one:
If time between 4pm and 11:59pm, Motion Sensor = true
Then Bulb = on
Result = Works just fine, so something odd about the Bulb being checked but I did not want it sending commands to it when it did not need to.
-
Yes. Although I only have one bulb per location so that does not help much.
I did run into a scenario that did not work and not exactly sure why...
If time between 4pm and 11:59pm, Motion Sensor = true, Bulb = off
Then Bulb = on
Result: Bulb never turned on.
A similar one:
If time between 4pm and 11:59pm, Motion Sensor = true
Then Bulb = on
Result = Works just fine, so something odd about the Bulb being checked but I did not want it sending commands to it when it did not need to.
We found the issue with bulb actually. We have fixed it and the future releases will contain the updated one.
Thanks.
-
Too bad there is not an open bug tracker we could check for such things. Then again very few companies go that route (a bug section in a forum does not count) so I am not really bothered. It would save you folks the hassle of replying to posts like mine. :)
-
You have to set the brightness percentage in the rule. Mine were all defaulted at 45%. I set them to go to 90% on trigger (door open) and 25% or off (depending on which light) on trigger (door closed)
That doesn't work for me - any action that involves the Wink lights turns them off: Off = turn off; On = turn off; set percent = turn off; set percent and turn on (either order) = turn off. The state in the sensors page doesn't necessarily obey the rule or reflect reality
Further oddness, in my current rule (set percent of two lights, then turn on), they both turn off, but one changes percent to zero, the other leaves it as it was. The sensors status page says they're both on, one at the percent it was on before, the other at zero.
Note I'm using the key fob to trigger the rule, if that matters. It's the only input-type sensor I have to experiment with
-
I have used a motion sensor in addition to the keyfob as a trigger.
-
This has been fixed and will work in the next firmware release.
-
Where can I get my hands on a key fob? These bulbs are great, but having to open up the APP to turn them on is a pain. My wife simply turns the switch connected to the lamp off and then I can't control them using the APP. Could really use a remote!
-
We'll be offering the one we offered to our Kickstarter backers on Amazon, hopefully from next month.