Two Push Notifications when Piston executes


#1

I have recently received my Samsung Hub 3 and two sensors, a EcoLink tilt sensor for my garage door and Samsung Leak Sensor.

I have set a couple simple piston and Im having random times when the piston is executing twice and sending multiple notifications.

This is issue is happening with both sensors. As you can see below I have tried using a variable to stop the second notification but this did not work. I also saw another post that indicated enabling parallelism helped but neither of these work for me.

My feeling is that its one of two things

  1. I originally had the new Smartthings app installed until I realized that Webcore only works with classic app. So I installed classic but realized that with both apps installed I was getting double alerts from a piston. I then uninstalled the newer app and no longer receive alerts from it. Is it possible that somehow Im receiving two alert from the classic app because its still thinks the newer app is running?
  2. Hub 3 is new and there is a bug with webcore?



#2

Any chance you set up a custom alert(s) for these devices in Smart Home Monitor with the same push notification message?

I have both apps installed and I only receive one push notification in each app.

Technically, webCoRE does work with the new app except for the Smart Home Monitor in that app. Webcore can only control SHM in the Classic app.

If you open the device in the Classic app and click on Smartapps in the upper menu, you will see all pistons, shm custom alerts and any other Smartapps that are associated with that device. You can click on each one to open and explore to see if you have set up other push notifications


#3

Nothing else configured in SHM, I even tried changing the message the push notification sends and both alerts I receive have the change in the message.

Plus, the logs for the piston shows two messages being sent.


#4

I must be blind. the logs you posted, I only see one push notification :slight_smile:


#5

is @MGDO defined in settings?


#6

Its a Global variable
image

It looks like the logs were cutoff. Here is another example

