Ge Link Bulbs

[fillibar]

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.

[rldreams]

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)

[LGNilsson]

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.

[fillibar]

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.

[Pradeep]

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.

[fillibar]

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.

[Mishakim]

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

[fillibar]

I have used a motion sensor in addition to the keyfob as a trigger.

[LGNilsson]

This has been fixed and will work in the next firmware release.

[jnowland]

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!

[LGNilsson]

We'll be offering the one we offered to our Kickstarter backers on Amazon, hopefully from next month.