I am not sure what happening with my web core. Lately none of my pistons are firing completely. Some will only trigger some lights; some will turn lights on but not others off.
Any ideas on why certain things do and don't work? Also, it's not the same devices each time. I have one piston that is set to turn on a night light and two bedside table lights. One night the night light will be on and none of the bedside table lights, the next night, the night light and one of the bedside table lights. Its completely all over the place.
Logs would be helpful for the piston to see what is happening
I'm lurking on this one.
I have a piston that doesn't turn on Sunset +60 anymore and my son has 2 bathrooms that, as far as I can see remotely, have the motion event and commands to the switches but nothing happens. This happened to him going to .152 yesterday and I feel my piston stopped working when I wne to .152 a while ago as i'm a beta tester.
Several ideas. As @nh.schottfam suggested, logs will be your friend in isolating where the chain of events breaks down. Otherwise, it is tough to tell if a trigger was received, condition or logic processed as expected, or an output command was lost in a mesh issue.
I also make liberal use of piston states for an abbreviated look at behavior and timing. It takes careful syntax, but allows me to quickly scan dozens pistons for anything odd. That might be a whole other thread, though.
