you might as well send the command to lock the door 
Isn’t that desirable? If she DOES lock the door, then you don’t want to scream at her, right? I think that behavior is actually desirable, apart from the user’s desire to see pistons running 
It’s a dumb joke between my wife and I. It started with a piston that runs when we both leave. It sends a message that says Bye Felisha. Those who have seen the movie Friday will get the reference. The joke has spiraled out of control since then.
@ady624 Any thoughts on my issue? I cannot fix the expression, it will not come up when I click on it and the only way to fix it on my side is to delete the entire section of the piston that has the expression. The down side is every section has an expression which means I will have to rebuild every piston.
@ady624 Hello, it looks like my variables are working except for one of them. rainPrecipitation is not working any more and it was. Could you possibly take a look at it and see if something got out of place? Here are some pics to help
This is the piston, all work except for the rain.
This is my core variable to show it is working in core.
Here is webcore showing it is not set.
Did you try Logging the output of percentPrecip to see if there’s actual data?
That is why I showed the core piston registering at 80% 2nd screen shot.
Maybe this is one of those outputs where it’s coming in as a string? Have you tried setting the variable from expression decimal([Weather Station:percentPrecip])
I have had it set to decimal for 3 weeks and everything was working perfect, until the last update,
Not sure what to tell you, this is beta and finding quirks is half the fun
And the other half is nagging @ady624, who has always been one step ahead of any bugs so the next person doesn’t trip over. 
Yep, you are correct. That is also why I only paused all of my core pistons, takes 5 seconds to fix my issue for now, unitl @ady624 finds the bug, lol.
How do I save the mode of my thermostat to a variable? Just testing at the moment, so I’ve got a virtual button that when I press it, it should save the mode to the variable and turn off the thermostat. When I press it again, it should use the variable to set the mode of the thermostat back to what it was before… Any help would be appreciated!
All that’s showing in the variable is "Thermostat 1’s thermostatmode. Logs are showing it’s setting the mode, but it’s setting the mode back to off… like it’s not saving the mode in the variable, just a pointer back to the mode…
Im Im a little confused should i upgrade or not?
This is this not a good thing?
Well, it depends. It is the right thing, but it could create problems. If you have a piston that uses bulbs and the bulbs are unavailable, they may not take the commands you are sending. I know in the past, even if the bulb was showing unavailable in the Hue app, the ST app was showing them as available and the piston would work. That may have changed with the new update. This is purely a red flag, as I didn’t get a chance to actually test.
This piston is using up 53% memory. Although doesn’t seem a problem, it surprised me given how short it is. What is it that’s chewing up the space? In fact, in general, how is memory usage driven? In old CoRE I would have written this as 2, 1 for turn on and 1 for turn off. The turn off would have been on turning off wait X minutes and cancel on piston state change but I thought the off for X minutes would generate less traffic in the event history so gave it a try.
What @anon36505037 said, see below from Adrian’s previous reply on the subject.
@destructure00, i missed your reply the other night. thank you for the example and information.