CoRE - Get peer assistance here with setting up Pistons

It has been discussed before, I think, that set color has dual action changes color and level. Is your level or color most important to you, or both transitions are a must?

I don’t understand the question. You’re right of course that Set Color sets hue, level, and saturation. But it’s irrelevant in this case, I think. All that piston does is, first, set the initial conditions (level and color). That works just fine. Then I tell it to transition to Warm White over the course of a minute. That doesn’t work at all. It seems to me that it should.

I see, you’re right, it appears to be a bug, and you’re also right about the 60 seconds, at minimum it’s confusing that you are not warned that it cannot exceed 60s @ady624 do you need more logs?

That’s a great idea! Have been testing something similar, but just gradually bring up the level, not the color.

I did get this working last night…

3 Likes

This works great. All of the lights change at the same time…

The only problem I’ve had is that the loop disdies not always break when the switch goes off. It takes several tries.

BREAK is part of WHILE or FOR loops, won’t work with repeat whole action - I mentioned before, a solution is required to stop that repeat whole action thing. Maybe a total count, or a break condition. BREAK does not currently affect the repeat.

1 Like

Transition to color is a custom command of Hues. I’ve found that some hues implementation require 10ths of seconds as time parameter, some seconds. Try varying the number, try with 1, see if it has any effect - be patient, I think I multiply that with 1000 because my DTH wants ms…

1 Like

I think I have the piston working for arrival and really like the wait command I had never used it before.

I will still need to figure out a separate piston for motion but this helps a lot.

Thanks,

Scott

If you want the fade to happen 7 minutes later, you need to put the Wait 7 minutes in a task right before the Fade, within the same action. It won’t do anything on its own.

Yeah, something is working. I noticed that sometimes the end color comes on, but I was’t able to get it to gradually transition…Oh well…

Gotcha… I think I understand… I will adjust it later tonight and see if I can figure out how to build it.

Thanks

Sorry to qutoe myself, but, I could never get that to work the way I thought it should. So, I retried, using WAS NOT for 3 minutes instead of wait.

If any of Pres1 or Pres2 changes to present (trigger) AND Each of Pres1 or Pres2 is present (condition) AND Time is Day --> set mode to day OR Time is night --> set mode to night ELSE-IF Pres1 WAS NOT present 3 min --> set mode Pres1Away (cancel on piston change) OR Pres2 WAS NOT present 3 min --> set mode Pres2Away (cancel on piston change) OR Each of Pres1 or Pres2 is not present --> set mode AllAway
But, this way, the ELSE-IF never executes. Does the WAS NOT fail because the trigger is long past gone by the time the period of “WAS NOT” is satisfied.

Any better ideas on how to do this?

The state of an ELSE IF piston will be true if any of the two conditions (IF or ELSE IF) is true. Use a latching piston on the first version and it will work. Then the piston is true if the top IF is true, false if the BUT IF is true.

1 Like

Ady, can u elaborate on how to get this loop to stop? I have mimicked bamarayne’s rule and I cannot get it to stop.

Go into the dashboard and pause the piston. Our delete it.

OK, but what about his suggestion for a conditional break? Or a total number of count times. Did you get this figured out yet?


I’m trying to set up some special color selections for the Hue bulbs in my front yard, based on holidays.

What I’ve written is basically:

Simple piston:
If time
Then -> follow up piston (1)
Else, basic warm white lights on

Follow-up piston (1)
If anytime during specific dates, if true action -> follow up color piston (2)
OR
If anytime during this other specific dates, if action true -> follow up color piston (3)
ELSE nothing

Follow up color piston (2)
If - nothing
Then - makes lights these colors

The idea is that different dates execute different specific follow up color Pistons.
BUT, I can’t get the color Pistons to fire. Is it because there’s nothing in the IF statement for the color piston?

Anyone have another way to do this??

I would use a follow up instead of repeat whole action

I just got home from work. I’m gong to mess with this and I’ll post what I find out.