device XYZ is not modifiable. Device is set to off
00lex opened this issue · 9 comments
Hi Kosta!
Maybe you remember my comment:
#17 (comment)
In rules, I can fix this by adding a delay for the 2nd part "change color", but sometimes and I don't know why, pimatic throw errors anyway.
maybe you can change the behavior of the raspbee plugin how to interact with turned off lights when you change the color first.
you can reproduce this easily by changing color OR color temp of a turned off light and the you get:
if you try this in deconz, deconz will turn on the light automatically and change the color.
this already worked with the hue-zll plugin.
yes, I think we can live with that behavior, but if you know what's wrong and its not a big deal, you can fix this in a future update.
thank you
hi,
no problem, i can implement it.
the deconz api does not allow changes when the lamp is turned off.
i don't know how other APIs manage this. but the simplest thing is,
that switched off lamps go on when you change the color values.
the deconz api does not allow changes when the lamp is turned off.
i don't know how other APIs manage this.
i don't know. sure? you could look what hack hue-zll use to bypass this
the deconz api returns a forbidden response.
i have looked. the hue plugin also simply sends the two requests one behind the other.
i will add this to the next release.
@00lex you can close the question ;)
https://github.com/markbergsma/pimatic-hue-zll/blob/master/hue-zll.coffee#L542
muchas gracias!
de nada
https://github.com/markbergsma/pimatic-hue-zll/blob/master/hue-zll.coffee#L542
hey kosta, I don't understand this, but i was not inactive.
I ask someone how he fix this, but read yourself:
ebaauw/homebridge-hue#515
its rather far-fetched because of homekit, but maybe you'll see the light.
sry if im a little overengaged. do what you think is right. you are the cook :)
version 0.1.5 published
now the plugin switch the lights on when parameters are modified
(with the same request)
works! thank you again