1) Give a description of the problem
I have a simple piston that uses both the Smartthings and the webcore presence sensors to Set Present or Not Present for a third “Master” presence sensor. I do this to fix the few times where one would not update at all or for a long time. Recently about once a week my webcore presence sensor goes away -> Home -> away in just under a second. My piston ends up not doing as expected. I think I need to put in a counter, or a lockout timer, etc. but I’m not sure if that would work either. Since these events happen so fast, its actually failing to complete the last step. I dont mind adding a little bit of a delay, but I dont want to delay too much, i have other pistons that are tied to the master piston, and I dont want to have to wait for an extra 10 seconds for a gargage door to open, or doors to unlock, etc.
2) What is the expected behavior?
Piston is super simple
If any of Webcore or Smartthings changes to Present, then set Master to Present
else if any Webcore of Smarthings changes to Not present then set master to Not Present.
3) What is happening/not happening?
Webcore changes to away, present to away very quickly causing the piston not to complete.
Here is a timeline from the three devices in IDE
2018-03-26 8:09:51.364 AM EDT - Smartthings Not Present
2018-03-26 8:09:51.821 AM EDT - Departed Command Sent to Master Presence
2018-03-26 8:09:51.834 AM EDT - Master Presence Set to Not Present
2018-03-26 8:10:43.985 AM EDT - Webcore Not Present
2018-03-26 8:10:44.001 AM EDT - Webcore Present
2018-03-26 8:10:44.443 AM EDT - Departed Command Sent to Master Presence
2018-03-26 8:10:46.971 AM EDT - Webcore Not Present
2018-03-26 8:10:54.544 AM EDT - Arrived Command Sent to Master Presence
2018-03-26 8:10:54.562 AM EDT - Master Presence Set to Present