Piston not picking up status properly


#1

Anyone having issues with WebCoRE, within the dashboard, properly showing the status of Smart Home Monitor, but not reflected with a piston that monitors it’s status? This is a new issue, never had a problem with this before…not sure if it has to do with the WebCoRE update today? I double checked and Smart Home Monitor is working perfectly…

I did some more testing and if the state of SHM changes (such as from armed to disarmed, etc.) then I see that message passed to the piston…no problem…so it looks like the way I had it set before doesn’t work anymore.

Here’s what I need:

A piston to monitor SHM status and if the status is in “unarmed” for a certain amount of time, I get notified…like I said, I had this working for many weeks no problem…not sure what happened…any suggestions?

Unfortunately, it looks like if there isn’t a change in the SHM, the piston doesn’t see this?

I also tested this with presence and I got the same results. For example, If XX stays present for XXX minutes, then XXX…that won’t work, because if the presence status doesn’t change, then the piston stays idle…

I know I am missing something basic here, but i don’t know what…


#2

Ok…I think I (partially) got this to work…The issue was WebCoRE wasn’t seeing the status of the SHM, but with the below example, it seems to be seeing it once I look at the logging (I can see that it properly evaluates the status of the SHM…)

The only thing I can’t seem to get working is how to cancel the notification if the presence sensor is no longer not present and/or the SHM status changes (e.g. presence is present should cancel the notification even if the SHM is not in armed stay/away…) WebCoRE is also not picking up when presence is away or not…not sure why. It will pick up the proper status when the piston is first initiated (e.g., after a pause is turned off) but after that, it is not reflecting the presence in the logs…even though ST is reflecting the presence.

In summary, if presence is ‘present’ the piston should not fire a notification regardless of the SHM status. If presence is ‘not present’ but the SHM status is armed stay or armed away, the piston should also not fire. Once the presence is ‘not present’ and the SHM status is not armed stay or armed away, the piston should fire the notification. I’m also desirous of a 10 minute buffer, which I wrote into the SHM status, although I’m open to this being associated with the presence ‘away’ for 10 minutes, if that makes more sense.

Any input on this, please?


#3

Here’s my resolution…Before I could use the SHM status - not the variable version - …but for whatever reason, that won’t work on this particular piston anymore (I’m still using it for other piston scenarios and it works fine…) Anyways, here it is…the only thing I could not figure out is how to put a 10 minute requirement on being away before the piston would trigger, but this should be sufficient…I had to play with every possible scenario to get this to work…lol