Door open alert help

#1

1) Give a description of the problem
Piston sending alert when it should not be.

2) What is the expected behavior?
If system armed home or away and door is open for 3 mins then should send off an alert.

3) What is happening/not happening?
It is sending off alerts when system is disarmed.

**4)

image
image.png1178×427 23.8 KB 

10/3/2018, 12:16:22 PM +603ms
+0ms ╔Received event [Home].time = 1538540183510 with a delay of -907ms
+71ms ║RunTime Analysis CS > 22ms > PS > 31ms > PE > 18ms > CE
+93ms ║Runtime (46867 bytes) successfully initialized in 31ms (v0.3.107.20180806) (92ms)
+95ms ║╔Execution stage started
+97ms ║║Cancelling condition #2's schedules...
+98ms ║║Condition #2 evaluated true (1ms)
+102ms ║║Comparison (string) armedAway is_not (string) disarmed = true (2ms)
+103ms ║║Condition #6 evaluated true (5ms)
+104ms ║║Cancelling condition #1's schedules...
+105ms ║║Condition group #1 evaluated true (state changed) (9ms)
+106ms ║║Cancelling statement #4's schedules...
+1572ms ║║Executed virtual command iftttMaker (1462ms)
+1575ms ║╚Execution stage complete. (1481ms)
+1606ms ╚Event processed successfully (1606ms)

This should be really simple but for some reason I just can not see why it keeps sending off an alert. It’s as if condition #6 is just being ignored.

Thanks for the help

#2

Someone please correct me if I am wrong, but I believe with your wording, the status from the monitor is checked at the moment the 3 minutes begins. This is how I would code it to keep the status check happening at the very end of the 3 minutes.

index
index.png1178×499 26.2 KB

#3

By the way, from your log, your house WAS armed at the time the alert was sent to IFTTT

armedAway is_not disarmed = true
is the same as saying
armedAway is armed = true

#4

Yeah that’s what is odd. It was not armed. I will give your piston a crack and see.

Thanks for the help!

#5

Yeah so your piston in a sense still works but for whatever reason still thinks the system is armed.

#6

Sounds like that should be your focus. Have you tried arming it and disarming it and checking the logs?

This sample piston below will not fix it, but if you let it run for a day or so, it will gather easy to understand information in your log. It should write one line each time the Smart Home Monitor changes.

index
index.jpg674×699 76.6 KB

#7

Well for whatever reason seems to be working not :confused:
Not sure what changed, I just armed and then disarmed to test that log piston and now it’s working. Thanks again!