I have hue lights and I use [BETA] Hue (Re)Connect - with scene handling. I group my lights together. If you do this, random color for a group won’t work well.
Question
In CoRe, transition to color is not working. Anyone else having this problem? I suspect it’s the DH again.
I’m trying to note details, but I’m still having issues with pages jumping to the wrong areas. In the cases I remember I’ll be creating a rule in expert mode with actions for individual conditions, and then cases for the rule as a whole. I’ll edit the rule actions and once I tap Done it’ll take me to the actions page for an individual condition (which may or may not contain an action).
Something is not correctly saving the parent page so it’s taking you elsewhere when you tap Done. I was running 0.1.114.20160706. I just upgraded to .115. but I haven’t tried creating a piston yet.
Specific color, using the color picker for the actual light, I’ve looked at the recient reports tab, to see the color values it gives, normally a hex value and a hue/sat value. When I use the same values in the the color options of a light. Using the hsl, and add a level, it’s not updating sometimes and others seems like a different color.
So just to test things are working as expected I was going to put in nice and simple RGB values.
I was curious what format the RGB is in, whether is a hex, or and 8bit value or float values… Like (1,0.5,0.5) or (255,127,127) with or without the () etc.
Again thanks for the responses gents apprcectiated.
RGB is a pair of three colors, Red, Green and Blue. Each one has a value between 0 and 255, where 0 means off and 255 full on. Each number is then encoded into two digit hexadecimal representation from 00 (decimal 0) to FF (decimal 255) and simply concatenated with the prefix #.
Red for example is R=255, G=0, B=0, or in hexadecimal format FF, 00, 00. In RGB that is #FF0000
While on the topic of color. I tried Transition to color Random in 10s but the Random or any color I pick gets dropped. I tried it on a Hue bulb. Bug or feature to stop my from messing with it?
I’ve been working with my hue bulbs quite a bit lately, and I can’t get them to behave reliably. Usually, the first time I rune a piston that I built to change colors it works pretty well, although it certainly seems to work better with only one or two lights…not many more. After the first cycle, it seems I really only get the last color to come up. I’ve tried both SetColor and manually setting hue, sat and level…it doesn’t seem to matter. I feel like this is probably more of a hue->ST->CoRE issue that anything else. Maybe just too many moving parts. It sounds like some folks are having success…but not me.
I’ve been getting similar results - first time it gives correct color… second sometimes… third unlikley.
I seemed to have more luck when i used the Reset action first. Also using seperate commands for setHue/Sat/Level seemed a little more consistent… but its ST-HUE intergration i guess that causes the issues. I know some folks have had some success with linking the lights directly with ST hub rather than Via the Hue hub, but if the internet goes down the ST hub is currently pretty redundant. so your lights become so as well a Rule system should be one of the few local processes on the ST Hub.
Ady624 - thanks for the info, so juust use Hex for color input
I see you have control over lowSpeed, medSpeed, and highSpeed in the app, I have a custom device type for lights and fans and would like to see if I can code them to work for these?