11/13/2018, 4:56:06 PM +459ms
+0ms ╔Received event [Home].:5153e9ca82d05b5aef5485c5a4abbf01: = @MGDO with a delay of 89ms
+64ms ║RunTime Analysis CS > 15ms > PS > 30ms > PE > 20ms > CE
+67ms ║Runtime (38223 bytes) successfully initialized in 30ms (v0.3.108.20180906) (65ms)
+68ms ║╔Execution stage started
+83ms ║║Comparison (enum) closed is (string) open = false (2ms)
+85ms ║║Condition #2 evaluated false (11ms)
+86ms ║║Condition group #1 evaluated false (state did not change) (12ms)
+88ms ║╚Execution stage complete. (21ms)
+90ms ╚Event processed successfully (91ms)
11/13/2018, 4:56:06 PM +206ms
+1ms ╔Received event [Main Garage Door].contact = closed with a delay of 1155ms
+91ms ║RunTime Analysis CS > 17ms > PS > 48ms > PE > 27ms > CE
+93ms ║Runtime (38203 bytes) successfully initialized in 48ms (v0.3.108.20180906) (91ms)
+95ms ║╔Execution stage started
+105ms ║║Comparison (enum) closed is (string) open = false (2ms)
+107ms ║║Cancelling condition #2’s schedules…
+108ms ║║Condition #2 evaluated false (8ms)
+110ms ║║Cancelling condition #1’s schedules…
+111ms ║║Condition group #1 evaluated false (state changed) (10ms)
+114ms ║╚Execution stage complete. (19ms)
+115ms ╚Event processed successfully (115ms)
11/13/2018, 4:54:11 PM +805ms
+2ms ╔Received event [Main Garage Door].contact = open with a delay of 260ms
+10227ms ║RunTime Analysis CS > 33ms > PS > 10169ms > PE > 25ms > CE
+10228ms ║Piston waited at a semaphore for 10116ms
+10231ms ║Runtime (38286 bytes) successfully initialized in 10169ms (v0.3.108.20180906) (10227ms)
+10232ms ║╔Execution stage started
+10244ms ║║Comparison (enum) open is (string) open = true (3ms)
+10246ms ║║Condition #2 evaluated true (7ms)
+10252ms ║║Comparison (boolean) false is (boolean) false = true (2ms)
+10254ms ║║Cancelling condition #7’s schedules…
+10255ms ║║Condition #7 evaluated true (8ms)
+10256ms ║║Cancelling condition #1’s schedules…
+10257ms ║║Condition group #1 evaluated true (state changed) (19ms)
+10261ms ║║Cancelling statement #3’s schedules…
+10268ms ║║Executed virtual command [Main Garage Door].setVariable (2ms)
+10285ms ║║Executed virtual command [Main Garage Door].sendPushNotification (12ms)
+10291ms ║║Executed virtual command [Main Garage Door].wait (1ms)
+10293ms ║║Requesting a wake up for Tue, Nov 13 2018 @ 5:54:22 PM PST (in 3600.0s)
+10299ms ║╚Execution stage complete. (67ms)
+10301ms ║Setting up scheduled job for Tue, Nov 13 2018 @ 5:54:22 PM PST (in 3599.994s)
+10316ms ╚Event processed successfully (10316ms)
11/13/2018, 4:54:12 PM +135ms
+0ms ╔Received event [Home].:5153e9ca82d05b5aef5485c5a4abbf01: = @MGDO with a delay of 133ms
+99ms ║RunTime Analysis CS > 19ms > PS > 53ms > PE > 27ms > CE
+101ms ║Runtime (38216 bytes) successfully initialized in 53ms (v0.3.108.20180906) (100ms)
+103ms ║╔Execution stage started
+121ms ║║Comparison (enum) open is (string) open = true (2ms)
+123ms ║║Condition #2 evaluated true (13ms)
+130ms ║║Comparison (boolean) true is (boolean) false = false (2ms)
+132ms ║║Cancelling condition #7’s schedules…
+134ms ║║Condition #7 evaluated false (9ms)
+135ms ║║Cancelling condition #1’s schedules…
+136ms ║║Condition group #1 evaluated false (state changed) (27ms)
+140ms ║╚Execution stage complete. (38ms)
+142ms ╚Event processed successfully (142ms)
11/13/2018, 4:54:11 PM +795ms
+1ms ╔Received event [Main Garage Door].contact = open with a delay of 298ms
+99ms ║RunTime Analysis CS > 26ms > PS > 52ms > PE > 21ms > CE
+101ms ║Runtime (38208 bytes) successfully initialized in 52ms (v0.3.108.20180906) (99ms)
+102ms ║╔Execution stage started
+114ms ║║Comparison (enum) open is (string) open = true (2ms)
+116ms ║║Cancelling condition #2’s schedules…
+117ms ║║Condition #2 evaluated true (9ms)
+124ms ║║Comparison (boolean) false is (boolean) false = true (2ms)
+126ms ║║Cancelling condition #7’s schedules…
+127ms ║║Condition #7 evaluated true (9ms)
+128ms ║║Cancelling condition #1’s schedules…
+130ms ║║Condition group #1 evaluated true (state changed) (21ms)
+133ms ║║Cancelling statement #3’s schedules…
+140ms ║║Executed virtual command [Main Garage Door].setVariable (2ms)
+158ms ║║Executed virtual command [Main Garage Door].sendPushNotification (13ms)
+164ms ║║Executed virtual command [Main Garage Door].wait (1ms)
+166ms ║║Requesting a wake up for Tue, Nov 13 2018 @ 5:54:11 PM PST (in 3600.0s)
+172ms ║╚Execution stage complete. (70ms)
+174ms ║Setting up scheduled job for Tue, Nov 13 2018 @ 5:54:11 PM PST (in 3599.994s)
+182ms ╚Event processed successfully (182ms)


#7

I also tried reinstalling the new Smartthings app and disabled notification on the classic app and still received the notification twice from the new app.


#8

I went to the extreme of removing webcore, reseting my hub and sensors to factory default and then we setting everything from scratch and I have the exact same issue.

Im at a loss. Would welcome any suggestions but I have to think it is a bug?


#9

Here’s my guess, force your subscription to the global variable to ‘never subscribe’.


#10

I believe I have solved my issue. I still dont understand why the original piston would run twice but with the following changes I now am receiving one notification,