Open reidrichardson opened 2 years ago
Thanks for all that troubleshooting output, however your command actually was turning off the device. Can you provide the same when turning it on?
tplink-smarthome-api setPowerState 192.168.1.81 true
you had "on" instead of "true"
Is there an existing issue for this?
What happened?
When setting the light strip to use a "color painting" and setting it to set to last state for power on, the light strip does not turn on if I do it through homekit. If it is set to a static color, it works as expected. Additionally, it seems to work fine using the official connectors for Alexa/Google Home, but obviously TP-Link supports these.
Same thing happens with the tplink-smarthome-api. It returns true, but the light is Not sure if this is really a 'bug' so much as a feature request for an unexpected lighting effect.
the logs are laid out in the following order 1) How tplink-smarthome-api sees the light strip when it has been set through the kasa app 2) The output returns true if I turn it on through the api command 3) The light info after the command has been ran, but the light isn't actually on
What, if anything, has recently changed?
Nothing other than setting it to use the color painting instead of a day light as far as I am aware
Version
7.0.1
Node Version
16.14.2
Homebridge Version
1.4.0
Which OS/Platform?
Linux
Relevant log output
Configuration