Hey @Gopack2! I have tested your Candle Light Effect Porch 1 and its looks pretty good. I am using it with DimmingCREE lights though (not RGB) and they are a were a little too bright so i brought the random down to 10 & 40 and 30 & 60. Cool work sir!
I made a candle flicker and think I broke the Device?
borristhecat
#25
Thanks @JDogg016 for the inspiration, I got a few more things to try but I added a random low temperature to the mix to make it even more realistic. Great idea!
Edit: actually having a small issue with this, i have osram RGB tuneable white lamps they work fine for about 20 seconds then they seems to stop for a bit then carry on. I think its too much information for ST to process constantly.
@bangali is there a way to have something like, after 10 loops wait for 5 seconds then continue? My thinking is it will then give ST a small breather space to then take the next load. I then have another piston that when i change the mode back to a normal one if its come from this mode wait for 20 seconds before it fires. 20 seconds was enough last night when i tested but if i leave the flicker on for a longer time it has more of a backlog to clear and then that piston doesn’t fire correctly.
borristhecat
#26
Hi @Gopack2 i just learnt from me trying the temperature thing that the randoms are wrong on this level 1 is set at between 35 and 95 % and level 2 is set between 50 % and 125%. I suspect what is wanted is between 35 / 60 and 50/75? if so it needs to be (35 + random(25)) and (50 + random(25)).
Gopack2
#27
Thnls I will adjust and try. What I was referring to with the random though in my question to Bangali was the the random setting of the scene, in my piston with code gyytw. It sets the scen but won’t alway change accurately. It seems to get stuck on a set scene. Even though it’s suppose to be a different one.
bangali
#28
doing a long run of this kind of flickering logic will sort of freeze the light for a while. this may be helped by pairing this sort of flickering with a motion sensor where the flickering only happens for 30 or 60 secs on motion active and uses a slow long fade task otherwise then changes to flickering on the next motion and so on.
just ignore me if you have run this continuously for 30+ mins and dont see this freezing behavior happen enough to disrupt the light show.
Jrrobertson3
#30
@JDogg016 - Sorry about that! Great Idea sir! Gives the front of my house a cool effect!
borristhecat
#31
This is what’s happening too mine but I don’t have any motion detection (untill nest protect allows it anyway, would be so good if they did) so how else could I fix it?
bangali
#32
hmm, its going to happen.
see this post:
i added the first if to manage that a bit. you will have to play around with the values on line 35 and 41. 15 iterations and 5 seconds respectively, seems to work for me.
BTW, in the first if i forgot to set i back to zero. so within the first if block also set i to zero. 
Make a loop for colored lights
Gopack2
#33
.Not really. I’ve tried the wait, I’ve tried moving the set scen variable around. Not triggering correctly. It sets the correct random scene. Bot won’t pass it to lifx reliably. Seems to get stuck on one scene and never changes, even though the variable is changing correctly. Is there a way to see what sb]cene is applied? Something like [porch1,Porch2,Porch3,Porch4: currentlifxScene]
I suppose I could try cases with the variable. Then use the lifxscene value from the dropdon as a way…
bangali
#34
i dont use lifx so cant really try it. but what if you set a 60 second wait timer right after setting the scene and before executing the piston … does that make a difference?
Gopack2
#35
No I pulled the candle flicker piston call out of the piston and same results. I will try later. Been a long day of work and I got three more of them to go… I’m going to try a case method and see if that works better
borristhecat
#37
I think I understand the 1st if part of the piston 
but how would I get it to work with mine as yours is for random colours, isn’t it?
