webCoRE does not trigger motion

[ErvinN]

Hi @nh.schottfam
I'd like to ask you for help regarding of the issue I'm discovering last few days when I updated my webCoRE to version 20211120. Some of my pistons stop triggering in case of motions (tested on two different devices, Fibaro and Neo Coolcam). When I checked the motion device I clearly see that motion is active but webcore piston does not reflect to this so finally nothing happens. I also switched on the FULL logs but there are no log entries in case of motion. I was not able to find what changes were made in the version 20211120 and also what changes in the piston code updated on 7th December 2021.
I also tried to REPAIR webcore via HPM but still the same, cleaned the cache and reboot the hub but issue still persist.
Here is one of my piston which doesn't reflect to motion and does not switch light on in case of motion:

[bobbles]

Just an observation but in my experience you need the triggers to be first followed by the conditions.
You could try changing the non-subscribed conditions (those without the lighting bolt in the left hand column) to 'Always Subscribe'. When you do this you will see a ' + ' sign next to the condition.
I think that would be my first thing to try.
I'm assuming from what you said this used to work but it just doesn't look right to me.

[thebearmay]

Couple of things I’d consider trying:

1. Create a small test piston with the devices that does nothing but displays the motion active/inactive status of the device (verifies that webCoRE sees the device correctly).
2. Replace the devices with a dummy device and save the piston. Trigger the dummy device to make sure the piston fires. If successful add the devices back in and save. Retest. (Possible the device entry in the piston may have been corrupted.)

[Pantheon]

This is just my 2 cents.
In your first IF, your triggers (lightning bolts in the left margin) are nested under a condition. You want to keep your triggers ("Time happens daily", "Livingroom Motion" changes) top level with conditions underneath. Also, just FYI...

In your second IF, I think there will be a problem with the triggers "stay inactive" and "switch changes to on". Your particular issue is that you are using stays. That is a special case. It is classed as a trigger but it is a ‘timed trigger’. When the piston evaluates Door contact stays open for 1 minute it will actually evaluate like Door contact is open. If that is true it will set a timer for 1 minute’s time and then return false and continue with the piston. If the door stays open then in one minute the piston will wake up and act like it has returned true for the condition. SO, I suspect you MIGHT have some logic conflicts with timed trigger "stay" and the trigger "Stairs Light switch changes to on", which will be immediately evaluated.

Generally I like to keep my piston trigger/condition structure like...

I think that I would restructure my triggers and conditions.

[nh.schottfam]

I agree with other's comments (as first thing to correct)

• nesting (not level 1 using left/right for level) changes/stays (triggers) within conditions or every blocks, will cause webCoRE tracking of changes to not run on each event (bad).

Also, you can see what the piston is subscribed to for events via

HE console -> apps -> select the piston gear icon

• scroll down to event subscriptions

If you are running a recent HE version, they had a very recent bug on DB issues and asked folks to upgrade to the most recent, so you may want to watch that.

Finally, as fyi, pausing, then resuming a piston (in the webcore dashboard; select the piston then pause, resume) also causes the subscriptions to be canceled and then recreated.)

[ErvinN]

Thank you all for the suggestions. I'm going to perform couple of tests and let you know in case I'll need some additional help.

[ErvinN]

Thanks to you all I was able to fix the issue with this particular piston.
The strange thing with this piston is that it was running fine about a year it just stop working properly few days ago when I went to latest version of webCoRE 20211120 and applied firmware 2.3.0.119.