Possible bug? But similar pistons work perfectly

[Cael]

I have 2 pistons that seem to have a problem even though they are identical to other pistons I have created (different mode changes triggered by time, and different lighting triggered by time). Even creating them new from scratch does not get rid of the problem.
Both of these get this problem either every time an update to WebCore happens, or even occasionally on their own. I would say it happens 1-3 times per week.

The only ‘fix’ needed for these is to click Edit, and then Save. No changes made at all. Then they work until the next time this happens.
Here are the screen shots. These shots were all taken before my ‘fix’ for today. So you can see in the piston that there are Event triggers as indicated by the lightning bolts.

Thanks for reviewing and letting me know if this is a bug or what it might be.

[Baz2473]

Change the
"and" to "or"
On the change mode to home piston.

[Baz2473]

Move your location mode restrictions to before the With actions. On both your pistons.

I think your restriction is causing the next scheduled event (next time) to be ignored because of where you have placed it.

[Cael]

Change the

And

To or

On the change mode to home piston.

Very nice catch. I have made the correction as it is a good one and I hope it solves the problem. It is weird though that it did work fine for several days in a row each week even as it was. But hopefully this was just a weird thing freaking it out.

[Cael]

Move your location mode restrictions to before the With actions. On both your pistons.

I think your restriction is causing the next scheduled event (next time) to be ignored because of where you have placed it.

Thanks! I have made the corrections. Hopefully I am the ‘bug’ here. __

[Cael]

Move your location mode restrictions to before the With actions. On both your pistons.

I think your restriction is causing the next scheduled event (next time) to be ignored because of where you have placed it.

Sadly, these changes did not fix the problem. As of the weekend I got the exact same problem again with only these 2 pistons

I have 2 pistons that seem to have a problem even though they are identical to other pistons I have created (different mode changes triggered by time, and different lighting triggered by time). Even creating them new from scratch does not get rid of the problem.

Both of these get this problem either every time an update to WebCore happens, or even occasionally on their own. I would say it happens 1-3 times per week.

The only ‘fix’ needed for these is to click Edit, and then Save. No changes made at all. Then they work until the next time this happens.

See original post for screen shots if you have any ideas.

.

[Baz2473]

Can you please post a “NEW” green snapshot of both your pistons and I’ll take a look for you.

[Cael]

Can you please post a “NEW” green snapshot of both your pistons and I’ll take a look for you.

Thanks!

I will include the ones that have this glitch and also a similar version that never glitches so you can compare.

Mode change to home - glitches after updates (or other random times)

Other Mode changes - never glitch (had Home mode in originally, but I took it out as it was glitching)

Late Morning Lighting - glitches

Early Morning Lighting - never glitches

[Baz2473]

Ok, so if you take a look at the examples you have posted. You will see that every one that you said glitched happens to have an “Only when” restriction at the top with a location restriction in it.

When the location is not one of the ones in your restriction the piston will not run. Using time as a trigger is tricky because when it happens at the time. It then schedules the next time for the piston to evaluate again. If you happen to change modes to one that is not in the restrictions then the piston stops and won’t run the next scheduled time event.

[Baz2473]

So for the first piston. Move the location mode restriction to directly above the action of “then”.
This way the piston will always run but it will only change the mode when it’s in the correct location mode.

[Baz2473]

In your “late morning” piston. You have the restrictions on there twice. Just simply remove the first set at the very top.

[Baz2473]

Here is what your 1st one should look like.

[Cael]

Move the location mode restriction to directly above the action of “then”.

Hmmmm…I swear I changed these last time…maybe I forgot to save them properly. Thanks so much for being patient with me. I really am the bug in this piston.

[Baz2473]

It’s not a problem. That’s what we are all here for. To help each other
Please do let me know how you get on.

[Baz2473]

If this has solved your query please can you check the tick box on the solution so other people will be able to find the solution easier in future.
Cheers.

[Cael]

check the tick box on the solution

Yup, did it this morning after everything worked and I saw that there was an update to the app. So clearly no more update conflicts.

Thanks!