Duplicate Notifications

#1

Receiving multiple push notifications maybe three or four

Only one Push notification should be received

image
image.png1093×220 5.39 KB 

2/9/2021, 1:37:18 PM +951ms
+2ms ╔Received event [Door Shutter Down].switch = off with a delay of 82ms
+89ms ║RunTime Analysis CS > 23ms > PS > 5ms > PE > 61ms > CE
+92ms ║Runtime (46707 bytes) successfully initialized in 5ms (v0.3.113.20210203) (89ms)
+93ms ║╔Execution stage started
+110ms ║║Condition #2 evaluated false (11ms)
+111ms ║║Condition group #1 evaluated false (state did not change) (14ms)
+126ms ║║Condition #10 evaluated false (13ms)
+127ms ║║Condition group #9 evaluated false (state did not change) (14ms)
+141ms ║║Condition #18 evaluated false (11ms)
+142ms ║║Condition group #17 evaluated false (state did not change) (13ms)
+156ms ║║Condition #26 evaluated false (12ms)
+158ms ║║Condition group #25 evaluated false (state did not change) (13ms)
+163ms ║║Comparison (enum) off changes_to (string) on = false (1ms)
+165ms ║║Cancelling condition #34's schedules...
+165ms ║║Condition #34 evaluated false (5ms)
+166ms ║║Cancelling condition #33's schedules...
+167ms ║║Condition group #33 evaluated false (state changed) (7ms)
+182ms ║║Condition #42 evaluated false (12ms)
+183ms ║║Condition group #41 evaluated false (state did not change) (13ms)
+197ms ║║Condition #50 evaluated false (11ms)
+198ms ║║Condition group #49 evaluated false (state did not change) (12ms)
+212ms ║║Condition #58 evaluated false (11ms)
+213ms ║║Condition group #57 evaluated false (state did not change) (13ms)
+228ms ║║Condition #74 evaluated false (12ms)
+230ms ║║Condition group #73 evaluated false (state did not change) (14ms)
+243ms ║║Condition #82 evaluated false (11ms)
+245ms ║║Condition group #81 evaluated false (state did not change) (12ms)
+247ms ║╚Execution stage complete. (153ms)
+248ms ╚Event processed successfully (248ms)
#2

Providing a green shot of the piston and log and trace information will help us help you.

#3

Your log is showing what happens when Door Shutter Down turns off, and indicating there is a lot more to the piston than we can see. Actually it doesn’t look like the same piston at all.

What is interesting is what happens before that. Is the piston seeing off, on, off, on, off, on, off, on and so correctly sending four notifications, or is it only sending one and the problem is elsewhere?

#4

Here is the full piston

image
image.png1093×220 5.39 KB

#5

Click the green camera icon on the bottom and share that image.

#6

That really isn’t the piston you ran in the first post. If you ran the above it would have looked more like:

| +1ms|╔Received event [Test Light].switch = off with a delay of 56ms|
|---|---|
|+32ms|║RunTime Analysis CS > 15ms > PS > 5ms > PE > 12ms > CE|
|+35ms|║Runtime (36699 bytes) successfully initialized in 5ms (v0.3.113.20210203) (33ms)|
|+36ms|║╔Execution stage started|
|+43ms|║║Comparison (enum) off changes_to (string) on = false (0ms)|
|+45ms|║║Condition #2 evaluated false (5ms)|
|+46ms|║║Condition group #1 evaluated false (state did not change) (6ms)|
|+48ms|║╚Execution stage complete. (13ms)|
|+49ms|╚Event processed successfully (49ms)|

Your piston is showing lots of other stuff floating around as well as a different device name, like you’d edited a bigger one and didn’t save it successfully. If that is the same piston then I’d suggest deleting it and creating a new one as it is rather corrupted.

#7

it is the same piston, except i updated it a bit, i used to have another action after the notification to wait for 120 seconds then turn of the device. i removed this action

This is the full piston as per the green camera button

image
image.png1178×1192 64.6 KB

#8

Any time you update a piston, you must run a full log (with trace enabled) of the NEW piston, and post that along with the updated piston. Please post a new log (trace enabled) for the piston above.

#9
+0ms ╔Received event [Home].test = 1612953305148 with a delay of 0ms
+77ms ║RunTime Analysis CS > 22ms > PS > 6ms > PE > 49ms > CE
+80ms ║Runtime (46654 bytes) successfully initialized in 6ms (v0.3.113.20210203) (79ms)
+82ms ║╔Execution stage started
+100ms ║║Condition #2 evaluated false (13ms)
+101ms ║║Condition group #1 evaluated false (state did not change) (14ms)
+116ms ║║Condition #10 evaluated false (12ms)
+117ms ║║Condition group #9 evaluated false (state did not change) (14ms)
+137ms ║║Condition #18 evaluated false (16ms)
+138ms ║║Condition group #17 evaluated false (state did not change) (17ms)
+151ms ║║Condition #26 evaluated false (11ms)
+153ms ║║Condition group #25 evaluated false (state did not change) (12ms)
+167ms ║║Condition #34 evaluated false (12ms)
+168ms ║║Condition group #33 evaluated false (state did not change) (13ms)
+184ms ║║Condition #42 evaluated false (13ms)
+185ms ║║Condition group #41 evaluated false (state did not change) (15ms)
+200ms ║║Condition #50 evaluated false (12ms)
+202ms ║║Condition group #49 evaluated false (state did not change) (13ms)
+215ms ║║Condition #58 evaluated false (11ms)
+216ms ║║Condition group #57 evaluated false (state did not change) (12ms)
+232ms ║║Condition #74 evaluated false (12ms)
+233ms ║║Condition group #73 evaluated false (state did not change) (13ms)
+247ms ║║Condition #82 evaluated false (12ms)
+249ms ║║Condition group #81 evaluated false (state did not change) (13ms)
+251ms ║╚Execution stage complete. (169ms)
+252ms ╚Event processed successfully (253ms) 
indent preformatted text by 4 spaces
#10

OK that makes sense now. There isn’t anything particularly remarkable about it though.

What you need to do is enable the full logs in the piston and then activate one of the shutters. That will show what the piston is responding to and what it is doing.

Each batch of logs starts with something like the following:

That shows that the piston has received an event saying that Door Shutter Down switch is off.

What you would expect to see is whatever shutter you activated turning on, which should result in a single push notification. You should then see it turn off again. If that is all you get then the extra notifications aren’t coming from webCoRE.

However if you see a sequence like on, off, on, off, on, off it means that the notifications are being generated by webCoRE. However they are being generated because the switch is being turned on and off multiple times. So you would have to determine why that is happening. Maybe that is normal?

By the way, using the Test button doesn’t help. All that does is run the piston immediately. You need to know what it is doing automatically.