Heya guys,
Running some tests (against TP-link LB130) and I’ve found that turning the bulb on using the “light.turn_on” domain-service doesn’t accept any “data”, so the brightness, white-temperature, color, etc… are not going through unless the bulb is already on.
Which confuses me since the Kasa application turns a light on as red.
So, I am thinking that the Kasa app sends the settings first, and then turns the light on (eg: change color to ‘red’, then turn the circuitry on to turn on the LEDs)… Only homeassistant doesn’t seem to like trying to send data to a light without it already being on… Which seems strange to me - the device is there and listening, why wouldn’t you be able to send it a command to either get stuff (like wattage / status) or to set stuff (like set the color in preparation of turning on) ?
But anyway, I was wondering if it was an issue with me specifically or if anyone else had noticed that the data section doesn’t seem to be getting done in the 1 “call service” node, and would actually take 2 of them (1 to turn on, the other to change the color).
Also, with TP-link bulbs, they save the last state they were in, so it has an option to come back on with the last color it had/has in that storage (a setting that can be changed through kasa, without turning the light on, and if the network goes down then bulbs still obey it).
Perhaps I’ve missed something here?
Maybe I should be using a different service / domain?
–
Paul Sanders