Sort of a newbish question

[veeectorm]

Im actually trying to set_power to a particular bulb.

Im able to controll all lights after find_bulbs or get_state, but im not really sure how to set_power or set_state to a particular bulb.

I used to do this on sharph's lifx--python by specifying the bulbs mac address, but i cant seem to do that anymore.

basically, i need to know what "bulbs" i supposed to be set to before using set_power(bulbs, False) or true, or set_state.

Sorry if this makes no sense.

thanks!

[mpapi]

Hey, thanks for using lazylights! It's a solid question, given that the 2.0 branch is so short on docs and examples at the moment.

Basically, set_power and set_state take a list (or set) of Bulbs. There are two ways to get a Bulb:

1. find_bulbs returns a set of them
2. get_state returns a list of objects that each have a bulb field

The latter is the way to go if you want to control individual bulbs:

import lazylights

all_bulbs = lazylights.find_bulbs(expected_bulbs=2)
bulbs_by_name = {state.label.strip(" \x00"): state.bulb
                 for state in lazylights.get_state(all_bulbs)}

lazylights.set_power([bulbs_by_name['Bedroom']], False)

Even if you only want to control one bulb, you need to pass a single-element list -- the exception you get if you pass a bulb in directly currently doesn't make that very obvious.

It's likely that I'll be adding a higher-level interface around some of this stuff in the next couple weeks -- I just wanted to get something simple and working out there for 2.0, and will circle back on it now that I'm getting some experience using it in my own scripts.

[veeectorm]

That's awesome...i was able to work it out!

Something i noticed:

set_state does not set_power, does it? On my(very temporary)script, i had to set_state first, then set_power so as to bring lights to a normal, acceptable color if i set them to red before for example, before turning them on.

CHeers.

[mpapi]

Right -- as far as I can tell, you can still change the state when the bulbs are off, and the change is then visible once you turn them on.

The low-level API I have now basically leaves it up to you to mix and match these accordingly, but I plan on eventually having something that's a little more point-and-shoot.