Why is my piston receiving events from other devices that are not being used in it?


#1

1) Give a description of the problem
I have a piston that is running correctly. However, in the logs I am receiving events from devices that are not being used in that piston

2) What is the expected behaviour?
I should receive only events that trigger the piston

**4) Post a Green Snapshot of the piston![image|45x37]
I am posting a red screenshot to keep the device names

5) Attach logs after turning logging level to Full
12/17/2019, 4:39:07 PM +300ms
+0ms ╔Received event [Breez-E].mode = favorite with a delay of 100ms
+89ms ╚Event processed successfully (88ms)
12/17/2019, 4:22:17 PM +279ms
+2ms ╔Received event [Breez-E].mode = auto with a delay of 86ms
+117ms ╚Event processed successfully (117ms)
12/17/2019, 3:27:28 PM +581ms
+1ms ╔Received event [Dust-E].mode = charging with a delay of 52ms
+98ms ╚Event processed successfully (98ms)
12/17/2019, 3:26:58 PM +470ms
+1ms ╔Received event [Dust-E].mode = returning with a delay of 63ms
+80ms ╚Event processed successfully (80ms)
12/17/2019, 3:12:18 PM +173ms
+2ms ╔Received event [Dust-E].mode = cleaning with a delay of 89ms
+121ms ╚Event processed successfully (121ms)
12/17/2019, 3:12:17 PM +833ms
+1ms ╔Received event [Breez-E].mode = favorite with a delay of 68ms
+106ms ╚Event processed successfully (105ms)
12/17/2019, 3:12:15 PM +168ms
+0ms ╔Received event [localhost].mode = Away with a delay of 98ms
+1719ms ╚Event processed successfully (1719ms)

The device Dust-E is another device that I own but I am not using in the current piston.

FYI: Dust-E = Roborock S50 and Breez-E is Xiaomi Air Purifier Pro


#2

It might be interesting to see what the logs say when the piston starts up and it is subscribing. On the other hand I rather suspect it might not.

Seems to me that webCoRE has subscribed to the ‘mode’ attribute of the ‘location’ as required and is getting events from the ‘mode’ attribute of other devices too. Whether that is webCoRE doing something wrong or SmartThings doing something wrong, I couldn’t say. It is almost like using ‘mode’ as the name of an attribute hasn’t been considered, but that seems ridiculous.


#3

According to the three lightning bolts in the left margin, this piston should fire each and every time “Location mode” changes to anything at all…

(although nothing is stopping you from triggering this piston from another piston…)