Capture and restore attributes

#21

My only clue was that I notice I get inconsistent hue performance to the ones closest to my wifi access point when the channels were too close.

#22

never had any issues. all my bulbs work fine being controlled directly (through st not using webcore, thru hue app, thru google home, ifttt, etc)

#23

i have tried your last piston and it doesnt work… have you tried having your bulb in colortemp mode? change the buld to 3000k or warm white using google home. test your piston and watch what happens

#24

I don’t use Google home and most of my piston interaction with color bulbs are using HSL which I find more reliable.

#26

ok, but that is not a viable solution to stick with hsl. even with the st app. if you open the bulb and set a color temperature of 3000 or whatever, it moves the bulb to ct from hsl. same thing if the hue app changes the bulb to a color temperature. if the bulb would update its hsl to match the colortemp this wouldnt be an issue, but it doesnt

sorry double post

#27

I tried it at ~3003K…

1/31/2019, 10:54:11 AM +283ms
+3210ms	║Current Values: Hue: 86 Sat: 42 Level: 100 Switch: on
1/31/2019, 10:53:57 AM +849ms
+151ms	║Current Values: Hue: 86 Sat: 42 Level: 100 Switch: on
+4367ms	║Current Values: Hue: 302 Sat: 60 Level: 43 Switch: on
#28

And?

Are you in front of your bulb? because neither of those hsl values are warm white @ 3003k
i am telling you… if you use the color temperature slider, it does not change the hsl values

#29

I’m looking at the bulb via blue iris

#30

its close bu its not 3003k. what dth/smartapp are you using?

#31

Untitled
Untitled.png824×231 7.14 KB

here you can see me change color to some blue using app, then 24 seconds later to 3002k with app…

note the data… no adjustment in hsl for color temp

#32

ST must have assigned this by default.

image