Louis Opter
Louis Opter
I'm not sure what you mean by block, I just want the state of the bulb to reflect the transition in real time.
I mean, yes as in LightState should reflect the transition in real time.
Ah I [did notice that](https://github.com/lopter/lightsd/commit/da9c1bb7e38e10c8122338df50a214b289d0a040) however I'm clamping the value to 0 or 0xffff (I think I have seen some LIFX code do the same thing) since the documentation explicitly...
Hmm, I think I get it, SetPower is just misnamed, it should be named SetBrightness am I correct? Edit: Hang on, I'm confused.
Ok, here is how I get it: SetPower is indeed SetPower and works in a boolean way. However StatePower does uses the full 0-65535 range, and its value isn't related...
No worries, lightsd will implement it in a correct way, you can actually see my work in progress in the lightsd-mq repository.
Hello, Sorry for the response time, will try to do better moving forward. > Conceptually, I don't think parse_amount is better than parse_float: I'd expect all numbers in the statement...
Hello @kedder, I'm wondering if you had some time to ponder that, especially about breaking the API which I thinks is (unfortunately) the right thing to do here. Happy holidays!
> Can we declare `parse_float` and `parse_int` deprecated (but still working) and recommend using new and shiny parse_amount instead? Enlightened plugins would switch, old ones would work as before. Sure,...