"Change color temperature over time" start CT

"Change color temperature over time" does not start at the current 2700 temperature. It starts at 2000 and then advances as expected to 4000.

Actually, when there are multiple bulbs, as in your case, it starts at the color temperature and level of the first bulb listed (not 2000) if that bulb is on. If the first bulb is off it starts at 1500. When there are multiple bulbs it has to pick one to determine where to start for all of them, so the first bulb is the one used.

All of the bulbs were at 2702. These are Sengled RGB. I've been using Set temperature which works well without turning the bulbs on. I was hoping I could get them to smoothly cycle up and down between 2700 and 4000 if they happen to be on when the color change is triggered. I was looking at the log info. I'll turn them on and see how they behave. Could be I'm trying to solve a problem I don't have.
Update:
This seemed to be working until one bulb P1 went to 4000K at the end and turned off. They uniformly went up to 4000k but glitched on the lowering command. If I do just two bulbs at a time it seems to work. I'll do it as two pairs of rules a few minutes apart. Maybe too much zigbee activity once in the same location.

Thought I had it figured out except 2000K came out of nowhere.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.