Webcore Motion Lights Issue

webcore

#1

Is anyone else having issues with their webcore motion lights turning off because the piston doesn’t reset on new motion?

I know with the old CoRE there was a race condition that could be created between the piston and the motion sensor, but I never saw issues as frequently as I do with webcore.

It seems like an IF MOTION ELSE DELAY OFF piston doesn’t reset on new motion that occurs between the ELSE and OFF.


(Robin) #2

Can you post a piston screenshot using the green snapshot button…

Default for a webCoRE piston is to cancel the ELSE on condition change… maybe you changed the default cancellation policy?


#3

Nope, didn’t change the default cancellation policy, but your comment released the brainfart of what I DID change.

I refactored it months ago to an IF Motion State Changes THEN SWITCH(Motion State). Evidently pistons don’t like this and it leads to some pretty funky control behavior vs an IF-THEN-ELSE. Being at home for the holidays is just exposing the issues.

Trying to get a bit too creative. Reverting back to IF-THEN-ELSE.

Thanks.


(MS) #4

Bahahahahahaha!!!


(might be my fake name?) #5

So @RobinWinbourne was kinda like a laxative for you?


(Robin) #6

I guess I’ve been called worse things over the years…

At least you didn’t call me a douche!!


#7

Okay, so reverting to the IF-THEN-ELSE actually did not work.

I actually removed my “changes to” and went with an “is” comparison structure. That fixed it. Now I have to figure out what borked the old code which used to work properly.

Ref: https://community.webcore.co/t/motion-sensor-not-always-firing-right/2861


#8

Here’s the snapshot, btw. The one I was working on was gone, so I just pulled from another piston that used the piston in question as a duplicate base.

I’m guessing the problem lies in the variable usage or the manual mode trigger.


(Robin) #9

Try this:


#10

So, with y9n6, the motion trigger is removed. I’m going to add an On Event.

The really confusing thing to me is this:

  1. Motion changes to Active and piston sends a SetLevel, and the dimmer shows 2x On events.
  2. The piston then sends an Off exactly 60 seconds later, before Motion changes to Inactive.

This used to work fine, so I’m really not sure where the problem is a this point.


#11

Things are getting worse. Webcore seems to be a bit fked up lately. Pistons are now completely missing events. Multiple motion lights setups that have been working for months are suddenly not working or frequently missing events.


#12

I have the same issue, been updated to latest version of website, ALL the motion sensor lights piston suddenly not working. Anyone got some info regarding this issue?


#13

Mine are fine. Are you sure it’s not a problem with your motion sensor?


(Lee Florack) #14

Things are working fine for me with all motion sensors and all webCoRE pistons.


#15

Thanks for the reply. Yes, the motion are detected normally in SmartThings. I can post the piston and log when I am with my machine.


#16

Here is my piston that used to work prior to the webcore upgrade. Thanks.


#17

Spend sometimes to investigate and realized that the lifx integration has been dropped in smartthings app. Just reauthorize and lights rules back to normal.

Thanks all.